CVE-2026-67316
MEDIUMDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 20% of all known CVEs.
References
Related Vulnerabilities
Other CWE-1321 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-0230 | Critical | 9.8 | 97% | - | - |
| CVE-2019-11358 | Medium | 6.1 | 87% | - | Fix |
| CVE-2020-7774 | High | 7.3 | 69% | - | Fix |
| CVE-2022-24760 | Critical | 10.0 | 49% | - | Fix |
| CVE-2022-39396 | Critical | 9.8 | 39% | - | Fix |
| CVE-2022-2564 | Critical | 9.8 | 33% | - | Fix |
Common questions
How do I fix CVE-2026-67316?
Published advisories record a fix for 3 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-67316 being actively exploited?
Not that we know of. CVE-2026-67316 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.28% is the estimated probability that it will be exploited in the next 30 days. That is higher than 20% of all scored CVEs.
How severe is CVE-2026-67316?
CVE-2026-67316 has a CVSS v4 base score of 6.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-67316 affect?
Published advisories record a fix for node-axios (Debian), grafana13 (Red Hat / RHEL), grafana13 (Rocky). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-67316
Markdown
[](https://tridentstack.com/cve/CVE-2026-67316)HTML
<a href="https://tridentstack.com/cve/CVE-2026-67316"><img src="https://tridentstack.com/cve/badge/CVE-2026-67316.svg" alt="CVE-2026-67316"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-03.