CVE-2026-67316

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). 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
Trending — 3 sources updated this weekElevated
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via (config || {}).data before config normalization, causing an attacker-controlled body to be sent on requests that did not set one. Additional low-level paths, only reachable when calling exported adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in axios 1.18.0 and 0.33.0.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 1, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

axios before 1.18.0 Prototype Pollution via bodyless methods | Advisories | VulnCheck

https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-bodyless-methods
github Patch Available🟡 PoC Available

Prototype pollution gadgets can alter axios request construction · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-mmx7-hfxf-jppx

Vendor Advisories for CVE-2026-67316(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana13-1-main-13.1.1-0.5.2.hum12026-08-05redhat
redhatgrafana13-1-main-13.1.1-0.5.hum12026-08-03redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-axios0.21.1+dfsg-1 ... 1.8.4+dfsg-1 (40 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (22 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (12 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (9 versions)1.18.0-1—
npm(1)
PackageVulnerable rangeFixed inDependents
axios—0.33.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 84× 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.

Showing the most recent 100 of 182 total refreshes for this CVE.

  1. 2026-09-29 06:46 UTCEG score recompute
  2. 2026-09-29 06:46 UTCVendor advisory
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 07:26 UTCVendor advisory
  5. 2026-09-27 18:22 UTCEG score recompute
  6. 2026-09-27 18:22 UTCVendor advisory
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-25 04:50 UTCEG score recompute
  10. 2026-09-25 04:50 UTCVendor advisory
  11. 2026-09-24 13:23 UTCVendor advisory
  12. 2026-09-24 00:18 UTCEG score recompute
  13. 2026-09-24 00:18 UTCVendor advisory
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-23 10:53 UTCVendor advisory
  16. 2026-09-22 21:32 UTCEG score recompute
  17. 2026-09-22 21:32 UTCVendor advisory
  18. 2026-09-22 06:58 UTCEG score recompute
  19. 2026-09-22 06:58 UTCVendor advisory
  20. 2026-09-20 20:59 UTCEG score recompute
  21. 2026-09-20 20:59 UTCVendor advisory
  22. 2026-09-20 20:16 UTCEPSS rescore
  23. 2026-09-19 23:31 UTCEG score recompute
  24. 2026-09-19 23:31 UTCVendor advisory
  25. 2026-09-19 03:57 UTCEG score recompute
Show 75 more
  1. 2026-09-19 03:57 UTCVendor advisory
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 14:51 UTCVendor advisory
  4. 2026-09-18 01:14 UTCEG score recompute
  5. 2026-09-18 01:14 UTCVendor advisory
  6. 2026-09-17 01:22 UTCEG score recompute
  7. 2026-09-17 01:22 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:24 UTCEG score recompute
  10. 2026-09-16 05:24 UTCVendor advisory
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 04:32 UTCEG score recompute
  13. 2026-09-15 04:32 UTCVendor advisory
  14. 2026-09-14 15:00 UTCVendor advisory
  15. 2026-09-14 01:55 UTCEG score recompute
  16. 2026-09-14 01:55 UTCVendor advisory
  17. 2026-09-13 12:50 UTCVendor advisory
  18. 2026-09-12 23:45 UTCEG score recompute
  19. 2026-09-12 23:45 UTCVendor advisory
  20. 2026-09-12 10:04 UTCVendor advisory
  21. 2026-09-11 20:59 UTCEG score recompute
  22. 2026-09-11 20:59 UTCVendor advisory
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 09:37 UTCEPSS rescore
  25. 2026-09-11 07:54 UTCVendor advisory
  26. 2026-09-10 18:49 UTCEG score recompute
  27. 2026-09-10 18:49 UTCVendor advisory
  28. 2026-09-10 03:16 UTCVendor advisory
  29. 2026-09-09 06:56 UTCEG score recompute
  30. 2026-09-09 06:56 UTCVendor advisory
  31. 2026-09-08 22:01 UTCEPSS rescore
  32. 2026-09-07 19:16 UTCEG score recompute
  33. 2026-09-07 19:16 UTCVendor advisory
  34. 2026-09-07 16:01 UTCEPSS rescore
  35. 2026-09-06 21:17 UTCEG score recompute
  36. 2026-09-06 21:17 UTCVendor advisory
  37. 2026-09-06 13:47 UTCEPSS rescore
  38. 2026-09-06 08:07 UTCVendor advisory
  39. 2026-09-05 19:00 UTCEG score recompute
  40. 2026-09-05 19:00 UTCVendor advisory
  41. 2026-09-05 15:31 UTCEPSS rescore
  42. 2026-09-05 05:56 UTCVendor advisory
  43. 2026-09-04 16:51 UTCEG score recompute
  44. 2026-09-04 16:51 UTCVendor advisory
  45. 2026-09-04 05:07 UTCEPSS rescore
  46. 2026-09-04 03:39 UTCVendor advisory
  47. 2026-09-03 09:03 UTCEG score recompute
  48. 2026-09-03 09:03 UTCVendor advisory
  49. 2026-09-02 14:12 UTCEPSS rescore
  50. 2026-09-02 07:57 UTCVendor advisory
  51. 2026-09-01 16:06 UTCEG score recompute▲ 1.10
  52. 2026-09-01 16:06 UTCVendor advisory
  53. 2026-09-01 15:56 UTCNVD updateCVSS v3 → 7.4 · severity → HIGH
  54. 2026-09-01 13:54 UTCEPSS rescore
  55. 2026-09-01 04:40 UTCEPSS rescore
  56. 2026-08-31 20:46 UTCVendor advisory
  57. 2026-08-30 23:58 UTCEG score recompute
  58. 2026-08-30 23:58 UTCVendor advisory
  59. 2026-08-30 23:58 UTCGHSA enrichment
  60. 2026-08-30 19:17 UTCEPSS rescore
  61. 2026-08-30 01:22 UTCEPSS rescore
  62. 2026-08-29 22:12 UTCEG score recompute
  63. 2026-08-29 22:12 UTCVendor advisory
  64. 2026-08-29 22:12 UTCGHSA enrichment
  65. 2026-08-28 21:42 UTCEPSS rescore
  66. 2026-08-27 08:56 UTCEG score recompute
  67. 2026-08-27 08:56 UTCVendor advisory
  68. 2026-08-27 08:56 UTCGHSA enrichment
  69. 2026-08-26 14:47 UTCEPSS rescore
  70. 2026-08-26 07:10 UTCEG score recompute
  71. 2026-08-26 07:10 UTCVendor advisory
  72. 2026-08-26 07:09 UTCGHSA enrichment
  73. 2026-08-25 13:49 UTCEPSS rescore
  74. 2026-08-25 05:18 UTCEG score recompute
  75. 2026-08-25 05:18 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67316?
CVE-2026-67316 is a high vulnerability published on August 1, 2026. axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is…
When was CVE-2026-67316 disclosed?
CVE-2026-67316 was first published on August 1, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67316 actively exploited?
CVE-2026-67316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67316?
CVE-2026-67316 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-67316?
A fix for CVE-2026-67316 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67316 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67316

Explore →

Is Your Infrastructure Affected by CVE-2026-67316?

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

Book a Demo →Browse All CVEs