The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host name part of a URL, making it a *different* URL usingthe wrong host name when it is later retrieved.For example, a URL like `http://example.com%2F127.0.0.1/`, would be allowed bythe parser and get transposed into `http://example.com/127.0.0.1/`. This flawcan be used to circumvent filters, checks and more.
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 7.5 · haxx, netapp, splunkNVD modified 2026-10-14 17:17
Affected (CPE criteria) 11
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: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/1553841 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/1553841 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