{"answers":{"affected":"2 open source packages ship an affected version, including axios.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101900 exists.","fix":"Upgrade axios to 1.20.0 or later.","what":"CVE-2026-101900 is a medium-severity code injection vulnerability in axios, published on 28 Sep 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-101900 and fix it if it is affected.\n\nWhat it is: CVE-2026-101900 is a medium-severity code injection vulnerability in axios, published on 28 Sep 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-101900 exists.\n\nAffected packages and fixed versions:\n- axios (npm): affected from 1.12.0; fixed in 1.20.0\n- axios (npm): affected from 1.12.0; fixed in 1.20.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-101900/ (Markdown: https://insights.sbomify.com/CVE-2026-101900/index.md)","id":"CVE-2026-101900","markdown":"https://insights.sbomify.com/CVE-2026-101900/index.md","name":"CVE-2026-101900","record":{"aliases":["CLEANSTART-2026-AM75023","CLEANSTART-2026-MF48068","CLEANSTART-2026-RK00164","DEBIAN-CVE-2026-101900","ECHO-6b1e-ec03-9a56","GHSA-4hqw-qxg8-jxx2","MINI-24m8-2php-hcfr","MINI-2h3g-6cxx-jjp9","MINI-5jff-mwpw-455v","MINI-c857-rhm8-vp67","MINI-cpv4-6582-5r6q","MINI-cqfp-9hwj-4g8m","MINI-crm2-33jg-qg2v","MINI-g3wf-4xxg-hx54","MINI-m3mp-5g98-346h","MINI-prc3-wp43-r87m","MINI-rw5f-7c99-wx2f","MINI-v8xw-2pp7-355q","MINI-vf7q-8gw7-p2qg","MINI-xrhv-vh7h-g9rv","MINI-xw27-jc36-rv23","UBUNTU-CVE-2026-101900"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript HTTP client","requires_auth":"none","summary":"Prototype pollution allows attackers to inject malicious headers into Axios fetch requests, potentially bypassing security controls or altering request behavior.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"},{"id":"CWE-693","name":"Protection Mechanism Failure"},{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"Axios is a promise-based HTTP client for the browser and Node.js. From 1.12.0 until 1.20.0, ResolveConfig reads inherited Symbol.toStringTag, append, and getHeaders properties while resolving FormData headers. A separate same-process prototype-pollution flaw supplies an array or non-plain class instance whose inherited properties make it appear FormData-like; plain objects are blocked. The inherited getHeaders function can return attacker-controlled headers that resolveConfig merges into a fetch adapter request. Attacker-controlled headers can alter authorization, cache, metadata-service, or application-specific request behavior. This issue is fixed in version 1.20.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: Fetch Adapter Header Injection via Inherited FormData getHeaders","id":"CVE-2026-101900","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Axios: Denial of Service via Unhandled 'error' Event in HTTP/2 ClientHttp2Session Initialization","id":"CVE-2026-101901"},"packages":[{"ecosystem":"npm","fixed":["1.20.0"],"introduced":["1.12.0"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-4hqw-qxg8-jxx2"},{"ecosystem":"npm","fixed":["1.20.0"],"introduced":["1.12.0"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-4hqw-qxg8-jxx2"}],"prev":{"headline":"Axios: CIDR-form NO_PROXY entries are ignored, causing proxy exclusion bypass for internal IP ranges","id":"CVE-2026-101899"},"products":["axios"],"published":"2026-09-28","related":[],"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":"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-09-28","vendors":["axios"]},"summary":"Prototype pollution allows attackers to inject malicious headers into Axios fetch requests, potentially bypassing security controls or altering request behavior.","url":"https://insights.sbomify.com/CVE-2026-101900/"}