Answer in brief
CVE-2022-27780 records a Medium severity (CVSS 5.3) vulnerability in CVE Program Container. The current sources do not mark it as known exploited. The current feed maps haxx/curl (generic), netapp/hci_bootstrap_os (generic), n/a/https://github.com/curl/curl (generic), netapp/ontap_9 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps haxx/curl (generic), netapp/hci_bootstrap_os (generic), n/a/https://github.com/curl/curl (generic), netapp/ontap_9 (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| haxx/curlgeneric | >=0 <7.86.0 | 7.86.0 |
| netapp/hci_bootstrap_osgeneric | 0 | Not reported |
| n/a/https://github.com/curl/curlgeneric | Fixed in 7.83.1 | Not reported |
| netapp/ontap_9generic | 0 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.0 <V3.1.5 | V3.1.5 |
| netapp/solidfire_\&_hci_management_nodegeneric | h300s || h410s || h500s || h700s | Not reported |
| netapp/solidfire_\&_hci_management_nodegeneric | 0 | Not reported |
| netapp/solidfire_\&_hci_storage_nodegeneric | 0 | Not reported |
Published upstream
Jun 1, 2022
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.