{"answers":{"affected":"2 open source packages ship an affected version, including axios. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67314 exists.","fix":"Upgrade axios to 1.18.0 or later.","what":"CVE-2026-67314 is a medium-severity vulnerability in axios, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-67314 and fix it if it is affected.\n\nWhat it is: CVE-2026-67314 is a medium-severity vulnerability in axios, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67314 exists.\n\nAffected packages and fixed versions:\n- axios (npm): affected from 1.15.2; fixed in 1.18.0\n- axios (npm): affected from 1.15.2; fixed in 1.18.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-67314/ (Markdown: https://insights.sbomify.com/CVE-2026-67314/index.md)","id":"CVE-2026-67314","markdown":"https://insights.sbomify.com/CVE-2026-67314/index.md","name":"CVE-2026-67314","record":{"aliases":["CLEANSTART-2026-UQ32454","CVE-2026-68943","DEBIAN-CVE-2026-67314","ECHO-2457-771f-4c04","GHSA-xj6q-8x83-jv6g","MINI-29w6-p48f-rfvp","MINI-4jhc-4vxx-r2jj","MINI-5hvg-vp69-4w45","MINI-6hqc-v526-hxjc","MINI-6qrx-rrg8-86fc","MINI-84pj-fmpw-2vjw","MINI-fqhm-67xf-rv45","MINI-g6c4-mm9v-675m","MINI-hhvv-6p79-v28v","MINI-mr74-cwq6-ww54","MINI-q4h8-757g-6547","MINI-qc42-4qfv-357p","MINI-rg7v-hgpq-428h","MINI-x85f-6fpj-8xqf","MINI-xwp8-2j9c-fc68","ROOT-APP-NPM-CVE-2026-67314","ROOT-APP-NPM-GHSA-xj6q-8x83-jv6g","UBUNTU-CVE-2026-67314"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript HTTP client","requires_auth":"none","summary":"Attackers can tamper with outbound HTTP requests by injecting Basic auth credentials if the application is already vulnerable to prototype pollution.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"axios","vendor":"axios"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"axios versions \u003e=1.15.2 and \u003c1.18.0 contain prototype-pollution read-side gadgets in Basic auth subfield handling (lib/adapters/http.js and lib/helpers/resolveConfig.js). When an application is already affected by a separate prototype-pollution primitive and makes an axios request with an own auth object that omits the username and/or password properties, axios reads the inherited Object.prototype.username and Object.prototype.password values and uses them to construct an outbound 'Authorization: Basic ...' header. axios itself does not pollute prototypes. The practical impact is outbound request tampering: an attacker who controls the polluted prototype values can inject attacker-chosen Basic auth credentials or replace an existing Authorization header. Credential disclosure is only possible under additional application-specific conditions.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"axios before 1.18.0 Prototype Pollution via auth subfields","id":"CVE-2026-67314","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"axios 0.31.0 before 0.33.0 and 1.15.0 before 1.18.0 NO_PROXY Bypass via 0.0.0.0","id":"CVE-2026-67315"},"packages":[{"ecosystem":"npm","fixed":["1.18.0"],"introduced":["1.15.2"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-xj6q-8x83-jv6g"},{"ecosystem":"npm","fixed":["1.18.0"],"introduced":["1.15.2"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-xj6q-8x83-jv6g"}],"prev":{"headline":"axios 0.28.0 before 1.18.0 Denial of Service via formDataToJSON","id":"CVE-2026-67313"},"products":["axios"],"published":"2026-08-01","related":[{"cvss_score":8.7,"headline":"Axios: Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`","id":"CVE-2026-44494","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":8.6,"headline":"axios's shouldBypassProxy does not recognize IPv4-mapped IPv6 addresses, allowing NO_PROXY bypass (incomplete fix for CVE-2025-62718)","id":"CVE-2026-44492","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":8.3,"headline":"axios before 0.33.0 Prototype Pollution via Node HTTP adapter","id":"CVE-2026-67320","kev_date_added":null,"published":"2026-08-01"},{"cvss_score":8.2,"headline":"Axios: Proxy-Authorization Credential Leak to Origin Server Across HTTP-to-HTTPS Redirect in Axios Node.js HTTP Adapter","id":"CVE-2026-44487","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":7.7,"headline":"Possible SSRF and Credential Leakage via Absolute URL in axios Requests","id":"CVE-2025-27152","kev_date_added":null,"published":"2025-03-07"},{"cvss_score":7.5,"headline":"Axios: Proxy-Authorization header leaks to redirect target when proxy is re-evaluated to direct connection","id":"CVE-2026-44486","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":7.5,"headline":"Axios: Allocation of Resources Without Limits or Throttling in axios","id":"CVE-2026-44488","kev_date_added":null,"published":"2026-06-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["axios"]},"summary":"Attackers can tamper with outbound HTTP requests by injecting Basic auth credentials if the application is already vulnerable to prototype pollution.","url":"https://insights.sbomify.com/CVE-2026-67314/"}