{"answers":{"affected":"4 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-42041 exists.","fix":"Upgrade axios to a fixed version for your release line: 0.31.1 or 1.15.1.","what":"CVE-2026-42041 is a medium-severity authentication bypass vulnerability in axios, published on 24 Apr 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-42041 and fix it if it is affected.\n\nWhat it is: CVE-2026-42041 is a medium-severity authentication bypass vulnerability in axios, published on 24 Apr 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-42041 exists.\n\nAffected packages and fixed versions:\n- axios (npm): affected all versions; fixed in 0.31.1\n- axios (npm): affected all versions; fixed in 0.31.1\n- axios (npm): affected from 1.0.0; fixed in 1.15.1\n- axios (npm): affected from 1.0.0; fixed in 1.15.1\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-42041/ (Markdown: https://insights.sbomify.com/CVE-2026-42041/index.md)","id":"CVE-2026-42041","markdown":"https://insights.sbomify.com/CVE-2026-42041/index.md","name":"CVE-2026-42041","record":{"aliases":["CLEANSTART-2026-CN08649","CLEANSTART-2026-IW47152","DEBIAN-CVE-2026-42041","ECHO-3a30-297d-811b","GHSA-w9j2-pvgh-6h63","MINI-23wx-x6q5-6wmj","MINI-2f7j-qgp6-fr2h","MINI-2fh3-c29m-r33h","MINI-39jr-rrm4-cmpv","MINI-48fj-8wp9-8j35","MINI-5hjw-f54m-8w6p","MINI-659h-v463-9jhq","MINI-8g4w-q57c-qq8f","MINI-9w7m-mrrx-3jwh","MINI-f8m8-qc88-gmgc","MINI-mj6v-6r77-gpxp","MINI-p88r-wxjh-x9mq","MINI-p95x-3836-6887","MINI-pv7f-rr46-38w3","MINI-qgcq-f57x-557m","MINI-v43x-mj2q-vjhg","MINI-w83f-7r48-5j9p","MINI-w9m4-q4vv-mwr5","MINI-x6mq-vwxp-w35p","ROOT-APP-NPM-CVE-2026-42041","UBUNTU-CVE-2026-42041"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript HTTP client","requires_auth":"none","summary":"Prototype pollution in Axios allows attackers to bypass authentication by suppressing HTTP error responses, treating failures as successes.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"axios","vendor":"axios"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-915","name":"Improperly Controlled Modification of Dynamically-Determined Object Attributes"},{"id":"CWE-287","name":"Improper Authentication"},{"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. Prior to 1.15.1 and 0.31.1, the Axios library is vulnerable to a Prototype Pollution \"Gadget\" attack that allows any Object.prototype pollution to silently suppress all HTTP error responses (401, 403, 500, etc.), causing them to be treated as successful responses. This completely bypasses application-level authentication and error handling. The root cause is that validateStatus is the only config property using the mergeDirectKeys merge strategy, which uses JavaScript's in operator — an operator that inherently traverses the prototype chain. When Object.prototype.validateStatus is polluted with () =\u003e true, all HTTP status codes are accepted as success. This vulnerability is fixed in 1.15.1 and 0.31.1.","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: Authentication Bypass via Prototype Pollution Gadget in `validateStatus` Merge Strategy","id":"CVE-2026-42041","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Axios: XSRF Token Cross-Origin Leakage via Prototype Pollution Gadget in `withXSRFToken` Boolean Coercion","id":"CVE-2026-42042"},"packages":[{"ecosystem":"npm","fixed":["0.31.1"],"introduced":["0"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-w9j2-pvgh-6h63"},{"ecosystem":"npm","fixed":["0.31.1"],"introduced":["0"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-w9j2-pvgh-6h63"},{"ecosystem":"npm","fixed":["1.15.1"],"introduced":["1.0.0"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-w9j2-pvgh-6h63"},{"ecosystem":"npm","fixed":["1.15.1"],"introduced":["1.0.0"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-w9j2-pvgh-6h63"}],"prev":{"headline":"Axios: Null Byte Injection via Reverse-Encoding in AxiosURLSearchParams","id":"CVE-2026-42040"},"products":["axios"],"published":"2026-04-24","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-09-10","vendors":["axios"]},"summary":"Prototype pollution in Axios allows attackers to bypass authentication by suppressing HTTP error responses, treating failures as successes.","url":"https://insights.sbomify.com/CVE-2026-42041/"}