Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Proxy-Authorization header not cleared on cross-origin redirect in fetch in Undici

CVSS 3.1 3.9 LOWEUVD CVSS 3.1 3.9 CVSS 3.1 · [email protected] · Secondary 3.9 LOWCVSS 3.1 · [email protected] · Primary 4.5 MEDIUMCVSS_V3 Publisher rating LOWFixed by undici 5.28.3Fixed by undici 6.6.1KEV status unknown

cve-program · CVE-2024-24758

Published

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Read the publisher's advisory

euvd · EUVD-2024-0479

Published

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Read the publisher's advisory

nvd · CVE-2024-24758

Published

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Read the publisher's advisory

osv · GHSA-3787-6prv-h9w3

Published

### Impact Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authorization` headers. ### Patches This is patched in v5.28.3 and v6.6.1 ### Workarounds There are no known workarounds. ### References - https://fetch.spec.whatwg.org/#authentication-entries - https://github.com/nodejs/undici/security/advisories/GHSA-wqq4-5wpv-mx2g

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2024-24758

Published

Proxy-Authorization header not cleared on cross-origin redirect in fetch in Undici

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Source published
16 Feb 2024 21:40:37 UTC
Source modified
13 Feb 2025 17:40:21 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

euvd · EUVD-2024-0479

Published

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6…

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Feb 16, 2024, 9:40:37 PM

dateUpdated: Feb 13, 2025, 5:40:21 PM

13 related source bulletins · separate from aliases

SUSE-SU-2024:0731-1: Security update for nodejs16

CVE-2023-46809 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806

SUSE-SU-2024:0730-1: Security update for nodejs18

CVE-2023-46809 · CVE-2024-21892 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806

openSUSE-SU-2024:13697-1: corepack20-20.11.1-1.1 on GA media

CVE-2023-46809 · CVE-2024-21890 · CVE-2024-21891 · CVE-2024-21892 · CVE-2024-21896 · CVE-2024-22017 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806

WID-SEC-W-2024-0393: Node.js: Mehrere Schwachstellen

CVE-2023-46809 · CVE-2024-21890 · CVE-2024-21891 · CVE-2024-21892 · CVE-2024-21896 · CVE-2024-22017 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806

SUSE-SU-2024:0644-1: Security update for nodejs18

CVE-2023-46809 · CVE-2024-21892 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806

msrc_CVE-2024-24758: Proxy-Authorization header not cleared on cross-origin redirect in fetch in Undici

CVE-2024-24758

SUSE-SU-2024:0729-1: Security update for nodejs16

CVE-2023-46809 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806

ICSA-24-319-08: Siemens SINEC INS

CVE-2023-2975 · CVE-2023-3341 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-4236 · CVE-2023-4408 · CVE-2023-4807 · CVE-2023-5517 · CVE-2023-5678 · CVE-2023-5679 · CVE-2023-5680 · CVE-2023-6129 · CVE-2023-6237 · CVE-2023-6516 · CVE-2023-7104 · CVE-2023-32002 · CVE-2023-32003 · CVE-2023-32004 · CVE-2023-32005 · CVE-2023-32006 · CVE-2023-32558 · CVE-2023-32559 · CVE-2023-38552 · CVE-2023-39331 · CVE-2023-39332 · CVE-2023-39333 · CVE-2023-44487 · CVE-2023-45143 · CVE-2023-46809 · CVE-2023-47038 · CVE-2023-47039 · CVE-2023-47100 · CVE-2023-48795 · CVE-2023-50387 · CVE-2023-50868 · CVE-2023-52389 · CVE-2024-0232 · CVE-2024-0727 · CVE-2024-2511 · CVE-2024-4741 · CVE-2024-5535 · CVE-2024-21890 · CVE-2024-21891 · CVE-2024-21892 · CVE-2024-21896 · CVE-2024-22017 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806 · CVE-2024-27980 · CVE-2024-27982 · CVE-2024-27983 · CVE-2024-46888 · CVE-2024-46889 · CVE-2024-46890 · CVE-2024-46891 · CVE-2024-46892 · CVE-2024-46894

NCSC-2024-0433: Kwetsbaarheden verholpen in Siemens producten

