CVE Intelligence
High SSRF exploit reference

CVE-2022-27780 — The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host...

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.

Published Jun 2, 2022 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: hackerone

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 2.5% (30-day exploitation probability)+13
  • Technical severity (high)+6
  • CISA SSVC: exploitation "poc"+5
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
2.47%
ahead of 84% of scored CVEs · Oct 14, 2026
Affects
Haxx
Curl and 9 more
CVSS base
7.5
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Haxx Curl, Netapp Clustered Data Ontap, Netapp H300s Firmware…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Haxx Curl ≥ 7.80.0 and < 7.83.1 Vulnerable NIST National Vulnerability Database
Netapp Clustered Data Ontap versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H300s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H410s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H500s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H700s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Hci Bootstrap Os versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Solidfire & Hci Management Node versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Solidfire, Enterprise Sds & Hci Storage Node versions not specified by the source Vulnerable NIST National Vulnerability Database
Splunk Universal Forwarder ≥ 8.2.0 and < 8.2.12≥ 9.0.0 and < 9.0.6version 9.1.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 nvd@nist.gov via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
5.3 CVSS 3.1 Medium 3.9 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
5.3 CVSS 3.1 Medium — — CISA-ADP via CVE Program (cve.org) e CISA ADP
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 7.5 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.
web/proxy/WAF logsnetwork IDS/IPSegress traffic

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Affected products added · haxx/curl, netapp/hci bootstrap os, netapp/clustered data ontap, netapp/solidfire, enterprise sds & hci storage node, ne
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 7.5
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2022
  • CVE published
    Jun 2, 2022 · hackerone

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

7 on the record

Elsewhere on this site

Haxx
every CVE for this vendor
SSRF
same class
CWE-918
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-82209 Insertion of Sensitive Information Into Sent Data in Haxx Curl Sep 6, 2026
  • High CVE-2026-80229 Use After Free in Haxx Curl Sep 6, 2026
  • High CVE-2026-80230 Improper Certificate Validation in Haxx Curl Sep 6, 2026
  • High CVE-2026-80231 A flaw in libcurl makes it wrongly reuse an existing HTTPS connection setup for a given… Sep 6, 2026
  • High CVE-2026-82208 Improper Certificate Validation in Haxx Curl Sep 6, 2026
  • High CVE-2026-80255 Insertion of Sensitive Information Into Sent Data in Haxx Curl Sep 6, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-27780 is "The curl URL parser wrongly accepts percent-encoded URL separators like '/'when decoding the host...", rated High. It affects Curl (Haxx); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 2.47% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.