CVE-2026-87863
🟡 Lowcurl · 8.2.0 through 8.22.0
CVSS (Koffei note)
–CVSS (v3.1, CVE List)
8.1EPSS (2026-11-18)
0.828%58.21th percentile
Exploitation
No — no exploitation mentioned by the vendor or CERT-FR; no SSVC yet; not in KEV. Not in the 0day "In the Wild" sheet (checked 18/11/2026). cyberveille RSS: checked 18/11/2026 (feed 19/10 to 17/11/2026), no result (automated enrichment)
Timeline
- 20/10/2026CVE record published (CVE List)
- 18/11/2026CERT-FR relays Oracle's off-cycle November update for six product lines
Risk
CVSS n/d — no score in the record, EPSS n/a (not scored or API error on 18/11/2026) (CWE-201: An HTTPS origin can send an extreme HSTS max-age that parses but fails to serialize on 64-bit; the HSTS cache file is truncated before the failed save, leaving it empty or partial, and the error is silently ignored.)
Fix
Yes — Oracle MySQL: Oracle cspunov2026 (17/11/2026)
Official 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H