CVE-2021-3506 · CVE-2023-2975 · CVE-2023-3341 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-4236 · CVE-2023-4408 · CVE-2023-4807 · CVE-2023-5363 · CVE-2023-5517 · CVE-2023-5678 · CVE-2023-5679 · CVE-2023-5680 · CVE-2023-6129 · CVE-2023-6237 · CVE-2023-6516 · CVE-2023-7104 · CVE-2023-28450 · CVE-2023-30584 · CVE-2023-32002 · CVE-2023-32003 · CVE-2023-32004 · CVE-2023-32005 · CVE-2023-32006 · CVE-2023-32558 · CVE-2023-32559 · CVE-2023-32736 · CVE-2023-38552 · CVE-2023-38709 · CVE-2023-39331 · CVE-2023-39332 · CVE-2023-39333 · CVE-2023-44487 · CVE-2023-45143 · CVE-2023-46218 · CVE-2023-46219 · CVE-2023-46280 · CVE-2023-46809 · CVE-2023-47038 · CVE-2023-47039 · CVE-2023-47100 · CVE-2023-48795 · CVE-2023-49441 · CVE-2023-50387 · CVE-2023-50868 · CVE-2023-52389 · CVE-2024-0232 · CVE-2024-0727 · CVE-2024-2004 · CVE-2024-2379 · CVE-2024-2398 · CVE-2024-2466 · CVE-2024-2511 · CVE-2024-4603 · CVE-2024-4741 · CVE-2024-5535 · CVE-2024-5594 · CVE-2024-21890 · CVE-2024-21891 · CVE-2024-21892 · CVE-2024-21896 · CVE-2024-22017 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24795 · CVE-2024-24806 · CVE-2024-26306 · CVE-2024-26925 · CVE-2024-27316 · CVE-2024-27980 · CVE-2024-27982 · CVE-2024-27983 · CVE-2024-28882 · CVE-2024-29119 · CVE-2024-36140 · CVE-2024-44102 · CVE-2024-46888 · CVE-2024-46889 · CVE-2024-46890 · CVE-2024-46891 · CVE-2024-46892 · CVE-2024-46894 · CVE-2024-47783 · CVE-2024-47808 · CVE-2024-47940 · CVE-2024-47941 · CVE-2024-47942 · CVE-2024-50310 · CVE-2024-50313 · CVE-2024-50557 · CVE-2024-50558 · CVE-2024-50559 · CVE-2024-50560 · CVE-2024-50561 · CVE-2024-50572

openSUSE-SU-2024:13698-1: corepack21-21.6.2-1.1 on GA media

CVE-2023-46809 · CVE-2024-21890 · CVE-2024-21891 · CVE-2024-21892 · CVE-2024-21896 · CVE-2024-22017 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758

SUSE-SU-2024:0728-1: Security update for nodejs16

CVE-2023-46809 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806

SUSE-SU-2024:0643-1: Security update for nodejs20

CVE-2023-46809 · CVE-2024-21890 · CVE-2024-21891 · CVE-2024-21892 · CVE-2024-21896 · CVE-2024-22017 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806

SSA-915275: SSA-915275: Multiple Vulnerabilities in SINEC INS Before V1.0 SP2 Update 3

CVE-2023-2975 · CVE-2023-3341 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-4236 · CVE-2023-4408 · CVE-2023-4807 · CVE-2023-5517 · CVE-2023-5678 · CVE-2023-5679 · CVE-2023-5680 · CVE-2023-6129 · CVE-2023-6237 · CVE-2023-6516 · CVE-2023-7104 · CVE-2023-32002 · CVE-2023-32003 · CVE-2023-32004 · CVE-2023-32005 · CVE-2023-32006 · CVE-2023-32558 · CVE-2023-32559 · CVE-2023-38552 · CVE-2023-39331 · CVE-2023-39332 · CVE-2023-39333 · CVE-2023-44487 · CVE-2023-45143 · CVE-2023-46809 · CVE-2023-47038 · CVE-2023-47039 · CVE-2023-47100 · CVE-2023-48795 · CVE-2023-50387 · CVE-2023-50868 · CVE-2023-52389 · CVE-2024-0232 · CVE-2024-0727 · CVE-2024-2511 · CVE-2024-4741 · CVE-2024-5535 · CVE-2024-21890 · CVE-2024-21891 · CVE-2024-21892 · CVE-2024-21896 · CVE-2024-22017 · CVE-2024-22019 · CVE-2024-22025 · CVE-2024-24758 · CVE-2024-24806 · CVE-2024-27980 · CVE-2024-27982 · CVE-2024-27983 · CVE-2024-46888 · CVE-2024-46889 · CVE-2024-46890 · CVE-2024-46891 · CVE-2024-46892 · CVE-2024-46894

Source published
Feb 16, 2024, 9:40:37 PM (timezone not stated)
Source modified
Feb 13, 2025, 5:40:21 PM (timezone not stated)
Saved here
15 Nov 2026 01:51:11 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

nvd · CVE-2024-24758

Published

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6…

Undici is an HTTP/1.1 client, written from scratch for Node.js. Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authentication` headers. This issue has been patched in versions 5.28.3 and 6.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-200 · NVD-CWE-noinfo

Original publisher date fields

published: 2024-02-16T22:15:08.160

lastModified: 2026-06-17T07:14:48.017

1 source CPE criteria · context only
  • cpe:2.3:a:nodejs:undici:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
16 Feb 2024 22:15:08 UTC
Source modified
17 Jun 2026 07:14:48 UTC
Saved here
24 Oct 2026 23:17:28 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 3.9 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L

CVSS 3.1 · [email protected] · Primary · 4.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

osv · GHSA-3787-6prv-h9w3

Published

Undici proxy-authorization header not cleared on cross-origin redirect in fetch

### Impact Undici already cleared Authorization headers on cross-origin redirects, but did not clear `Proxy-Authorization` headers. ### Patches This is patched in v5.28.3 and v6.6.1 ### Workarounds There are no known workarounds. ### References - https://fetch.spec.whatwg.org/#authentication-entries - https://github.com/nodejs/undici/security/advisories/GHSA-wqq4-5wpv-mx2g

Source published
16 Feb 2024 16:02:52 UTC
Source modified
10 Sep 2026 03:50:05 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

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

Publisher rating · LOW

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 22:31 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current