Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2022-35949: `undici.request` vulnerable to SSRF using absolute URL on `pathname`

Noroxi assessment

Priority: Plan (action score 40/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.2% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: node-undici (Debian:12) 5.8.2+dfsg1+~cs18.9.18.1-1; undici (npm) 5.8.2; nodejs16 (openSUSE:Leap 15.3) 16.17.0-150300.7.9.1.
  • Severity is disputed: the assigning authority (CNA) scores it 5.3, NVD 9.8.

Add it to your regular patch cycle. Upgrade to node-undici (Debian:12) 5.8.2+dfsg1+~cs18.9.18.1-1; undici (npm) 5.8.2; nodejs16 (openSUSE:Leap 15.3) 16.17.0-150300.7.9.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

undici is an HTTP/1.1 client, written from scratch for Node.js.`undici` is vulnerable to SSRF (Server-side Request Forgery) when an application takes in **user input** into the `path/pathname` option of `undici.request`. If a user specifies a URL such as `http://127.0.0.1` or `//127.0.0.1` ```js const undici = require("undici") undici.request({origin: "http://example.com", pathname: "//127.0.0.1"}) ``` Instead of processing the request as `http://example.org//127.0.0.1` (or `http://example.org/http://127.0.0.1` when `http://127.0.0.1 is used`), it actually processes the request as `http://127.0.0.1/` and sends it to `http://127.0.0.1`. If a developer passes in user input into `path` parameter of `undici.request`, it can result in an _SSRF_ as they will assume that the hostname cannot change, when in actual fact it can change because the specified path parameter is combined with the base URL. This issue was fixed in `undici@5.8.1`. The best workaround is to validate user input before passing it to the `undici.request` call.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Aug 12, 2022
Updated
Jun 17, 2026
EPSS
1.8% · 79th percentile

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.8%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.8
CNA · GitHub_M
5.3
4.5 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-35949

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nodejs records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nodejsundici

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs undiciup to 5.8.1 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • nodejs undici

    • <= 5.8.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12node-undicibefore 5.8.2+dfsg1+~cs18.9.18.1-15.8.2+dfsg1+~cs18.9.18.1-1
npmundicibefore 5.8.25.8.2
openSUSE:Leap 15.3nodejs16before 16.17.0-150300.7.9.116.17.0-150300.7.9.1
openSUSE:Leap 15.4nodejs16before 16.17.0-150400.3.6.116.17.0-150400.3.6.1
openSUSE:Tumbleweednodejs16before 16.17.0-2.116.17.0-2.1
SUSE:Linux Enterprise Module for Web and Scripting 12nodejs16before 16.17.0-8.9.116.17.0-8.9.1
SUSE:Linux Enterprise Module for Web and Scripting 15 SP3nodejs16before 16.17.0-150300.7.9.116.17.0-150300.7.9.1
SUSE:Linux Enterprise Module for Web and Scripting 15 SP4nodejs16before 16.17.0-150400.3.6.116.17.0-150400.3.6.1

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-1525undici is vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
    39Monitor
  • CVE-2026-109829undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects
    36Monitor
  • CVE-2026-109383undici vulnerable to TLS certificate validation bypass via dropped tls options in Agent
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2022-31150Jul 19, 2022 · CRLF injection in request headers
    26Monitor
  • ← EarlierCVE-2022-31151Jul 21, 2022 · Uncleared cookies on cross-host/cross-origin redirect in undici
    26Monitor
  • Later →CVE-2022-35948Aug 15, 2022 · CRLF Injection in Nodejs ‘undici’ via Content-Type
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:node-undici5.8.2+dfsg1+~cs18.9.18.1-1 · Debian:12Package registry (OSV)
npm:undici5.8.2Package registry (OSV)
opensuse:nodejs1616.17.0-150400.3.6.1 · openSUSE:Leap 15.4Package registry (OSV)
suse:nodejs1616.17.0-150400.3.6.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP4Package registry (OSV)
suse:nodejs1616.17.0-8.9.1 · SUSE:Linux Enterprise Module for Web and Scripting 12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

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

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records