{"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-44489 exists.","fix":"Upgrade axios to 1.16.0 or later.","what":"CVE-2026-44489 is a low-severity code injection vulnerability in axios, published on 11 Jun 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-44489 and fix it if it is affected.\n\nWhat it is: CVE-2026-44489 is a low-severity code injection vulnerability in axios, published on 11 Jun 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-44489 exists.\n\nAffected packages and fixed versions:\n- axios (npm): affected from 1.15.2; fixed in 1.16.0\n- axios (npm): affected from 1.15.2; fixed in 1.16.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-44489/ (Markdown: https://insights.sbomify.com/CVE-2026-44489/index.md)","id":"CVE-2026-44489","markdown":"https://insights.sbomify.com/CVE-2026-44489/index.md","name":"CVE-2026-44489","record":{"aliases":["DEBIAN-CVE-2026-44489","ECHO-e2b7-45f0-bb81","GHSA-654m-c8p4-x5fp","MINI-4mj2-5rpf-rccx","MINI-7w7m-99h4-g3mh","MINI-9xj4-58p8-hgvm","MINI-cgjw-w43w-fqvm","MINI-crpr-wvmj-mcv9","MINI-g65c-4mpx-4736","MINI-h5r4-53rr-x6x4","MINI-jc7f-jxjr-55m7","ROOT-APP-NPM-CVE-2026-44489","UBUNTU-CVE-2026-44489"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript HTTP client","requires_auth":"none","summary":"Prototype pollution allows injecting attacker-controlled Proxy-Authorization headers into proxied requests, potentially exposing credentials or bypassing authentication.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"axios","vendor":"axios"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"},{"id":"CWE-113","name":"Improper Neutralization of CRLF Sequences in HTTP Headers"}],"description":"Axios is a promise based HTTP client for the browser and Node.js. From 1.15.2 to before 1.16.0, nested objects created by utils.merge() (e.g., config.proxy) are still constructed as plain {} with Object.prototype in their chain. The setProxy() function at lib/adapters/http.js:209-223 reads proxy.username, proxy.password, and proxy.auth without hasOwnProperty checks. When Object.prototype.username is polluted, setProxy() constructs a Proxy-Authorization header with attacker-controlled credentials and injects it into every proxied HTTP request. This vulnerability is fixed in 1.16.0.","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: Proxy-Authorization Header Injection via Prototype Pollution — Incomplete Null-Prototype Fix","id":"CVE-2026-44489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Axios: DoS \u0026 Header Injection via Prototype Pollution Read-Side Gadgets in axios merge functions","id":"CVE-2026-44490"},"packages":[{"ecosystem":"npm","fixed":["1.16.0"],"introduced":["1.15.2"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-654m-c8p4-x5fp"},{"ecosystem":"npm","fixed":["1.16.0"],"introduced":["1.15.2"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-654m-c8p4-x5fp"}],"prev":{"headline":"Axios: Allocation of Resources Without Limits or Throttling in axios","id":"CVE-2026-44488"},"products":["axios"],"published":"2026-06-11","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-06-11","vendors":["axios"]},"summary":"Prototype pollution allows injecting attacker-controlled Proxy-Authorization headers into proxied requests, potentially exposing credentials or bypassing authentication.","url":"https://insights.sbomify.com/CVE-2026-44489/"}