{"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-42037 exists.","fix":"Upgrade axios to 1.15.1 or later.","what":"CVE-2026-42037 is a medium-severity 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-42037 and fix it if it is affected.\n\nWhat it is: CVE-2026-42037 is a medium-severity 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-42037 exists.\n\nAffected packages and fixed versions:\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-42037/ (Markdown: https://insights.sbomify.com/CVE-2026-42037/index.md)","id":"CVE-2026-42037","markdown":"https://insights.sbomify.com/CVE-2026-42037/index.md","name":"CVE-2026-42037","record":{"aliases":["CLEANSTART-2026-GJ80180","CLEANSTART-2026-HP63393","DEBIAN-CVE-2026-42037","ECHO-96d5-9fbe-5e29","GHSA-445q-vr5w-6q77","MINI-3fmx-xvwg-j8gp","MINI-4xmr-j8fx-vhxj","MINI-5rch-hgmm-3vx9","MINI-83gj-gp9p-275w","MINI-84cq-c477-753f","MINI-84j9-8657-xcjg","MINI-878q-wqmm-w4p9","MINI-932f-v2fg-jv9c","MINI-9m59-6pv2-w5f9","MINI-f42w-wjx7-8vr5","MINI-gfgf-hxcj-vphw","MINI-j2q7-f9h2-fq39","MINI-pwrq-gm2c-r9pv","MINI-qfjv-vhr3-fphg","MINI-rgxj-c7j7-hghr","MINI-vhx9-hxp2-jc69","MINI-w7r8-w453-fpxr","MINI-x6qj-j56h-m6fw","MINI-xvhp-2grc-p35c","ROOT-APP-NPM-CVE-2026-42037","UBUNTU-CVE-2026-42037"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js HTTP client","requires_auth":"none","summary":"Attackers can inject arbitrary MIME headers into multipart requests via unsanitized blob types, bypassing Node.js protections and altering request structure.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"axios","vendor":"axios"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-93","name":"Improper Neutralization of CRLF Sequences"}],"description":"Axios is a promise based HTTP client for the browser and Node.js. From 1.0.0 to before 1.15.1, the FormDataPart constructor in lib/helpers/formDataToStream.js interpolates value.type directly into the Content-Type header of each multipart part without sanitizing CRLF (\\r\\n) sequences. An attacker who controls the .type property of a Blob/File-like object (e.g., via a user-uploaded file in a Node.js proxy service) can inject arbitrary MIME part headers into the multipart form-data body. This bypasses Node.js v18+ built-in header protections because the injection targets the multipart body structure, not HTTP request headers. This vulnerability is fixed in 1.15.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: CRLF Injection in multipart/form-data body via unsanitized blob.type in formDataToStream","id":"CVE-2026-42037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Axios: no_proxy bypass via IP alias allows SSRF","id":"CVE-2026-42038"},"packages":[{"ecosystem":"npm","fixed":["1.15.1"],"introduced":["1.0.0"],"last_affected":[],"package":"axios","purl":null,"source":"GHSA-445q-vr5w-6q77"},{"ecosystem":"npm","fixed":["1.15.1"],"introduced":["1.0.0"],"last_affected":[],"package":"axios","purl":"pkg:npm/axios","source":"GHSA-445q-vr5w-6q77"}],"prev":{"headline":"Axios: HTTP adapter streamed responses bypass maxContentLength","id":"CVE-2026-42036"},"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-04-27","vendors":["axios"]},"summary":"Attackers can inject arbitrary MIME headers into multipart requests via unsanitized blob types, bypassing Node.js protections and altering request structure.","url":"https://insights.sbomify.com/CVE-2026-42037/"}