elysia
1.4.32 · 11 Nov 2026MIT2.2M / weekRepositorynpmAtom feed
1.4.32 is the newest release of 1.x.
In short
1 security1 new1 faster2 fixed8 changed
Security
Fixes 1 advisory that affected 1.4.16
- CriticalElysia vulnerable to prototype pollution with multiple standalone schema validationGHSA-hxj9-33pp-j2cc · 9 Dec 2025Fixed in 1.4.17
4 advisories affect 1.4.17; 1.4.29 fixes them
- Highelysia has Inefficient Algorithmic Complexity and Interpretation ConflictGHSA-9643-4qgh-g8mx · 23 Sep 2026Fixed in 1.4.29
- HighElysia has a string URL format ReDoSGHSA-f45g-68q3-5w8x · 10 Mar 2026Fixed in 1.4.26
- HighElysia affected by arbitrary code injection through cookie configGHSA-8vch-m3f4-q8jf · 9 Dec 2025Fixed in 1.4.18
- ModerateElysia Cookie Value Prototype PollutionGHSA-8hq9-phh3-p2wp · 17 Mar 2026Fixed in 1.4.27
Release note
What's Changed
Improvement:
Serveris always resolved toanywhen@types/bunis missingOptimize cookie value comparison using FNV-1a hash
Set-Cookie headers not sent when errors are thrown
HEAD to handle Promise value
Security:
- Security
Cookie injection, prototype pollution, and RCE
Bug fix:
Excess property checking
Allow cookie.sign to be string
Change:
Change customError property to unknown
Prevent sending set-cookie header when cookie value is not modified
Standard schema on websocket
Conditional parseQuery parameter
Conditional pass
c.requestto handler for streaming responseFix missing
contentTypetype onparser
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.