Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2023-45143: Undici's cookie header not cleared on cross-origin redirect in fetch

Noroxi assessment

Priority: Monitor (action score 14/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.3% (FIRST EPSS); higher than 72% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: nodejs undici 5.26.2.

Low priority for now. Upgrade to nodejs undici 5.26.2 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. Prior to version 5.26.2, Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Cookie` headers. By design, `cookie` headers are forbidden request headers, disallowing them to be set in RequestInit.headers in browser environments. Since undici handles headers more liberally than the spec, there was a disconnect from the assumptions the spec made, and undici's implementation of fetch. As such this may lead to accidental leakage of cookie to a third-party site or a malicious attacker who can control the redirection target (ie. an open redirector) to leak the cookie to the third party site. This was patched in version 5.26.2. There are no known workarounds.

LowCVSS 3.5 · v3.1—No exploit Fix available
Published
Oct 12, 2023
Updated
Jun 17, 2026
EPSS
1.3% · 72th percentile

Report tools

JSON

Action score

14

Monitor

Low priority for now.

CVSS
14 / 40 · 3.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
3.5
CNA · GitHub_M
3.9
0.4 point gap

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

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-2023-45143

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
fedoraprojectfedora

Affected versions

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

  • fedoraproject fedora37
  • fedoraproject fedora38
  • fedoraproject fedora39
  • nodejs undicibefore 5.26.2

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.26.2affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejsbefore 1:20.8.1-1.module_el8.9.0+3675+0258a6d91:20.8.1-1.module_el8.9.0+3675+0258a6d9
AlmaLinux:8nodejsbefore 1:18.18.2-1.module_el8.8.0+3652+0e111ba01:18.18.2-1.module_el8.8.0+3652+0e111ba0
AlmaLinux:8nodejs-develbefore 1:20.8.1-1.module_el8.9.0+3675+0258a6d91:20.8.1-1.module_el8.9.0+3675+0258a6d9
AlmaLinux:8nodejs-develbefore 1:18.18.2-1.module_el8.8.0+3652+0e111ba01:18.18.2-1.module_el8.8.0+3652+0e111ba0
AlmaLinux:8nodejs-docsbefore 1:20.8.1-1.module_el8.9.0+3675+0258a6d91:20.8.1-1.module_el8.9.0+3675+0258a6d9
AlmaLinux:8nodejs-docsbefore 1:18.18.2-1.module_el8.8.0+3652+0e111ba01:18.18.2-1.module_el8.8.0+3652+0e111ba0
AlmaLinux:8nodejs-full-i18nbefore 1:20.8.1-1.module_el8.9.0+3675+0258a6d91:20.8.1-1.module_el8.9.0+3675+0258a6d9
AlmaLinux:8nodejs-full-i18nbefore 1:18.18.2-1.module_el8.8.0+3652+0e111ba01:18.18.2-1.module_el8.8.0+3652+0e111ba0
AlmaLinux:8nodejs-nodemonbefore 3.0.1-1.module_el8.9.0+3675+0258a6d93.0.1-1.module_el8.9.0+3675+0258a6d9
AlmaLinux:8nodejs-nodemonbefore 3.0.1-1.module_el8.8.0+3613+1ed8c91d3.0.1-1.module_el8.8.0+3613+1ed8c91d
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8nodejs-packagingbefore 2021.06-4.module_el8.9.0+3684+11b9e9592021.06-4.module_el8.9.0+3684+11b9e959
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.7.0+3343+ea2b79012021.06-4.module_el8.7.0+3343+ea2b7901
AlmaLinux:8nodejs-packaging-bundlerbefore 2021.06-4.module_el8.9.0+3684+11b9e9592021.06-4.module_el8.9.0+3684+11b9e959
AlmaLinux:8npmbefore 1:10.1.0-1.20.8.1.1.module_el8.9.0+3675+0258a6d91:10.1.0-1.20.8.1.1.module_el8.9.0+3675+0258a6d9
AlmaLinux:8npmbefore 1:9.8.1-1.18.18.2.1.module_el8.8.0+3652+0e111ba01:9.8.1-1.18.18.2.1.module_el8.8.0+3652+0e111ba0
AlmaLinux:9nodejsbefore 1:18.18.2-2.module_el9.2.0+43+3ebc9e201:18.18.2-2.module_el9.2.0+43+3ebc9e20
AlmaLinux:9nodejs-develbefore 1:18.18.2-2.module_el9.2.0+43+3ebc9e201:18.18.2-2.module_el9.2.0+43+3ebc9e20
AlmaLinux:9nodejs-docsbefore 1:18.18.2-2.module_el9.2.0+43+3ebc9e201:18.18.2-2.module_el9.2.0+43+3ebc9e20
AlmaLinux:9nodejs-full-i18nbefore 1:18.18.2-2.module_el9.2.0+43+3ebc9e201:18.18.2-2.module_el9.2.0+43+3ebc9e20
AlmaLinux:9nodejs-nodemonbefore 3.0.1-1.module_el9.2.0+36+853e48f53.0.1-1.module_el9.2.0+36+853e48f5
AlmaLinux:9nodejs-packagingbefore 2021.06-4.module_el9.1.0+13+d9a595ea2021.06-4.module_el9.1.0+13+d9a595ea
AlmaLinux:9nodejs-packaging-bundlerbefore 2021.06-4.module_el9.1.0+13+d9a595ea2021.06-4.module_el9.1.0+13+d9a595ea
AlmaLinux:9npmbefore 1:9.8.1-1.18.18.2.2.module_el9.2.0+43+3ebc9e201:9.8.1-1.18.18.2.2.module_el9.2.0+43+3ebc9e20

+60

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-35949`undici.request` vulnerable to SSRF using absolute URL on `pathname`
    40Plan
  • 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

Published before and after this one in the same product

  • ← EarlierCVE-2022-35948Aug 15, 2022 · CRLF Injection in Nodejs ‘undici’ via Content-Type
    21Monitor
  • ← EarlierCVE-2023-24807Feb 16, 2023 · Undici vulnerable to Regular Expression Denial of Service in Headers
    30Monitor
  • Later →CVE-2024-24750Feb 16, 2024 · Backpressure request ignored in fetch() in Undici
    26Monitor

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
nodejs undici5.26.2 · descriptionVendor (CNA)
almalinux:nodejs1:18.18.2-2.module_el9.2.0+43+3ebc9e20 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-devel1:18.18.2-2.module_el9.2.0+43+3ebc9e20 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-docs1:18.18.2-2.module_el9.2.0+43+3ebc9e20 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-full-i18n1:18.18.2-2.module_el9.2.0+43+3ebc9e20 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-nodemon3.0.1-1.module_el9.2.0+36+853e48f5 · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-packaging2021.06-4.module_el9.1.0+13+d9a595ea · AlmaLinux:9Package registry (OSV)
almalinux:nodejs-packaging-bundler2021.06-4.module_el9.1.0+13+d9a595ea · AlmaLinux:9Package registry (OSV)
almalinux:npm1:9.8.1-1.18.18.2.2.module_el9.2.0+43+3ebc9e20 · AlmaLinux:9Package registry (OSV)
alpine:nodejs18.18.2-r0 · Alpine:v3.17Package registry (OSV)
alpine:nodejs-current20.8.1-r0 · Alpine:v3.18Package registry (OSV)
alpine:openjdk2121.0.2_p13-r0 · Alpine:v3.19Package registry (OSV)
debian:node-undici5.15.0+dfsg1+~cs20.10.9.3-1+deb12u2 · Debian:12Package registry (OSV)
npm:undici5.26.2Package registry (OSV)
npm:undici5.8.0Package registry (OSV)
opensuse:nodejs-electron25.9.1-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:nodejs2020.8.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:nodejs1:18.18.2-2.module+el9.2.0.z+20408+7cb5fda5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-debuginfo1:18.18.2-2.module+el9.2.0.z+20408+7cb5fda5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-debugsource1:18.18.2-2.module+el9.2.0.z+20408+7cb5fda5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-devel1:18.18.2-2.module+el9.2.0.z+20408+7cb5fda5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-docs1:18.18.2-2.module+el9.2.0.z+20408+7cb5fda5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-full-i18n1:18.18.2-2.module+el9.2.0.z+20408+7cb5fda5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-nodemon0:3.0.1-1.module+el9.2.0.z+19753+58118bc0 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-packaging0:2021.06-4.module+el9.1.0+15718+e52ec601 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:nodejs-packaging-bundler0:2021.06-4.module+el9.1.0+15718+e52ec601 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:npm1:9.8.1-1.18.18.2.2.module+el9.2.0.z+20408+7cb5fda5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:nodejs-nodemon0:3.0.1-1.module+el9.7.0+40017+f0db1785 · Rocky Linux:9Package registry (OSV)
rocky linux:nodejs-packaging0:2021.06-4.module+el9.7.0+40022+9ecc286c · Rocky Linux:9Package registry (OSV)
suse:nodejs1616.20.2-8.36.1 · SUSE:Linux Enterprise Module for Web and Scripting 12Package registry (OSV)

+1

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.

No history yet (it accumulates with the daily EPSS job).

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.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

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

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

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

Change log

  1. Fix✗ → ✓

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

References

Show all references (10 more)

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

All records