{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-87863 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-87863 is a vulnerability in curl, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-87863 and fix it if it is affected.\n\nWhat it is: CVE-2026-87863 is a vulnerability in curl, published on 20 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-87863 in the wild and no public exploit code.\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-87863/ (Markdown: https://insights.sbomify.com/CVE-2026-87863/index.md)","id":"CVE-2026-87863","markdown":"https://insights.sbomify.com/CVE-2026-87863/index.md","name":"CVE-2026-87863","record":{"aliases":["ALPINE-CVE-2026-87863","AZL-109911","AZL-109986","AZL-110046","AZL-110142","AZL-110241","AZL-110307","BELL-CVE-2026-87863","CURL-CVE-2026-87863","DEBIAN-CVE-2026-87863","ECHO-1454-5f4f-4ffc","GHSA-53q4-87wj-266h","MINI-gvq6-j79p-gh3m","UBUNTU-CVE-2026-87863"],"analysis":null,"analysis_generated_by":null,"assigner":"curl","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"An authenticated HTTPS origin can supply an HSTS `max-age` value that the\nparser accepts, but time serialization later fails to process. On 64-bit\nsystems, extreme max-age values compute an absolute expiry within standard\ntime integer limits that exceeds calendar time structure bounds. During cache\nsaves, the original HSTS file is truncated before writing a temporary\nreplacement; when serialization fails, the temporary file is deleted, leaving\nan empty or partial cache. Because the save error is silently ignored during\ncleanup, curl exits successfully despite the data loss.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HSTS response erases persisted entries","id":"CVE-2026-87863","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"IMAP APPEND plus CRLF conversion command injection","id":"CVE-2026-87864"},"packages":[],"prev":{"headline":"HSTS cache import drops longer-lived child","id":"CVE-2026-87862"},"products":["curl"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-20","vendors":["curl"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-87863/"}