Quick answers
- Is CVE-2025-66456 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-66456 being exploited in the wild.
- How severe is CVE-2025-66456?
- Critical severity, with a CVSS score of 9.8, published 9 December 2025.
- Which products and versions are affected?
- elysia (npm) SEMVER:introduced=1.4.0,fixed=1.4.17.
- Is there a fix for CVE-2025-66456?
- Yes. elysia (npm): upgrade to 1.4.17 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-66456 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-66456?
- Check whether you run ElysiaJS Elysia or elysia (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- elysia (npm): upgrade to 1.4.17 or later
npm install elysia@1.4.17
Technical details
The vulnerability exists in the mergeDeep function used when processing multiple standalone schema validations with the same key. When merging validation results, the code fails to sanitize the __proto__ property, allowing an attacker to pollute the prototype chain and inject arbitrary properties into all objects. The attack requires routes with more than 2 standalone schema validators and relies on an "any" type in the schema guard. The vulnerability is network-reachable with no authentication required. When chained with GHSA-8vch-m3f4-q8jf (arbitrary code injection through cookie config), it enables remote code execution. Patched in version 1.4.17.
Affected products
- Elysia Elysia 1.4.0 to 1.4.16
Identifiers
- CVE-2025-66456
- GHSA-hxj9-33pp-j2cc
Timeline
- 2025-12-09: disclosed
- 2025-12-09: patched: Fixed in version 1.4.17