Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

Cross-site Scripting in tempuraGHSA-w4v7-hwx7-9929

MEDIUMFix: lukeed/tempura@58a5c36

GHSA-w4v7-hwx7-9929 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in tempura. 1 public exploit reference exists, so weaponization risk is real. A fix is available for tempura — see the affected versions and patch details below.

Also known asCVE-2021-23784SNYK-JS-TEMPURA-1569633
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.00%0.59%1.17%1.76%0.3%1.3%Apr 26Aug 26Oct 26

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

How urgent is this, really

GHSA-w4v7-hwx7-9929 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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.

7other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
tempuranpm
191Kdownloads / week

Description

This affects the package tempura before 0.4.0. If the input to the esc function is of type object (i.e an array) it is returned without being escaped/sanitized, leading to a potential Cross-Site Scripting vulnerability.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmtempuraall versions0.4.0npm install tempura@0.4.0

Affected Products

1 product · 1 configurations
Application
tempuratempura_project
< 0.4.0
range
Exploits & PoCs
1

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

This affects the package tempura before 0.4.0. If the input to the esc f…

snyk.ioNVDNov 2021

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update tempura to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w4v7-hwx7-9929 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

This affects the package tempura before 0.4.0. If the input to the esc function is of type object (i.e an array) it is returned without being escaped/sanitized, leading to a potential Cross-Site Scripting vulnerability.
O3 Security · Impact-Aware SCA

Is GHSA-w4v7-hwx7-9929 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Cross-site Scripting in tempura (Medium 6.1)