CVE-2026-87863

UnknownEPSS 0.29%

Last modified

CVE-2026-87863 is a vulnerability of currently unknown severity. An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exceeds calendar time structure bounds. EPSS estimates a 0.29% chance of exploitation in the next 30 days.

Description

An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exceeds calendar time structure bounds. During cache saves, the original HSTS file is truncated before writing a temporary replacement; when serialization fails, the temporary file is deleted, leaving an empty or partial cache. Because the save error is silently ignored during cleanup, curl exits successfully despite the data loss.

Metrics

EPSS Probability
0.29%

20.5th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
curlcurl>= 8.22.0, <= 8.22.0; >= 8.21.0, <= 8.21.0; >= 8.20.0, <= 8.20.0; >= 8.19.0, <= 8.19.0; >= 8.18.0, <= 8.18.0; >= 8.17.0, <= 8.17.0; >= 8.16.0, <= 8.16.0; >= 8.15.0, <= 8.15.0; >= 8.14.1, <= 8.14.1; >= 8.14.0, <= 8.14.0; >= 8.13.0, <= 8.13.0; >= 8.12.1, <= 8.12.1; >= 8.12.0, <= 8.12.0; >= 8.11.1, <= 8.11.1; >= 8.11.0, <= 8.11.0; >= 8.10.1, <= 8.10.1; >= 8.10.0, <= 8.10.0; >= 8.9.1, <= 8.9.1; >= 8.9.0, <= 8.9.0; >= 8.8.0, <= 8.8.0; >= 8.7.1, <= 8.7.1; >= 8.7.0, <= 8.7.0; >= 8.6.0, <= 8.6.0; >= 8.5.0, <= 8.5.0; >= 8.4.0, <= 8.4.0; >= 8.3.0, <= 8.3.0; >= 8.2.1, <= 8.2.1; >= 8.2.0, <= 8.2.0

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-87863?
An authenticated HTTPS origin can supply an HSTS `max-age` value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exceeds calendar time structure bounds. During cache saves, the original HSTS file is truncated before writing a temporary replacement; when serialization fails, the temporary file is deleted, leaving an empty or partial cache. Because the save error is silently ignored during cleanup, curl exits successfully despite the data loss.
How severe is CVE-2026-87863?
Severity scoring for CVE-2026-87863 is pending analysis. The EPSS model estimates a 0.29% probability of exploitation in the next 30 days.
How do I fix CVE-2026-87863?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-87863?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST