libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided with a trailing dot.curl can be told to receive and send cookies. curl's "cookie engine" can bebuilt with or without [Public Suffix List](https://publicsuffix.org/)awareness. If PSL support not provided, a more rudimentary check exists to atleast prevent cookies from being set on TLDs. This check was broken if thehost name in the URL uses a trailing dot.This can allow arbitrary sites to set cookies that then would get sent to adifferent and unrelated site or domain.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 5.3 · haxx, netapp, splunkNVD modified 2026-10-14 17:17
Affected (CPE criteria) 12
cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:*cpe:2.3:o:netapp:hci_bootstrap_os:-:*:*:*:*:*:*:*cpe:2.3:a:netapp:clustered_data_ontap:-:*:*:*:*:*:*:*cpe:2.3:a:netapp:solidfire\,_enterprise_sds_\&_hci_storage_node:-:*:*:*:*:*:*:*cpe:2.3:a:netapp:solidfire_\&_hci_management_node:-:*:*:*:*:*:*:*cpe:2.3:h:netapp:hci_compute_node:-:*:*:*:*:*:*:*cpe:2.3:o:netapp:h410s_firmware:-:*:*:*:*:*:*:*cpe:2.3:o:netapp:h700s_firmware:-:*:*:*:*:*:*:*cpe:2.3:o:netapp:h500s_firmware:-:*:*:*:*:*:*:*cpe:2.3:o:netapp:h300s_firmware:-:*:*:*:*:*:*:*cpe:2.3:a:splunk:universal_forwarder:*:*:*:*:*:*:*:*cpe:2.3:a:splunk:universal_forwarder:9.1.0:*:*:*:*:*:*:*
References 7
- https://hackerone.com/reports/1553301 Exploit, Third Party Advisory
- https://security.gentoo.org/glsa/202212-01 Third Party Advisory
- https://security.netapp.com/advisory/ntap-20220609-0009/ Third Party Advisory
- https://hackerone.com/reports/1553301 Exploit, Third Party Advisory
- https://security.gentoo.org/glsa/202212-01 Third Party Advisory
- https://security.netapp.com/advisory/ntap-20220609-0009/ Third Party Advisory
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html