elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
Upgrading elysia From 1.4.16 to 1.4.17
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 1
- advisory fixed
- 2
- new
- 2
- fixes
Security
4 advisories still affect 1.4.17
- Elysia Cookie Value Prototype Pollutionmoderate · GHSA-8hq9-phh3-p2wp
- Elysia affected by arbitrary code injection through cookie confighigh · GHSA-8vch-m3f4-q8jf
- elysia has Inefficient Algorithmic Complexity and Interpretation Conflicthigh · GHSA-9643-4qgh-g8mx
- Elysia has a string URL format ReDoShigh · GHSA-f45g-68q3-5w8x
Upgrading to 1.4.29 clears them.
Fixes 1 advisory affecting 1.4.16
- Elysia vulnerable to prototype pollution with multiple standalone schema validationcritical · GHSA-hxj9-33pp-j2cc
- 1.4.17
Cookie injection, prototype pollution, and RCE
Release by release
- Security
Cookie injection, prototype pollution, and RCE
- New
Optimize cookie value comparison using FNV-1a hash
- New
Allow cookie.sign to be string
- Fixed
Prevent sending set-cookie header when cookie value is not modified
- Fixed
Fix missing
contentTypetype onparser
- Security
8 other lines we could not sort, mostly version bumps
- 1.4.17
Serveris always resolved toanywhen@types/bunis missing - 1.4.17
Set-Cookie headers not sent when errors are thrown
- 1.4.17
HEAD to handle Promise value
- 1.4.17
Excess property checking
- 1.4.17
Change customError property to unknown
- 1.4.17
Standard schema on websocket
- 1.4.17
Conditional parseQuery parameter
- 1.4.17
Conditional pass
c.requestto handler for streaming response
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.