{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86409 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-86409 is a high-severity vulnerability in curl, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-86409 and fix it if it is affected.\n\nWhat it is: CVE-2026-86409 is a high-severity vulnerability in curl, published on 20 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86409 exists.\n\nAffected product: curl. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-86409/ (Markdown: https://insights.sbomify.com/CVE-2026-86409/index.md)","id":"CVE-2026-86409","markdown":"https://insights.sbomify.com/CVE-2026-86409/index.md","name":"CVE-2026-86409","record":{"aliases":["ALPINE-CVE-2026-86409","AZL-109914","AZL-109956","AZL-110010","AZL-110160","AZL-110256","AZL-110283","BELL-CVE-2026-86409","CURL-CVE-2026-86409","DEBIAN-CVE-2026-86409","ECHO-b6fb-b123-10db","GHSA-57hx-469r-xq3r","MINI-7c46-pm2w-833c","MINI-hhjx-8w93-wcqx","UBUNTU-CVE-2026-86409"],"analysis":null,"analysis_generated_by":null,"assigner":"curl","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication,\ncontrary to expectations and documentation. A subsequent transfer on the same\nhandle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL\nisset next, leaking state information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"stale SigV4 headers sent unintended","id":"CVE-2026-86409","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"redirect to SFTP or SCP bypasses host verification","id":"CVE-2026-86410"},"packages":[],"prev":{"headline":"MISP Missing Authorization in Cryptographic Key View Exposes Signing Keys from Protected Events","id":"CVE-2026-86408"},"products":["curl"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["curl"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-86409/"}