CVE-2026-67319

LOWNVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.7 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% 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
Trending — 3 sources updated this weekElevated
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 3.7Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

axios before 0.33.0 (and 1.x before 1.18.0) can consume inherited properties from nested request option objects when the JavaScript process's Object.prototype has already been polluted by another component. While the top-level merged config uses a null prototype, nested plain objects such as auth and paramsSerializer are cloned into ordinary objects and read without own-property checks. When an application passes placeholder nested objects such as auth: {} or paramsSerializer: {}, inherited username/password values can cause silent injection of an Authorization: Basic header, and inherited encode/serialize values can alter query-string serialization (full serializer replacement requires a function-valued pollution primitive). This is exploitable only in the presence of pre-existing prototype pollution.

CVSS v3
3.7
EG Score
3.7LOWmedium confidence
EG Risk
33
EG Risk 33/100

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
Severity37% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

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 0.33.0 Prototype Pollution via nested option objects | Advisories | VulnCheck

https://www.vulncheck.com/advisories/axios-before-prototype-pollution-via-nested-option-objects
github Patch Available🟡 PoC Available

Nested axios option objects can consume polluted prototype values · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-7q8q-rj6j-mhjq

Vendor Advisories for CVE-2026-67319(4)

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.4.hum12026-08-01redhat
redhatgrafana12-4-main-12.4.6-0.3.hum12026-08-01redhat

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—1.18.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 42× 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 149 total refreshes for this CVE.

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

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

Same vendor

2 shown

redhat:RHSA-2026:49387 · redhat:RHSA-2026:49401

Frequently asked(5)

What is CVE-2026-67319?
CVE-2026-67319 is a low vulnerability published on August 1, 2026. axios before 0.33.0 (and 1.x before 1.18.0) can consume inherited properties from nested request option objects when the JavaScript process's Object.prototype has already been polluted by another component. While the top-level merged config uses a null prototype, nested plain objects such as auth…
When was CVE-2026-67319 disclosed?
CVE-2026-67319 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-67319 actively exploited?
CVE-2026-67319 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67319?
CVE-2026-67319 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-67319?
A fix for CVE-2026-67319 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67319 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-67319

Explore →

Is Your Infrastructure Affected by CVE-2026-67319?

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

Book a Demo →Browse All CVEs