Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-8hq9-phh3-p2wp

MEDIUM

Elysia Cookie Value Prototype Pollution

Also known asCVE-2026-31865
Published
Mar 17, 2026
Updated
Mar 19, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk14th percentile+0.21%
0.00%0.24%0.49%0.73%0.0%0.0%0.0%0.2%Apr 26Jun 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
📦elysia

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Elysia cookie can be overridden by prototype pollution , eg. __proto__

Sending cookie with the follows name can override cookie value:

__proto__=%7B%22injected%22%3A%22polluted%22%7D

Patches

Patched by 1.4.27

Workarounds

  1. Use t.Cookie validation to enforce validation value
  2. Prevent iterable over cookie if possible

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmelysiaall versions1.4.27

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for elysia. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update elysia to 1.4.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8hq9-phh3-p2wp is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-8hq9-phh3-p2wp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-8hq9-phh3-p2wp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Elysia cookie can be overridden by prototype pollution , eg. `__proto__` Sending cookie with the follows name can override cookie value: ```bash __proto__=%7B%22injected%22%3A%22polluted%22%7D ``` ### Patches Patched by 1.4.27 ### Workarounds 1. Use t.Cookie validation to enforce validation value 2. Prevent iterable over cookie if possible
O3 Security · Impact-Aware SCA

Is GHSA-8hq9-phh3-p2wp in your dependencies?

O3 detects GHSA-8hq9-phh3-p2wp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.