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

CVE-2022-37611 — gh-pages

CRITICALFix: tschaub/gh-pages#452

CVE-2022-37611 is a critical-severity (CVSS 9.8) CWE-1321 vulnerability in gh-pages. A fix is available for gh-pages — see the affected versions and patch details below.

tschaub gh-pages vulnerable to prototype pollution

Also known asGHSA-8mmm-9v2q-x3f9
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • 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 CVE-2022-37611.

EPSS Exploitation Probability

via FIRST.org ↗
1.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk
0.00%0.62%1.25%1.87%0.5%1.4%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.

1Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream
gh-pagesnpm
688Kdownloads / week

Description

Prototype pollution vulnerability in tschaub gh-pages 3.1.0 via the partial variable in util.js.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmgh-pagesall versions5.0.0npm install gh-pages@5.0.0

Affected Products

1 product · 1 configurations
Application
gh-pagesgh-pages_project
1 version
3.1.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update gh-pages to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-37611 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

Prototype pollution vulnerability in tschaub gh-pages 3.1.0 via the partial variable in util.js.
O3 Security · Impact-Aware SCA

Is CVE-2022-37611 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2022-37611: gh-pages — Fixed in 5.0.0