CVE-2022-24999

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.5%, top 18% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 15%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: [email protected]" in its release description, is not vulnerable).

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
96.3%
KEV
Not listed

Published

November 26, 2022

Last Modified

April 29, 2025

References (10)

Vendor Advisories for CVE-2022-24999(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunode-qs (6.9.1+ds-1ubuntu0.1~esm1) @ focal2026-05-25ubuntu
redhatopenshift-service-mesh/prometheus-rhel8:2.2.7-72023-06-15redhat
redhatodf4/mcg-core-rhel8:v4.12.3-42023-05-23redhat
redhatnodejs:14-8060020230306170237.ad008a3a2023-04-12redhat
redhatnodejs:14-8040020230306170312.522a0ee42023-03-30redhat
redhatrhmtc/openshift-migration-ui-rhel8:v1.7.8-52023-03-23redhat
redhatopenshift-logging/logging-view-plugin-rhel8:v5.6.3-52023-03-08redhat
redhatopenshift-logging/logging-view-plugin-rhel8:v5.5.8-32023-03-08redhat
redhatmta/mta-ui-rhel8:6.0.1-102023-02-28redhat
redhatrh-nodejs14-nodejs-nodemon-0:2.0.20-2.el72023-02-06redhat
redhatnodejs:14-8070020221212161539.bd1311ed2023-01-09redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
qs—6.2.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 36× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-09 19:07 UTCEPSS rescore
  3. 2026-07-08 15:12 UTCEPSS rescore
  4. 2026-07-07 13:44 UTCEPSS rescore
  5. 2026-07-05 02:28 UTCEPSS rescore
  6. 2026-07-04 06:29 UTCEPSS rescore
  7. 2026-07-04 06:29 UTCEPSS rescore
  8. 2026-07-01 15:04 UTCEPSS rescore
  9. 2026-06-29 14:04 UTCEPSS rescore
  10. 2026-06-29 14:04 UTCEPSS rescore
  11. 2026-06-28 14:06 UTCEPSS rescore
  12. 2026-06-28 12:49 UTCOSV refresh
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-28 04:54 UTCEPSS rescore
  15. 2026-06-27 03:07 UTCEPSS rescore
  16. 2026-06-25 13:48 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-21 14:55 UTCEPSS rescore
  22. 2026-06-21 14:55 UTCEPSS rescore
  23. 2026-06-21 01:58 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-18 17:51 UTCEPSS rescore
Show 46 more
  1. 2026-06-18 17:51 UTCEPSS rescore
  2. 2026-06-17 17:51 UTCEPSS rescore
  3. 2026-06-17 17:51 UTCEPSS rescore
  4. 2026-06-16 17:51 UTCEPSS rescore
  5. 2026-06-15 17:46 UTCEPSS rescore
  6. 2026-06-14 23:15 UTCEPSS rescore
  7. 2026-06-14 23:15 UTCEPSS rescore
  8. 2026-06-13 22:58 UTCEPSS rescore
  9. 2026-06-13 22:58 UTCEPSS rescore
  10. 2026-06-12 23:10 UTCEPSS rescore
  11. 2026-06-12 23:10 UTCEPSS rescore
  12. 2026-06-11 13:58 UTCEPSS rescore
  13. 2026-06-11 13:58 UTCEPSS rescore
  14. 2026-06-10 23:39 UTCOSV refresh
  15. 2026-06-10 22:16 UTCEPSS rescore
  16. 2026-06-10 13:20 UTCEPSS rescore
  17. 2026-06-08 14:15 UTCEPSS rescore
  18. 2026-06-08 14:15 UTCEPSS rescore
  19. 2026-06-07 15:23 UTCEPSS rescore
  20. 2026-06-07 15:23 UTCEPSS rescore
  21. 2026-06-05 22:45 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-02 20:11 UTCEPSS rescore
  27. 2026-06-02 20:11 UTCEPSS rescore
  28. 2026-06-02 20:11 UTCEPSS rescore
  29. 2026-06-01 13:50 UTCEPSS rescore
  30. 2026-06-01 13:50 UTCEPSS rescore
  31. 2026-06-01 13:50 UTCEPSS rescore
  32. 2026-05-31 22:29 UTCEPSS rescore
  33. 2026-05-31 22:29 UTCEPSS rescore
  34. 2026-05-31 00:15 UTCEPSS rescore
  35. 2026-05-31 00:15 UTCEPSS rescore
  36. 2026-05-29 13:42 UTCEPSS rescore
  37. 2026-05-28 13:43 UTCEPSS rescore
  38. 2026-05-28 13:43 UTCEPSS rescore
  39. 2026-05-28 13:43 UTCEPSS rescore
  40. 2026-05-27 13:39 UTCEPSS rescore
  41. 2026-05-27 13:39 UTCEPSS rescore
  42. 2026-05-26 13:43 UTCEPSS rescore
  43. 2026-05-26 07:17 UTCEPSS rescore
  44. 2026-05-26 07:17 UTCEPSS rescore
  45. 2026-05-25 11:32 UTCEG score recompute
  46. 2026-05-25 11:32 UTCVendor advisory

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCn8tz/CVE-2022-24999
    First seen Apr 18, 2022

    "qs" prototype poisoning vulnerability ( CVE-2022-24999 )

    Open source ↗
  • GitHub PoC9pings/CVE-2022-24999
    First seen Apr 18, 2022

    "qs" prototype poisoning vulnerability ( CVE-2022-24999 )

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-24999?
CVE-2022-24999 is a high vulnerability published on November 26, 2022. qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an proto key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of…
When was CVE-2022-24999 disclosed?
CVE-2022-24999 was first published in the National Vulnerability Database on November 26, 2022, with the most recent update on April 29, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-24999 actively exploited?
CVE-2022-24999 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-24999?
CVE-2022-24999 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-24999?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-24999, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-24999

Explore →

Is Your Infrastructure Affected by CVE-2022-24999?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs