Quick answers
- Is CVE-2026-67319 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67319 being exploited in the wild.
- How severe is CVE-2026-67319?
- Medium severity, with a CVSS score of 4, published 1 August 2026.
- Which products and versions are affected?
- Axios >=0.8.0 <0.33.0, >=1.0.0 <1.18.0.
- Is there a fix for CVE-2026-67319?
- A patch was published on 2026-07-06: Patches released: 0.33.0, 1.18.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67319 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-67319?
- Check whether you run Axios at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a prototype-pollution gadget in Axios that affects nested request option objects (auth, paramsSerializer). While the top-level merged config is protected with Object.create(null), nested objects are cloned into ordinary objects using plain {} constructors, allowing inherited properties from a polluted Object.prototype to be read. An attacker who has already polluted Object.prototype (via a separate vulnerability elsewhere in the application) can inject or override username/password for Basic auth or inject serialize/encode functions for query-string tampering. The attack requires passing placeholder nested objects like auth: {} or paramsSerializer: {} without explicit own properties. Patched versions (0.33.0+, 1.18.0+) harden these nested objects.
Affected products
- Axios Axios >=0.8.0 <0.33.0, >=1.0.0 <1.18.0
Identifiers
- CVE-2026-67319
- GHSA-7q8q-rj6j-mhjq
Timeline
- 2026-07-20: disclosed
- 2026-07-06: patched: Patches released: 0.33.0, 1.18.0