Skip to main content
CVE-2024-9681VulnerabilityPublished Updated

When curl is asked to use HSTS, the expiry time for a subdomain might overwrite a parent domain's cache entry, making

Source GCVE Database

0
Compare
Authoritative record:CVE-2024-9681· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium.

Data as of 30 Oct 2026, 00:41 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.15.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

Until a fix is available, users should be aware of this behavior when using curl with HSTS and consider manual cache management or avoiding mixed HTTP accesses to parent and subdomains with differing HSTS policies.

Description

A vulnerability in curl's handling of HSTS cache expiry times can cause the expiry time for a subdomain to overwrite the parent domain's cache entry. This leads to incorrect enforcement durations of HTTPS redirection for the parent domain, potentially causing curl to either prematurely revert to HTTP or continue HTTPS access beyond the intended expiry. The issue occurs when curl uses HSTS with URLs involving both a parent domain and its subdomain, and the HSTS cache has been populated from prior HTTPS accesses or manual entries.

References

Community reviews

Loading reviews…