NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

ejs lacks certain pollution protectionGHSA-ghr5-ch3p-vcr6

MEDIUMFix: mde/ejs@e469741

GHSA-ghr5-ch3p-vcr6 is a medium-severity (CVSS 4) CWE-693 vulnerability in ejs. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for ejs — see the affected versions and patch details below.

Also known asCVE-2024-33883
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-ghr5-ch3p-vcr6.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk
0.11%0.76%1.40%2.04%1.3%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

16Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
ejsnpm
59.2Mdownloads / week

Description

The ejs (aka Embedded JavaScript templates) package before 3.1.10 for Node.js lacks certain pollution protection.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmejsall versions3.1.10npm install ejs@3.1.10
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ejs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update ejs to 3.1.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghr5-ch3p-vcr6 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.

Frequently Asked Questions

The ejs (aka Embedded JavaScript templates) package before 3.1.10 for Node.js lacks certain pollution protection.
O3 Security · Impact-Aware SCA

Is GHSA-ghr5-ch3p-vcr6 in your dependencies?

Find it across npm, including transitive dependencies.

GHSA-ghr5-ch3p-vcr6: ejs — Fixed in 3.1.10