CVE-2026-11525
undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).
Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.
This was introduced in undici 5.15.0 when the cookies feature was added.
Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.
Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
3.7
undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).
Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.
This was introduced in undici 5.15.0 when the cookies feature was added.
Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.
Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
CVE-2026-11525- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-183
- Updated
- 2026-11-02
EUVDEUVD-2026-37758
3.7
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).
Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.
This was introduced in undici 5.15.0 when the cookies feature was added.
Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.
Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
EUVD-2026-37758- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-g8m3-5g58-fq7m
3.7
undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching
Impact
When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens:
SameSite=NoneOfYourBusinessis parsed asNone, the most permissive setting.SameSite=StrictLaxis parsed asLax, a downgrade fromStrict.
Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.
This was introduced in undici 5.15.0 when the cookies feature was added.
Patches
Upgrade to undici v6.27.0, v7.28.0 or v8.5.0.
Workarounds
After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
GHSA-g8m3-5g58-fq7m- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-183
- Updated
- 2026-11-02
NVD
3.7
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).
Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.
This was introduced in undici 5.15.0 when the cookies feature was added.
Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.
Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
CVE-2026-11525- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-183
- Updated
- 2026-11-02
OSV
3.7
undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).
Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.
This was introduced in undici 5.15.0 when the cookies feature was added.
Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.
Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
CVE-2026-11525- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-183
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-11525
3.7
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict). Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide. This was introduced in undici 5.15.0 when the cookies feature was added. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
DEBIAN-CVE-2026-11525- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
Show 45 moreShow less
OSVGHSA-g8m3-5g58-fq7m
3.7
undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching
Impact
When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens:
SameSite=NoneOfYourBusinessis parsed asNone, the most permissive setting.SameSite=StrictLaxis parsed asLax, a downgrade fromStrict.
Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.
This was introduced in undici 5.15.0 when the cookies feature was added.
Patches
Upgrade to undici v6.27.0, v7.28.0 or v8.5.0.
Workarounds
After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
GHSA-g8m3-5g58-fq7m- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Weakness
- CWE-183
- Updated
- 2026-11-02
OSVRHSA-2026:35841
8.1
Red Hat Security Advisory: nodejs24 security, bug fix, and enhancement update
- Record
RHSA-2026:35841- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:35842
8.1
Red Hat Security Advisory: nodejs22 security, bug fix, and enhancement update
- Record
RHSA-2026:35842- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:35891
8.1
Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update
- Record
RHSA-2026:35891- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:35892
8.1
Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update
- Record
RHSA-2026:35892- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:38236
7.5
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- Record
RHSA-2026:38236- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVRHSA-2026:39868
8.1
Red Hat Security Advisory: nodejs:24 security, bug fix, and enhancement update
- Record
RHSA-2026:39868- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:41947
8.1
Red Hat Security Advisory: nodejs:22 security, bug fix, and enhancement update
- Record
RHSA-2026:41947- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRHSA-2026:45783
3.7
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- Record
RHSA-2026:45783- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
OSVRLSA-2026:35841
8.1
Important: nodejs24 security, bug fix, and enhancement update
Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
Security Fix(es):
-
ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
-
undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
-
undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
-
undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
-
undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
-
undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy (CVE-2026-9697)
-
undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing (CVE-2026-6734)
-
nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
-
nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
-
nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
-
nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
-
nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
-
Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
-
nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
-
nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs24: Rebase to the latest Node.js 24 release [rhel-10.2.z] (JIRA:Rocky Linux-186582)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:35841- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRLSA-2026:35842
8.1
Important: nodejs22 security, bug fix, and enhancement update
Node.js is a platform built on Chrome's JavaScript runtime \ for easily building fast, scalable network applications. \ Node.js uses an event-driven, non-blocking I/O model that \ makes it lightweight and efficient, perfect for data-intensive \ real-time applications that run across distributed devices.
Security Fix(es):
-
ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
-
undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
-
undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
-
undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
-
undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
-
nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
-
nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
-
nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
-
nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
-
nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
-
Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
-
nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
-
nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs22: Rebase to the latest Node.js 22 release [rhel-10.2.z] (JIRA:Rocky Linux-186623)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:35842- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRLSA-2026:35891
8.1
Important: nodejs:24 security, bug fix, and enhancement update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
-
ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
-
undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
-
undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
-
undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
-
undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
-
undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy (CVE-2026-9697)
-
undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing (CVE-2026-6734)
-
nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
-
nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
-
nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
-
nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
-
nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
-
Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
-
nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
-
nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs:24/nodejs: Rebase to the latest Node.js 24 release [rhel-9.8.z] (JIRA:Rocky Linux-186580)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:35891- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRLSA-2026:35892
8.1
Important: nodejs:22 security, bug fix, and enhancement update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
-
ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
-
undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
-
undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
-
undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
-
undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
-
nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
-
nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
-
nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
-
nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
-
nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
-
Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
-
nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
-
nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs:22/nodejs: Rebase to the latest Node.js 22 release [rhel-9.8.z] (JIRA:Rocky Linux-186622)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:35892- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRLSA-2026:39868
8.1
Important: nodejs:24 security, bug fix, and enhancement update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
-
ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
-
undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
-
undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
-
undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
-
undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
-
undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy (CVE-2026-9697)
-
undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing (CVE-2026-6734)
-
nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
-
nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
-
nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
-
nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
-
nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
-
Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
-
nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
-
nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs:24/nodejs: Rebase to the latest Node.js 24 release [rhel-8] (JIRA:Rocky Linux-168744)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:39868- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVRLSA-2026:41947
8.1
Important: nodejs:22 security, bug fix, and enhancement update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
-
ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
-
undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
-
undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
-
undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
-
undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
-
nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
-
nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
-
nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
-
nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
-
nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
-
Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
-
nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
-
nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs:22/nodejs: Rebase to the latest Node.js 22 release [rhel-8] (JIRA:Rocky Linux-176170)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
RLSA-2026:41947- CVSS 3.1
- 8.1 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N - Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-11525
3.7
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict). Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide. This was introduced in undici 5.15.0 when the cookies feature was added. Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0. Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
UBUNTU-CVE-2026-11525- CVSS 3.1
- 3.7 Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N - Updated
- 2026-11-02
OSVALSA-2026:35841 No score
Important: nodejs24 security, bug fix, and enhancement update
Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
Security Fix(es):
- ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
- undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
- undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
- undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
- undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
- undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy (CVE-2026-9697)
- undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing (CVE-2026-6734)
- nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
- nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
- nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
- nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
- nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
- Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
- nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
- nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs24: Rebase to the latest Node.js 24 release [almalinux-10.2.z] (JIRA:AlmaLinux-186582)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:35841- Updated
- 2026-11-02
OSVALSA-2026:35842 No score
Important: nodejs22 security, bug fix, and enhancement update
Node.js is a platform built on Chrome's JavaScript runtime \ for easily building fast, scalable network applications. \ Node.js uses an event-driven, non-blocking I/O model that \ makes it lightweight and efficient, perfect for data-intensive \ real-time applications that run across distributed devices.
Security Fix(es):
- ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
- undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
- undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
- undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
- undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
- nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
- nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
- nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
- nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
- nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
- Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
- nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
- nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs22: Rebase to the latest Node.js 22 release [almalinux-10.2.z] (JIRA:AlmaLinux-186623)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:35842- Updated
- 2026-11-02
OSVALSA-2026:35891 No score
Important: nodejs:24 security, bug fix, and enhancement update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
- ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
- undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
- undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
- undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
- undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
- undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy (CVE-2026-9697)
- undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing (CVE-2026-6734)
- nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
- nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
- nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
- nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
- nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
- Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
- nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
- nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs:24/nodejs: Rebase to the latest Node.js 24 release [almalinux-9.8.z] (JIRA:AlmaLinux-186580)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:35891- Updated
- 2026-11-02
OSVALSA-2026:35892 No score
Important: nodejs:22 security, bug fix, and enhancement update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
- ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
- undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
- undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
- undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
- undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
- nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
- nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
- nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
- nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
- nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
- Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
- nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
- nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs:22/nodejs: Rebase to the latest Node.js 22 release [almalinux-9.8.z] (JIRA:AlmaLinux-186622)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:35892- Updated
- 2026-11-02
OSVALSA-2026:39868 No score
Important: nodejs:24 security, bug fix, and enhancement update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
- ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
- undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
- undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
- undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
- undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
- undici: undici: Man-in-the-Middle attack via ignored TLS options with SOCKS5 proxy (CVE-2026-9697)
- undici: undici: Information disclosure and data integrity issues due to incorrect Socks5ProxyAgent connection routing (CVE-2026-6734)
- nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
- nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
- nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
- nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
- nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
- Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
- nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
- nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs:24/nodejs: Rebase to the latest Node.js 24 release [almalinux-8] (JIRA:AlmaLinux-168744)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:39868- Updated
- 2026-11-02
OSVALSA-2026:41947 No score
Important: nodejs:22 security, bug fix, and enhancement update
Node.js is a software development platform for building fast and scalable network applications in the JavaScript programming language.
Security Fix(es):
- ip-address: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (CVE-2026-42338)
- undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (CVE-2026-12151)
- undici: Undici: Information disclosure due to improper cache-control header parsing (CVE-2026-9678)
- undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery. (CVE-2026-6733)
- undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (CVE-2026-11525)
- nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames (CVE-2026-48619)
- nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling (CVE-2026-48930)
- nodejs: Node.js: Unauthorized file metadata modification (CVE-2026-48935)
- nodejs: Node.js WebCrypto: Denial of Service via large input to subtle.encrypt() (CVE-2026-48933)
- nodejs: Node.js: Certification validation bypass in TLS host verification (CVE-2026-48934)
- Node.js: Node.js: Trust-policy bypass due to hostname matching inconsistency (CVE-2026-48928)
- nodejs: Node.js: Information disclosure of proxy credentials via proxy tunnel error handling (CVE-2026-48615)
- nodejs: Node.js: Authentication bypass due to TLS hostname handling and unicode dot separator mismatch (CVE-2026-48618)
Bug Fix(es) and Enhancement(s):
- nodejs:22/nodejs: Rebase to the latest Node.js 22 release [almalinux-8] (JIRA:AlmaLinux-176170)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
- Record
ALSA-2026:41947- Updated
- 2026-11-02
OSVAZL-91194 No score
CVE-2026-11525 affecting package nodejs for versions less than 24.18.1-1
Impact: When undici parses a Set-Cookie header, it accepts any SameSite attribute value that contains Strict, Lax, or None as a substring, rather than the case-insensitive exact match specified by RFC 6265. Non-spec values are silently mapped to one of the three standard tokens. For example, SameSite=NoneOfYourBusiness is parsed as None (the most permissive setting), and SameSite=StrictLax is parsed as Lax (a downgrade from Strict).
Affected applications are those that consume Set-Cookie headers from server responses (for example via undici's fetch or proxy code paths) and then forward or rely on the parsed sameSite attribute. A malicious or non-compliant server can coerce the consumer's view of a cookie's SameSite policy to a weaker value, silently degrading the SameSite enforcement the cookie is supposed to provide.
This was introduced in undici 5.15.0 when the cookies feature was added.
Patches: Upgrade to undici v6.26.0, v7.28.0 or v8.5.0.
Workarounds: After parsing a Set-Cookie header, validate that the resulting sameSite attribute is one of 'Strict', 'Lax', or 'None' (exact, case-insensitive) before forwarding or relying on it.
- Record
AZL-91194- Updated
- 2026-11-02
OSVCLSA-2026-1784336934 No score
TuxCare security update for undici (3 CVEs)
TuxCare rebuilt undici to address 3 CVEs. Fixed in 5.28.5-tuxcare.5.
- Record
CLSA-2026-1784336934- Updated
- 2026-11-02
OSVCLSA-2026-1785204338 No score
TuxCare security update for undici (6 CVEs)
TuxCare rebuilt undici to address 6 CVEs. Fixed in 6.11.1-tuxcare.4.
- Record
CLSA-2026-1785204338- Updated
- 2026-11-02
OSVCLSA-2026-1786370674 No score
TuxCare security update for undici (2 CVEs)
TuxCare rebuilt undici to address 2 CVEs. Fixed in 5.29.0-tuxcare.5.
- Record
CLSA-2026-1786370674- Updated
- 2026-11-02
OSVCLSA-2026-1790542220 No score
TuxCare security update for undici (12 CVEs)
TuxCare rebuilt undici to address 12 CVEs. Fixed in 6.19.7-tuxcare.1.
- Record
CLSA-2026-1790542220- Updated
- 2026-11-02
OSVCLSA-2026-1791028079 No score
TuxCare security update for undici (11 CVEs)
TuxCare rebuilt undici to address 11 CVEs. Fixed in 6.19.5-tuxcare.2.
- Record
CLSA-2026-1791028079- Updated
- 2026-11-02
OSVCLSA-2026-1791973587 No score
TuxCare security update for undici (15 CVEs)
TuxCare rebuilt undici to address 15 CVEs. Fixed in 6.20.0-tuxcare.3.
- Record
CLSA-2026-1791973587- Updated
- 2026-11-02
OSVCLSA-2026-1792451423 No score
TuxCare security update for undici (5 CVEs)
TuxCare rebuilt undici to address 5 CVEs. Fixed in 7.24.4-tuxcare.1.
- Record
CLSA-2026-1792451423- Updated
- 2026-11-02
OSVCLSA-2026-1792867313 No score
TuxCare security update for undici-types (15 CVEs)
TuxCare rebuilt undici-types to address 15 CVEs. Fixed in 6.20.0-tuxcare.3.
- Record
CLSA-2026-1792867313- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:11121-1 No score
corepack24-24.17.0-1.1 on GA media
These are all security issues fixed in the corepack24-24.17.0-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2026:11121-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21058-1 No score
Security update for nodejs22
This update for nodejs22 fixes the following issues
Update to 22.23.0:
- CVE-2026-6733: undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpecvalue can lead to DoS (bsc#1266318). - CVE-2026-9679: undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding (bsc#1268477).
- CVE-2026-11525: undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (bsc#1268481).
- CVE-2026-12151: undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-21637: synchronous exceptions thrown during certain callbacks bypass the standard TLS error handling paths and can cause a denial of service (bsc#1256576).
- CVE-2026-21710: uncaught TypeError exception can cause a denial of service (bsc#1260455).
- CVE-2026-21713: timing side-channel in HMAC verification via memcmp can lead to potential MAC forgery (bsc#1260463).
- CVE-2026-21714: WINDOW_UPDATE frames on stream 0 can lead to memory leak (bsc#1260480).
- CVE-2026-21715: permission model bypass in realpathSync.native can allow file existence disclosure (bsc#1260482).
- CVE-2026-21716: promise-based FileHandle methods can be used to modify file permissions and ownership (bsc#1260462).
- CVE-2026-21717: crafted request can lead to hash collisions trivially predictable (bsc#1260494).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog parameters_set stack buffer overflow (bsc#1262274).
- CVE-2026-42338: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: Proxy credentials leaked in ERR_PROXY_TUNNEL error message (bsc#1268598).
- CVE-2026-48617: permission model enforcement bypass via
process.report.writeReport()path misvalidation (bsc#1268554). - CVE-2026-48618: Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: Unbounded memory growth in node:http2 clients via attacker-controlled ORIGIN frames (bsc#1268618).
- CVE-2026-48928: Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930: Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings (bsc#1268606).
- CVE-2026-48931: HTTP Response Queue Poisoning via TOCTOU Race Condition in http.Agent (bsc#1268611).
- CVE-2026-48933: Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48935: Permission Model bypass via FileHandle.utimes() in the promises API (bsc#1268609).
- CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555).
- Record
openSUSE-SU-2026:21058-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2026:21236-1 No score
Security update for nodejs24
This update for nodejs24 fixes the following issues
Update to version 24.18.0 (bsc#1269825).
Security issues fixed:
- CVE-2026-2581: undici: denial of service due to uncontrolled resource consumption (bsc#1268480).
- CVE-2026-6733: undici: response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpecvalue can lead to DoS (bsc#1266318). - CVE-2026-9678: undici: information disclosure due to improper
cache-controlheader parsing (bsc#1268478). - CVE-2026-9679: undici: HTTP header injection via
Set-Cookiepercent-decoding (bsc#1268477). - CVE-2026-11525: undici: weakening of cookie
SameSitepolicy due to incorrect parsing ofSet-Cookieheader (bsc#1268481). - CVE-2026-12151: undici: denial of service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog
parameters_setstack buffer overflow (bsc#1262274). - CVE-2026-42338: ip-address: cross-site scripting due to improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: proxy credentials leaked in
ERR_PROXY_TUNNELerror message (bsc#1268598). - CVE-2026-48617: permission model enforcement bypass via
process.report.writeReport()path misvalidation (bsc#1268554). - CVE-2026-48618: unicode dot separator handling can lead to TLS wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: unbounded memory growth in
node:http2clients via attacker-controlledORIGINframes (bsc#1268618). - CVE-2026-48928: uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930:
embedded-nulhostnames can lead to silent authority rebinding due toc-stringtruncation in resolver bindings (bsc#1268606). - CVE-2026-48931: HTTP response queue poisoning via TOCTOU race condition in
http.Agent(bsc#1268611). - CVE-2026-48933: WebCrypto AES integer overflow leads to remote process abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different
servernameleads to unauthorized connections (bsc#1268608). - CVE-2026-48935: permission model bypass via
FileHandle.utimes()in thepromisesAPI (bsc#1268609). - CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555).
Other updates and bugfixes:
- Version 24.18.0:
- doc: update
blockListstability status to release candidate - fs: support caller-supplied
readFile()buffers - http: close pre-request sockets in
closeIdleConnections - loader: implement package maps
- net: support
TCP_KEEPINTVLandTCP_KEEPCNTinsetKeepAlive - tls: add
certificateCompressionoption - vfs: dispatch
node:fs/promisesto mounted VFS instances - vfs: add minimal
node:vfssubsystem
- doc: update
- For changes in older versions, see https://github.com/nodejs/node/releases.
- Remove
update-alternativesfrom scriptlets if not available. - Explicitly
BuildRequireupdate-alternativesand mark it as being used in post/postun. - Add
-fno-lifetime-dsetoCXXFLAGSto avoid parallel/test-snapshot-reproducible testsuite failure with GCC 16.
- Record
openSUSE-SU-2026:21236-1- Updated
- 2026-11-02
OSVROOT-APP-NPM-CVE-2026-11525 No score
CVE-2026-11525 in undici - Patched by Root
Root has patched CVE-2026-11525 in the undici package for Root:npm. Multiple fixed versions available.
- Record
ROOT-APP-NPM-CVE-2026-11525- Updated
- 2026-11-05
OSVSUSE-SU-2026:22368-1 No score
Security update for nodejs22
This update for nodejs22 fixes the following issues
Update to 22.23.0:
- CVE-2026-6733: undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpecvalue can lead to DoS (bsc#1266318). - CVE-2026-9679: undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding (bsc#1268477).
- CVE-2026-11525: undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (bsc#1268481).
- CVE-2026-12151: undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-21637: synchronous exceptions thrown during certain callbacks bypass the standard TLS error handling paths and can cause a denial of service (bsc#1256576).
- CVE-2026-21710: uncaught TypeError exception can cause a denial of service (bsc#1260455).
- CVE-2026-21713: timing side-channel in HMAC verification via memcmp can lead to potential MAC forgery (bsc#1260463).
- CVE-2026-21714: WINDOW_UPDATE frames on stream 0 can lead to memory leak (bsc#1260480).
- CVE-2026-21715: permission model bypass in realpathSync.native can allow file existence disclosure (bsc#1260482).
- CVE-2026-21716: promise-based FileHandle methods can be used to modify file permissions and ownership (bsc#1260462).
- CVE-2026-21717: crafted request can lead to hash collisions trivially predictable (bsc#1260494).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog parameters_set stack buffer overflow (bsc#1262274).
- CVE-2026-42338: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: Proxy credentials leaked in ERR_PROXY_TUNNEL error message (bsc#1268598).
- CVE-2026-48617: permission model enforcement bypass via
process.report.writeReport()path misvalidation (bsc#1268554). - CVE-2026-48618: Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: Unbounded memory growth in node:http2 clients via attacker-controlled ORIGIN frames (bsc#1268618).
- CVE-2026-48928: Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930: Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings (bsc#1268606).
- CVE-2026-48931: HTTP Response Queue Poisoning via TOCTOU Race Condition in http.Agent (bsc#1268611).
- CVE-2026-48933: Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48935: Permission Model bypass via FileHandle.utimes() in the promises API (bsc#1268609).
- CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555).
- Record
SUSE-SU-2026:22368-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:22565-1 No score
Security update for nodejs24
This update for nodejs24 fixes the following issues
Update to version 24.18.0 (bsc#1269825).
Security issues fixed:
- CVE-2026-2581: undici: denial of service due to uncontrolled resource consumption (bsc#1268480).
- CVE-2026-6733: undici: response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpecvalue can lead to DoS (bsc#1266318). - CVE-2026-9678: undici: information disclosure due to improper
cache-controlheader parsing (bsc#1268478). - CVE-2026-9679: undici: HTTP header injection via
Set-Cookiepercent-decoding (bsc#1268477). - CVE-2026-11525: undici: weakening of cookie
SameSitepolicy due to incorrect parsing ofSet-Cookieheader (bsc#1268481). - CVE-2026-12151: undici: denial of service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog
parameters_setstack buffer overflow (bsc#1262274). - CVE-2026-42338: ip-address: cross-site scripting due to improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: proxy credentials leaked in
ERR_PROXY_TUNNELerror message (bsc#1268598). - CVE-2026-48617: permission model enforcement bypass via
process.report.writeReport()path misvalidation (bsc#1268554). - CVE-2026-48618: unicode dot separator handling can lead to TLS wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: unbounded memory growth in
node:http2clients via attacker-controlledORIGINframes (bsc#1268618). - CVE-2026-48928: uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930:
embedded-nulhostnames can lead to silent authority rebinding due toc-stringtruncation in resolver bindings (bsc#1268606). - CVE-2026-48931: HTTP response queue poisoning via TOCTOU race condition in
http.Agent(bsc#1268611). - CVE-2026-48933: WebCrypto AES integer overflow leads to remote process abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different
servernameleads to unauthorized connections (bsc#1268608). - CVE-2026-48935: permission model bypass via
FileHandle.utimes()in thepromisesAPI (bsc#1268609). - CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555).
Other updates and bugfixes:
- Version 24.18.0:
- doc: update
blockListstability status to release candidate - fs: support caller-supplied
readFile()buffers - http: close pre-request sockets in
closeIdleConnections - loader: implement package maps
- net: support
TCP_KEEPINTVLandTCP_KEEPCNTinsetKeepAlive - tls: add
certificateCompressionoption - vfs: dispatch
node:fs/promisesto mounted VFS instances - vfs: add minimal
node:vfssubsystem
- doc: update
- For changes in older versions, see https://github.com/nodejs/node/releases.
- Remove
update-alternativesfrom scriptlets if not available. - Explicitly
BuildRequireupdate-alternativesand mark it as being used in post/postun. - Add
-fno-lifetime-dsetoCXXFLAGSto avoid parallel/test-snapshot-reproducible testsuite failure with GCC 16.
- Record
SUSE-SU-2026:22565-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:2633-1 No score
Security update for nodejs24
This update for nodejs24 fixes the following issues
Update to 24.17.0:
- CVE-2026-2581: undici: Undici: Denial of Service due to uncontrolled resource consumption (bsc#1268480).
- CVE-2026-6733: undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpecvalue can lead to DoS (bsc#1266318). - CVE-2026-9678: undici: Undici: Information disclosure due to improper cache-control header parsing (bsc#1268478).
- CVE-2026-9679: undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding (bsc#1268477).
- CVE-2026-11525: undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (bsc#1268481).
- CVE-2026-12151: undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog parameters_set stack buffer overflow (bsc#1262274).
- CVE-2026-42338: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: Proxy credentials leaked in ERR_PROXY_TUNNEL error message (bsc#1268598).
- CVE-2026-48617: permission model enforcement bypass via
process.report.writeReport()path misvalidation (bsc#1268554). - CVE-2026-48618: Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: Unbounded memory growth in node:http2 clients via attacker-controlled ORIGIN frames (bsc#1268618).
- CVE-2026-48928: Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930: Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings (bsc#1268606).
- CVE-2026-48931: HTTP Response Queue Poisoning via TOCTOU Race Condition in http.Agent (bsc#1268611).
- CVE-2026-48933: Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48935: Permission Model bypass via FileHandle.utimes() in the promises API (bsc#1268609).
- CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555).
- Record
SUSE-SU-2026:2633-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:2647-1 No score
Security update for nodejs22
This update for nodejs22 fixes the following issues
Update to 22.23.0:
- CVE-2026-6733: undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpecvalue can lead to DoS (bsc#1266318). - CVE-2026-9679: undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding (bsc#1268477).
- CVE-2026-11525: undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (bsc#1268481).
- CVE-2026-12151: undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog parameters_set stack buffer overflow (bsc#1262274).
- CVE-2026-42338: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: Proxy credentials leaked in ERR_PROXY_TUNNEL error message (bsc#1268598).
- CVE-2026-48617: permission model enforcement bypass via
process.report.writeReport()path misvalidation (bsc#1268554). - CVE-2026-48618: Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: Unbounded memory growth in node:http2 clients via attacker-controlled ORIGIN frames (bsc#1268618).
- CVE-2026-48928: Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930: Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings (bsc#1268606).
- CVE-2026-48931: HTTP Response Queue Poisoning via TOCTOU Race Condition in http.Agent (bsc#1268611).
- CVE-2026-48933: Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48935: Permission Model bypass via FileHandle.utimes() in the promises API (bsc#1268609).
- CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555).
- Record
SUSE-SU-2026:2647-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:2695-1 No score
Security update for nodejs22
This update for nodejs22 fixes the following issues:
- CVE-2026-48618: tls: normalize hostname for server identity checks (bsc#1268593).
- CVE-2026-48933: crypto: guard WebCrypto cipher output length (bsc#1268592).
- CVE-2026-48615: lib,test: redact proxy credentials in tunnel errors (bsc#1268598).
- CVE-2026-48619: http2: cap originSet size to prevent unbounded memory growth (bsc#1268618).
- CVE-2026-48928: tls: fix case-sensitive SNI context matching (bsc#1268605).
- CVE-2026-48930: dns,net: reject hostnames with embedded NUL bytes (bsc#1268606).
- CVE-2026-48934: tls: bind reusable sessions to authenticated host (bsc#1268608).
- CVE-2026-48617: permission: handle process.chdir on writereport (bsc#1268554).
- CVE-2026-48931: http: fix response queue poisoning in http.Agent (bsc#1268611).
- CVE-2026-48935: permission: disable FileHandle utimes with permission model (bsc#1268609).
- CVE-2026-48937: http2: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555). - CVE-2026-12151: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-6733: undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery ( bsc#1268479).
- CVE-2026-9679: undici: vulnerable to HTTP header injection via Set-Cookie percent-decoding ( bsc#1268477).
- CVE-2026-11525: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (bsc#1268481).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog parameters_set stack buffer overflow. (bsc#1262274).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpec( bsc#1266318). - CVE-2026-42338: ip-address: Cross-site scripting via improper HTML escaping of untrusted input (bsc#1268097).
- Record
SUSE-SU-2026:2695-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:3929-1 No score
Security update for nodejs20
This update for nodejs20 fixes the following issues:
- CVE-2025-22150: undici: predictable random values used when defining the boundary for a
multipart/form-datarequest (bsc#1236258). - CVE-2026-6733: undici: response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpecvalue can lead to DoS (bsc#1266318). - CVE-2026-9679: undici: HTTP header injection via
Set-Cookiepercent-decoding (bsc#1268477). - CVE-2026-11525: undici: weakening of cookie
SameSitepolicy due to incorrect parsing ofSet-Cookieheader (bsc#1268481). - CVE-2026-12151: undici: denial of service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-16728: undici: downstream response desynchronization via retry interceptor (bsc#1273593).
- CVE-2026-16729: undici:
setCookiefunction does not fully sanitize cookie attributes (bsc#1273591). - CVE-2026-22036: undici: unbounded decompression chain in HTTP responses via
Content-Encodingmay lead to resource exhaustion (bsc#1256848). - CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog
parameters_setstack buffer overflow (bsc#1262274). - CVE-2026-42338: ip-address: cross-site scripting via improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: proxy credentials leaked in
ERR_PROXY_TUNNELerror message (bsc#1268598). - CVE-2026-48617: permission model enforcement bypass via
process.report.writeReport()path misvalidation (bsc#1268554). - CVE-2026-48618: unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: unbounded memory growth in
node:http2clients via attacker-controlledORIGINframes (bsc#1268618). - CVE-2026-48928: uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930:
embedded-nulhostnames can lead to silent authority rebinding due toc-stringtruncation in resolver bindings (bsc#1268606). - CVE-2026-48931: HTTP response queue poisoning via TOCTOU race condition in
http.Agent(bsc#1268611). - CVE-2026-48933: WebCrypto AES integer overflow leads to remote process abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48935: permission model bypass via
FileHandle.utimes()in thepromisesAPI (bsc#1268609). - CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555). - CVE-2026-54272: ip-address: misclassification of IPv4-mapped/NAT64 IPv6 addresses allows for bypass of SSRF and trust- boundary checks (bsc#1272882).
- CVE-2026-56846: HTTP/2 retained headers can bypass
maxSessionMemorylimits (bsc#1272941). - CVE-2026-56847: permission model allows trace events to write outside the allowlist (bsc#1272949).
- CVE-2026-56848: HTTP/2 re-entrant send can cause heap use-after-free (bsc#1272942).
- CVE-2026-56850: HTTPS agent can reuse mTLS identities across PFX certificates (bsc#1272944).
- CVE-2026-58039: permission model allows process reports to write outside the allowlist (bsc#1272950).
- CVE-2026-58040: HTTPS agent session reuse can skip hostname verification (bsc#1272945).
- CVE-2026-58042:
dns.resolveAny()can abort on DNS responses with manyArecords (bsc#1272947). - CVE-2026-58043: permission model path matching can over-grant filesystem access (bsc#1272943).
- CVE-2026-58044: HTTP parser header truncation can enable request smuggling (bsc#1272951).
- CVE-2026-58045:
node:zlibsync APIs can crash on spoofedTypedArraylength (bsc#1272948). - CVE-2026-69192: ip-address:
Address4…
- Record
SUSE-SU-2026:3929-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:3930-1 No score
Security update for nodejs20
This update for nodejs20 fixes the following issues:
- CVE-2025-22150: undici: predictable random values used when defining the boundary for a
multipart/form-datarequest (bsc#1236258). - CVE-2026-6733: undici: response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9496: pacote: excessive CPU consumption in
addGitShawhen processing a specially craftedspec.rawSpecvalue can lead to DoS (bsc#1266318). - CVE-2026-9679: undici: HTTP header injection via
Set-Cookiepercent-decoding (bsc#1268477). - CVE-2026-11525: undici: weakening of cookie
SameSitepolicy due to incorrect parsing ofSet-Cookieheader (bsc#1268481). - CVE-2026-12151: undici: denial of service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-16728: undici: downstream response desynchronization via retry interceptor (bsc#1273593).
- CVE-2026-16729: undici:
setCookiefunction does not fully sanitize cookie attributes (bsc#1273591). - CVE-2026-22036: undici: unbounded decompression chain in HTTP responses via
Content-Encodingmay lead to resource exhaustion (bsc#1256848). - CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-40170: ngtcp2: qlog
parameters_setstack buffer overflow (bsc#1262274). - CVE-2026-42338: ip-address: cross-site scripting via improper HTML escaping of untrusted input (bsc#1268097).
- CVE-2026-48615: proxy credentials leaked in
ERR_PROXY_TUNNELerror message (bsc#1268598). - CVE-2026-48617: permission model enforcement bypass via
process.report.writeReport()path misvalidation (bsc#1268554). - CVE-2026-48618: unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: unbounded memory growth in
node:http2clients via attacker-controlledORIGINframes (bsc#1268618). - CVE-2026-48928: uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930:
embedded-nulhostnames can lead to silent authority rebinding due toc-stringtruncation in resolver bindings (bsc#1268606). - CVE-2026-48931: HTTP response queue poisoning via TOCTOU race condition in
http.Agent(bsc#1268611). - CVE-2026-48933: WebCrypto AES integer overflow leads to remote process abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48935: permission model bypass via
FileHandle.utimes()in thepromisesAPI (bsc#1268609). - CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555). - CVE-2026-54272: ip-address: misclassification of IPv4-mapped/NAT64 IPv6 addresses allows for bypass of SSRF and trust- boundary checks (bsc#1272882).
- CVE-2026-56846: HTTP/2 retained headers can bypass
maxSessionMemorylimits (bsc#1272941). - CVE-2026-56847: permission model allows trace events to write outside the allowlist (bsc#1272949).
- CVE-2026-56848: HTTP/2 re-entrant send can cause heap use-after-free (bsc#1272942).
- CVE-2026-56850: HTTPS agent can reuse mTLS identities across PFX certificates (bsc#1272944).
- CVE-2026-58039: permission model allows process reports to write outside the allowlist (bsc#1272950).
- CVE-2026-58040: HTTPS agent session reuse can skip hostname verification (bsc#1272945).
- CVE-2026-58042:
dns.resolveAny()can abort on DNS responses with manyArecords (bsc#1272947). - CVE-2026-58043: permission model path matching can over-grant filesystem access (bsc#1272943).
- CVE-2026-58044: HTTP parser header truncation can enable request smuggling (bsc#1272951).
- CVE-2026-58045:
node:zlibsync APIs can crash on spoofedTypedArraylength (bsc#1272948). - CVE-2026-69192: ip-address:
Address4…
- Record
SUSE-SU-2026:3930-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:4248-1 No score
Security update for nodejs18
This update for nodejs18 fixes the following issues:
- CVE-2025-22150: undici: insufficiently random values used when defining the boundary for a multipart/form-data request (bsc#1236258).
- CVE-2025-23166: improper error handling in async cryptographic operations crashes process (bsc#1243218).
- CVE-2025-23167: llhttp: improper HTTP header block termination in llhttp (bsc#1243220).
- CVE-2025-55131: timeout-based race conditions allow for allocations that contain leftover data from previous operations and lead to exposure of in-process secrets (bsc#1256570).
- CVE-2025-59465: malformed HTTP/2 HEADERS frame with invalid HPACK data can cause a crash due to an unhandled error (bsc#1256573).
- CVE-2025-59466: uncatchable 'Maximum call stack size exceeded' error when
async_hooks.createHook()is enabled can lead to crash (bsc#1256574). - CVE-2025-62408: c-ares 1.32.3-1.34.5 use after free() (bsc#1254738).
- CVE-2026-6733: undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9679: undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding (bsc#1268477).
- CVE-2026-11525: undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (bsc#1268481).
- CVE-2026-12151: undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-15157: No validation of the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher (bsc#1272958).
- CVE-2026-16728: undici: downstream response desynchronization via retry interceptor (bsc#1273593).
- CVE-2026-16729: undici: undici's setCookie function does not fully sanitize cookie attributes (bsc#1273591).
- CVE-2026-21637: synchronous exceptions thrown during certain callbacks bypass the standard TLS error handling paths and can cause a denial of service (bsc#1256576).
- CVE-2026-21710: uncaught TypeError exception can cause a denial of service (bsc#1260455).
- CVE-2026-21713: timing side-channel in HMAC verification via memcmp can lead to potential MAC forgery (bsc#1260463).
- CVE-2026-21714: WINDOW_UPDATE frames on stream 0 can lead to memory leak (bsc#1260480).
- CVE-2026-21717: crafted request can lead to hash collisions trivially predictable (bsc#1260494).
- CVE-2026-22036: undici: unbounded decompression chain in HTTP responses via Content-Encoding may lead to resource exhaustion (bsc#1256848).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-48618: Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: Unbounded memory growth in node:http2 clients via attacker-controlled ORIGIN frames (bsc#1268618).
- CVE-2026-48928: Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930: Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings (bsc#1268606).
- CVE-2026-48931: HTTP Response Queue Poisoning via TOCTOU Race Condition in http.Agent (bsc#1268611).
- CVE-2026-48933: Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48935: Permission Model bypass via FileHandle.utimes() in the promises API (bsc#1268609).
- CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555). - CVE-2026-56846: HTTP/2 retained headers can bypass maxSessionMemory limits (bsc#1272941).
- CVE-2026-56848: HTTP/2 re-entrant send can cause heap-use-after-free (bsc#1272942).
- CVE-2026-56850: HTTPS…
- Record
SUSE-SU-2026:4248-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:4261-1 No score
Security update for nodejs18
This update for nodejs18 fixes the following issues:
- CVE-2025-22150: undici: insufficiently random values used when defining the boundary for a multipart/form-data request (bsc#1236258).
- CVE-2025-23166: improper error handling in async cryptographic operations crashes process (bsc#1243218).
- CVE-2025-23167: llhttp: improper HTTP header block termination in llhttp (bsc#1243220).
- CVE-2025-55131: timeout-based race conditions allow for allocations that contain leftover data from previous operations and lead to exposure of in-process secrets (bsc#1256570).
- CVE-2025-59465: malformed HTTP/2 HEADERS frame with invalid HPACK data can cause a crash due to an unhandled error (bsc#1256573).
- CVE-2025-59466: uncatchable 'Maximum call stack size exceeded' error when
async_hooks.createHook()is enabled can lead to crash (bsc#1256574). - CVE-2025-62408: c-ares 1.32.3-1.34.5 use after free() (bsc#1254738).
- CVE-2026-6733: undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-9679: undici: undici vulnerable to HTTP header injection via Set-Cookie percent-decoding (bsc#1268477).
- CVE-2026-11525: undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (bsc#1268481).
- CVE-2026-12151: undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-15157: No validation of the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher (bsc#1272958).
- CVE-2026-16728: undici: downstream response desynchronization via retry interceptor (bsc#1273593).
- CVE-2026-16729: undici: undici's setCookie function does not fully sanitize cookie attributes (bsc#1273591).
- CVE-2026-21637: synchronous exceptions thrown during certain callbacks bypass the standard TLS error handling paths and can cause a denial of service (bsc#1256576).
- CVE-2026-21710: uncaught TypeError exception can cause a denial of service (bsc#1260455).
- CVE-2026-21713: timing side-channel in HMAC verification via memcmp can lead to potential MAC forgery (bsc#1260463).
- CVE-2026-21714: WINDOW_UPDATE frames on stream 0 can lead to memory leak (bsc#1260480).
- CVE-2026-21717: crafted request can lead to hash collisions trivially predictable (bsc#1260494).
- CVE-2026-22036: undici: unbounded decompression chain in HTTP responses via Content-Encoding may lead to resource exhaustion (bsc#1256848).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-48618: Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: Unbounded memory growth in node:http2 clients via attacker-controlled ORIGIN frames (bsc#1268618).
- CVE-2026-48928: Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930: Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings (bsc#1268606).
- CVE-2026-48931: HTTP Response Queue Poisoning via TOCTOU Race Condition in http.Agent (bsc#1268611).
- CVE-2026-48933: Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48935: Permission Model bypass via FileHandle.utimes() in the promises API (bsc#1268609).
- CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555). - CVE-2026-56846: HTTP/2 retained headers can bypass maxSessionMemory limits (bsc#1272941).
- CVE-2026-56848: HTTP/2 re-entrant send can cause heap-use-after-free (bsc#1272942).
- CVE-2026-56850: HTTPS…
- Record
SUSE-SU-2026:4261-1- Updated
- 2026-11-02
OSVSUSE-SU-2026:4355-1 No score
Security update for nodejs16
This update for nodejs16 fixes the following issues:
- CVE-2025-23085: memory leak when remote peer abruptly closes socket without sending GOAWAY notification (bsc#1236250).
- CVE-2025-23166: improper error handling in async cryptographic operations crashes process (bsc#1243218).
- CVE-2025-23167: llhttp: improper HTTP header block termination in llhttp (bsc#1243220).
- CVE-2025-55131: timeout-based race conditions allow for allocations that contain leftover data from previous operations and lead to exposure of in-process secrets (bsc#1256570).
- CVE-2025-59465: malformed HTTP/2 HEADERS frame with invalid HPACK data can cause a crash due to an unhandled error (bsc#1256573).
- CVE-2025-59466: uncatchable 'Maximum call stack size exceeded' error when
async_hooks.createHook()is enabled can lead to crash (bsc#1256574). - CVE-2026-6733: undici: Undici: Response queue poisoning on reused keep-alive sockets can lead to incorrect response delivery (bsc#1268479).
- CVE-2026-11525: undici: undici: Weakening of cookie SameSite policy due to incorrect parsing of Set-Cookie header (bsc#1268481).
- CVE-2026-12151: undici: undici: Denial of Service due to unbounded memory growth via WebSocket frames (bsc#1268482).
- CVE-2026-15157: No validation of the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher (bsc#1272958).
- CVE-2026-21637: synchronous exceptions thrown during certain callbacks bypass the standard TLS error handling paths and can cause a denial of service (bsc#1256576).
- CVE-2026-21710: uncaught TypeError exception can cause a denial of service (bsc#1260455).
- CVE-2026-21713: timing side-channel in HMAC verification via memcmp can lead to potential MAC forgery (bsc#1260463).
- CVE-2026-21714: WINDOW_UPDATE frames on stream 0 can lead to memory leak (bsc#1260480).
- CVE-2026-22036: undici: unbounded decompression chain in HTTP responses via Content-Encoding may lead to resource exhaustion (bsc#1256848).
- CVE-2026-27135: nghttp2: assertion failure due to missing state validation can lead to DoS (bsc#1259853).
- CVE-2026-48618: Node.js unicode dot separator handling can lead to tls wildcard-depth authentication bypass due to resolver and verifier hostname normalization mismatch (bsc#1268593).
- CVE-2026-48619: Unbounded memory growth in node:http2 clients via attacker-controlled ORIGIN frames (bsc#1268618).
- CVE-2026-48928: Uppercase sni context matching can lead to mtls authorization bypass due to case-sensitive hostname matching (bsc#1268605).
- CVE-2026-48930: Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings (bsc#1268606).
- CVE-2026-48931: HTTP Response Queue Poisoning via TOCTOU Race Condition in http.Agent (bsc#1268611).
- CVE-2026-48933: Node.js WebCrypto AES Integer Overflow Leads to Remote Process Abort (bsc#1268592).
- CVE-2026-48934: TLS host identity verification bypass via session reuse with different servername leads to unauthorized connections (bsc#1268608).
- CVE-2026-48937: servers keep accepting data even after sending a
GOAWAYframe (bsc#1268555). - CVE-2026-56846: HTTP/2 retained headers can bypass maxSessionMemory limits (bsc#1272941).
- CVE-2026-56848: HTTP/2 re-entrant send can cause heap-use-after-free (bsc#1272942).
- CVE-2026-56850: HTTPS Agent can reuse mTLS identities across PFX certificates (bsc#1272944).
- CVE-2026-58040: HTTPS Agent session reuse can skip hostname verification (bsc#1272945).
- CVE-2026-58042: dns.resolveAny() can abort on DNS responses with many A records (bsc#1272947).
- CVE-2026-58044: HTTP parser header truncation can enable request smuggling (bsc#1272951).
- CVE-2026-58045: node:zlib sync APIs can crash on spoofed TypedArray length (bsc#1272948).
- Record
SUSE-SU-2026:4355-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
undicinpm |
before 6.27.0 | 6.27.0 |
undicinpm |
7.0.0 up to 7.28.0 | 7.28.0 |
undicinpm |
8.0.0 up to 8.5.0 | 8.5.0 |
nodejs24AlmaLinux:10 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-develAlmaLinux:10 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-docsAlmaLinux:10 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-full-i18nAlmaLinux:10 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-libsAlmaLinux:10 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-npmAlmaLinux:10 |
before 1:11.16.0-1.24.18.0.1.el10_2 | 1:11.16.0-1.24.18.0.1.el10_2 |
nodejsAlmaLinux:10 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
Show 206 moreShow less
| Package | Affected | Fixed |
|---|---|---|
nodejs-develAlmaLinux:10 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-docsAlmaLinux:10 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-full-i18nAlmaLinux:10 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-libsAlmaLinux:10 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-npmAlmaLinux:10 |
before 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 |
nodejsAlmaLinux:9 |
before 1:24.18.0-1.module_el9.8.0+277+61fc613e | 1:24.18.0-1.module_el9.8.0+277+61fc613e |
nodejs-develAlmaLinux:9 |
before 1:24.18.0-1.module_el9.8.0+277+61fc613e | 1:24.18.0-1.module_el9.8.0+277+61fc613e |
nodejs-docsAlmaLinux:9 |
before 1:24.18.0-1.module_el9.8.0+277+61fc613e | 1:24.18.0-1.module_el9.8.0+277+61fc613e |
nodejs-full-i18nAlmaLinux:9 |
before 1:24.18.0-1.module_el9.8.0+277+61fc613e | 1:24.18.0-1.module_el9.8.0+277+61fc613e |
nodejs-libsAlmaLinux:9 |
before 1:24.18.0-1.module_el9.8.0+277+61fc613e | 1:24.18.0-1.module_el9.8.0+277+61fc613e |
nodejs-nodemonAlmaLinux:9 |
before 3.0.3-3.module_el9.7.0+209+ecf6523e | 3.0.3-3.module_el9.7.0+209+ecf6523e |
nodejs-packagingAlmaLinux:9 |
before 2021.06-6.module_el9.7.0+209+ecf6523e | 2021.06-6.module_el9.7.0+209+ecf6523e |
nodejs-packaging-bundlerAlmaLinux:9 |
before 2021.06-6.module_el9.7.0+209+ecf6523e | 2021.06-6.module_el9.7.0+209+ecf6523e |
npmAlmaLinux:9 |
before 1:11.16.0-1.24.18.0.1.module_el9.8.0+277+61fc613e | 1:11.16.0-1.24.18.0.1.module_el9.8.0+277+61fc613e |
v8-13.6-develAlmaLinux:9 |
before 3:13.6.233.17-1.24.18.0.1.module_el9.8.0+277+61fc613e | 3:13.6.233.17-1.24.18.0.1.module_el9.8.0+277+61fc613e |
nodejsAlmaLinux:9 |
before 1:22.23.1-1.module_el9.8.0+276+8b329b47 | 1:22.23.1-1.module_el9.8.0+276+8b329b47 |
nodejs-develAlmaLinux:9 |
before 1:22.23.1-1.module_el9.8.0+276+8b329b47 | 1:22.23.1-1.module_el9.8.0+276+8b329b47 |
nodejs-docsAlmaLinux:9 |
before 1:22.23.1-1.module_el9.8.0+276+8b329b47 | 1:22.23.1-1.module_el9.8.0+276+8b329b47 |
nodejs-full-i18nAlmaLinux:9 |
before 1:22.23.1-1.module_el9.8.0+276+8b329b47 | 1:22.23.1-1.module_el9.8.0+276+8b329b47 |
nodejs-libsAlmaLinux:9 |
before 1:22.23.1-1.module_el9.8.0+276+8b329b47 | 1:22.23.1-1.module_el9.8.0+276+8b329b47 |
nodejs-nodemonAlmaLinux:9 |
before 3.0.1-1.module_el9.7.0+208+fb06c0ab | 3.0.1-1.module_el9.7.0+208+fb06c0ab |
nodejs-packagingAlmaLinux:9 |
before 2021.06-6.module_el9.7.0+227+12323393 | 2021.06-6.module_el9.7.0+227+12323393 |
nodejs-packaging-bundlerAlmaLinux:9 |
before 2021.06-6.module_el9.7.0+227+12323393 | 2021.06-6.module_el9.7.0+227+12323393 |
npmAlmaLinux:9 |
before 1:10.9.8-1.22.23.1.1.module_el9.8.0+276+8b329b47 | 1:10.9.8-1.22.23.1.1.module_el9.8.0+276+8b329b47 |
v8-12.4-develAlmaLinux:9 |
before 3:12.4.254.21-1.22.23.1.1.module_el9.8.0+276+8b329b47 | 3:12.4.254.21-1.22.23.1.1.module_el9.8.0+276+8b329b47 |
nodejsAlmaLinux:8 |
before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
nodejs-develAlmaLinux:8 |
before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
nodejs-docsAlmaLinux:8 |
before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
nodejs-full-i18nAlmaLinux:8 |
before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
nodejs-libsAlmaLinux:8 |
before 1:24.18.0-1.module_el8.10.0+4228+2938bc94 | 1:24.18.0-1.module_el8.10.0+4228+2938bc94 |
nodejs-nodemonAlmaLinux:8 |
before 3.0.3-1.module_el8.10.0+4061+f8ceeab9 | 3.0.3-1.module_el8.10.0+4061+f8ceeab9 |
nodejs-packagingAlmaLinux:8 |
before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
nodejs-packaging-bundlerAlmaLinux:8 |
before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
npmAlmaLinux:8 |
before 1:11.16.0-1.24.18.0.1.module_el8.10.0+4228+2938bc94 | 1:11.16.0-1.24.18.0.1.module_el8.10.0+4228+2938bc94 |
v8-13.6-develAlmaLinux:8 |
before 3:13.6.233.17-1.24.18.0.1.module_el8.10.0+4228+2938bc94 | 3:13.6.233.17-1.24.18.0.1.module_el8.10.0+4228+2938bc94 |
nodejsAlmaLinux:8 |
before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
nodejs-develAlmaLinux:8 |
before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
nodejs-docsAlmaLinux:8 |
before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
nodejs-full-i18nAlmaLinux:8 |
before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
nodejs-libsAlmaLinux:8 |
before 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 | 1:22.23.1-1.module_el8.10.0+4231+1bf2f855 |
nodejs-nodemonAlmaLinux:8 |
before 3.0.1-1.module_el8.10.0+3956+47c9ee9f | 3.0.1-1.module_el8.10.0+3956+47c9ee9f |
nodejs-packagingAlmaLinux:8 |
before 2021.06-6.module_el8.10.0+4158+e796f37f | 2021.06-6.module_el8.10.0+4158+e796f37f |
nodejs-packaging-bundlerAlmaLinux:8 |
before 2021.06-6.module_el8.10.0+4158+e796f37f | 2021.06-6.module_el8.10.0+4158+e796f37f |
npmAlmaLinux:8 |
before 1:10.9.8-1.22.23.1.1.module_el8.10.0+4231+1bf2f855 | 1:10.9.8-1.22.23.1.1.module_el8.10.0+4231+1bf2f855 |
v8-12.4-develAlmaLinux:8 |
before 3:12.4.254.21-1.22.23.1.1.module_el8.10.0+4231+1bf2f855 | 3:12.4.254.21-1.22.23.1.1.module_el8.10.0+4231+1bf2f855 |
nodejsAzure Linux:3 |
before 24.18.1-1 | 24.18.1-1 |
undiciTuxCare:npm |
5.28.5-tuxcare.0 up to 5.28.5-tuxcare.5, plus listed versions 5.28.55.28.5-tuxcare.15.28.5-tuxcare.25.28.5-tuxcare.35.28.5-tuxcare.4 |
5.28.5-tuxcare.5 |
undiciTuxCare:npm |
6.11.1-tuxcare.0 up to 6.11.1-tuxcare.4, plus listed versions 6.11.16.11.1-tuxcare.16.11.1-tuxcare.26.11.1-tuxcare.3 |
6.11.1-tuxcare.4 |
undiciTuxCare:npm |
5.29.0-tuxcare.0 up to 5.29.0-tuxcare.5, plus listed versions 5.29.05.29.0-tuxcare.15.29.0-tuxcare.25.29.0-tuxcare.35.29.0-tuxcare.4 |
5.29.0-tuxcare.5 |
undiciTuxCare:npm |
6.19.7-tuxcare.0 up to 6.19.7-tuxcare.1, plus listed versions 6.19.7 |
6.19.7-tuxcare.1 |
undiciTuxCare:npm |
6.19.5-tuxcare.0 up to 6.19.5-tuxcare.2, plus listed versions 6.19.56.19.5-tuxcare.1 |
6.19.5-tuxcare.2 |
undiciTuxCare:npm |
6.20.0-tuxcare.0 up to 6.20.0-tuxcare.3, plus listed versions 6.20.06.20.0-tuxcare.16.20.0-tuxcare.2 |
6.20.0-tuxcare.3 |
undiciTuxCare:npm |
7.24.4-tuxcare.0 up to 7.24.4-tuxcare.1, plus listed versions 7.24.4 |
7.24.4-tuxcare.1 |
undici-typesTuxCare:npm |
6.20.0-tuxcare.0 up to 6.20.0-tuxcare.3, plus listed versions 6.20.06.20.0-tuxcare.16.20.0-tuxcare.2 |
6.20.0-tuxcare.3 |
node-undiciDebian:12 |
All versions, plus listed versions 5.15.0+dfsg1+~cs20.10.9.3-15.15.0+dfsg1+~cs20.10.9.3-1+deb12u15.15.0+dfsg1+~cs20.10.9.3-1+deb12u25.15.0+dfsg1+~cs20.10.9.3-1+deb12u35.15.0+dfsg1+~cs20.10.9.3-1+deb12u4 Show 35 moreShow less5.19.1+dfsg1+~cs20.10.9.5-15.19.1+dfsg1+~cs20.10.9.5-25.22.1+dfsg1+~cs20.10.10.2-15.26.3+dfsg1+~cs23.10.12-15.26.3+dfsg1+~cs23.10.12-25.26.3+dfsg1+~cs23.10.12-35.28.0+dfsg1+~cs23.11.12.3-15.28.0+dfsg1+~cs23.11.12.3-25.28.2+dfsg1+~cs23.11.12.3-15.28.2+dfsg1+~cs23.11.12.3-25.28.2+dfsg1+~cs23.11.12.3-35.28.2+dfsg1+~cs23.11.12.3-45.28.2+dfsg1+~cs23.11.12.3-55.28.2+dfsg1+~cs23.11.12.3-65.28.4+dfsg1+~cs23.12.11-15.28.4+dfsg1+~cs23.12.11-27.1.0+dfsg1+~cs24.12.10-17.15.0+dfsg+~cs3.2.0-17.15.0+dfsg+~cs3.2.0-37.16.0+dfsg+~cs3.2.0-17.16.0+dfsg+~cs3.2.0-27.18.2+dfsg+~cs3.2.0-17.2.3+dfsg1+~cs24.12.11-17.2.3+dfsg1+~cs24.12.11-27.24.5+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-27.24.6+dfsg+~cs3.2.0-37.3.0+dfsg1+~cs24.12.11-17.3.0+dfsg1+~cs24.12.11-28.10.2+dfsg+~cs3.2.2-18.5.0+dfsg+~cs3.2.0-18.5.0+dfsg+~cs3.2.0-28.5.0+dfsg+~cs3.2.0-38.9.0+dfsg+~cs3.2.0-1 |
None known |
node-undiciDebian:13 |
All versions, plus listed versions 7.15.0+dfsg+~cs3.2.0-17.15.0+dfsg+~cs3.2.0-37.16.0+dfsg+~cs3.2.0-17.16.0+dfsg+~cs3.2.0-27.18.2+dfsg+~cs3.2.0-1 Show 11 moreShow less7.24.5+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-27.24.6+dfsg+~cs3.2.0-37.3.0+dfsg1+~cs24.12.11-17.3.0+dfsg1+~cs24.12.11-28.10.2+dfsg+~cs3.2.2-18.5.0+dfsg+~cs3.2.0-18.5.0+dfsg+~cs3.2.0-28.5.0+dfsg+~cs3.2.0-38.9.0+dfsg+~cs3.2.0-1 |
None known |
node-undiciDebian:14 |
before 8.5.0+dfsg+~cs3.2.0-1, plus listed versions 7.15.0+dfsg+~cs3.2.0-17.15.0+dfsg+~cs3.2.0-37.16.0+dfsg+~cs3.2.0-17.16.0+dfsg+~cs3.2.0-27.18.2+dfsg+~cs3.2.0-1 Show 6 moreShow less7.24.5+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-17.24.6+dfsg+~cs3.2.0-27.24.6+dfsg+~cs3.2.0-37.3.0+dfsg1+~cs24.12.11-17.3.0+dfsg1+~cs24.12.11-2 |
8.5.0+dfsg+~cs3.2.0-1 |
nodejs24Red Hat:enterprise_linux:10.2 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-debuginfoRed Hat:enterprise_linux:10.2 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-debugsourceRed Hat:enterprise_linux:10.2 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-develRed Hat:enterprise_linux:10.2 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-docsRed Hat:enterprise_linux:10.2 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-full-i18nRed Hat:enterprise_linux:10.2 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-libsRed Hat:enterprise_linux:10.2 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-libs-debuginfoRed Hat:enterprise_linux:10.2 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs24-npmRed Hat:enterprise_linux:10.2 |
before 1:11.16.0-1.24.18.0.1.el10_2 | 1:11.16.0-1.24.18.0.1.el10_2 |
nodejsRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-debuginfoRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-develRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-docsRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-full-i18nRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-libsRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-libs-debuginfoRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-npmRed Hat:enterprise_linux:10.2 |
before 1:10.9.8-1.22.23.1.2.el10_2 | 1:10.9.8-1.22.23.1.2.el10_2 |
nodejs22Red Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs22-debuginfoRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs22-debugsourceRed Hat:enterprise_linux:10.2 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejsRed Hat:enterprise_linux:9::appstream |
before 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 | 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 |
nodejs-debuginfoRed Hat:enterprise_linux:9::appstream |
before 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 | 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 |
nodejs-debugsourceRed Hat:enterprise_linux:9::appstream |
before 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 | 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 |
nodejs-develRed Hat:enterprise_linux:9::appstream |
before 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 | 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 |
nodejs-docsRed Hat:enterprise_linux:9::appstream |
before 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 | 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 |
nodejs-full-i18nRed Hat:enterprise_linux:9::appstream |
before 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 | 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 |
nodejs-libsRed Hat:enterprise_linux:9::appstream |
before 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 | 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 |
nodejs-libs-debuginfoRed Hat:enterprise_linux:9::appstream |
before 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 | 1:24.18.0-1.module+el9.8.0+24456+b244c3b4 |
nodejs-nodemonRed Hat:enterprise_linux:9::appstream |
before 0:3.0.3-3.module+el9.8.0+24355+35d95b59 | 0:3.0.3-3.module+el9.8.0+24355+35d95b59 |
nodejs-packagingRed Hat:enterprise_linux:9::appstream |
before 0:2021.06-6.module+el9.8.0+24355+35d95b59 | 0:2021.06-6.module+el9.8.0+24355+35d95b59 |
nodejs-packaging-bundlerRed Hat:enterprise_linux:9::appstream |
before 0:2021.06-6.module+el9.8.0+24355+35d95b59 | 0:2021.06-6.module+el9.8.0+24355+35d95b59 |
npmRed Hat:enterprise_linux:9::appstream |
before 1:11.16.0-1.24.18.0.1.module+el9.8.0+24456+b244c3b4 | 1:11.16.0-1.24.18.0.1.module+el9.8.0+24456+b244c3b4 |
v8-13.6-develRed Hat:enterprise_linux:9::appstream |
before 3:13.6.233.17-1.24.18.0.1.module+el9.8.0+24456+b244c3b4 | 3:13.6.233.17-1.24.18.0.1.module+el9.8.0+24456+b244c3b4 |
nodejsRed Hat:enterprise_linux:9::appstream |
before 1:22.23.1-1.module+el9.8.0+24457+996af7aa | 1:22.23.1-1.module+el9.8.0+24457+996af7aa |
nodejs-debuginfoRed Hat:enterprise_linux:9::appstream |
before 1:22.23.1-1.module+el9.8.0+24457+996af7aa | 1:22.23.1-1.module+el9.8.0+24457+996af7aa |
nodejs-debugsourceRed Hat:enterprise_linux:9::appstream |
before 1:22.23.1-1.module+el9.8.0+24457+996af7aa | 1:22.23.1-1.module+el9.8.0+24457+996af7aa |
nodejs-develRed Hat:enterprise_linux:9::appstream |
before 1:22.23.1-1.module+el9.8.0+24457+996af7aa | 1:22.23.1-1.module+el9.8.0+24457+996af7aa |
nodejs-docsRed Hat:enterprise_linux:9::appstream |
before 1:22.23.1-1.module+el9.8.0+24457+996af7aa | 1:22.23.1-1.module+el9.8.0+24457+996af7aa |
nodejs-full-i18nRed Hat:enterprise_linux:9::appstream |
before 1:22.23.1-1.module+el9.8.0+24457+996af7aa | 1:22.23.1-1.module+el9.8.0+24457+996af7aa |
nodejs-libsRed Hat:enterprise_linux:9::appstream |
before 1:22.23.1-1.module+el9.8.0+24457+996af7aa | 1:22.23.1-1.module+el9.8.0+24457+996af7aa |
nodejs-libs-debuginfoRed Hat:enterprise_linux:9::appstream |
before 1:22.23.1-1.module+el9.8.0+24457+996af7aa | 1:22.23.1-1.module+el9.8.0+24457+996af7aa |
nodejs-nodemonRed Hat:enterprise_linux:9::appstream |
before 0:3.0.1-1.module+el9.8.0+24156+bb41d456 | 0:3.0.1-1.module+el9.8.0+24156+bb41d456 |
nodejs-packagingRed Hat:enterprise_linux:9::appstream |
before 0:2021.06-6.module+el9.8.0+24156+bb41d456 | 0:2021.06-6.module+el9.8.0+24156+bb41d456 |
nodejs-packaging-bundlerRed Hat:enterprise_linux:9::appstream |
before 0:2021.06-6.module+el9.8.0+24156+bb41d456 | 0:2021.06-6.module+el9.8.0+24156+bb41d456 |
npmRed Hat:enterprise_linux:9::appstream |
before 1:10.9.8-1.22.23.1.1.module+el9.8.0+24457+996af7aa | 1:10.9.8-1.22.23.1.1.module+el9.8.0+24457+996af7aa |
v8-12.4-develRed Hat:enterprise_linux:9::appstream |
before 3:12.4.254.21-1.22.23.1.1.module+el9.8.0+24457+996af7aa | 3:12.4.254.21-1.22.23.1.1.module+el9.8.0+24457+996af7aa |
nodejs24Red Hat:hummingbird:1 |
before 0:24.18.0-0.3.hum1 | 0:24.18.0-0.3.hum1 |
nodejs24-binRed Hat:hummingbird:1 |
before 0:24.18.0-0.3.hum1 | 0:24.18.0-0.3.hum1 |
nodejs24-develRed Hat:hummingbird:1 |
before 0:24.18.0-0.3.hum1 | 0:24.18.0-0.3.hum1 |
nodejs24-docsRed Hat:hummingbird:1 |
before 0:24.18.0-0.3.hum1 | 0:24.18.0-0.3.hum1 |
nodejs24-full-i18nRed Hat:hummingbird:1 |
before 0:24.18.0-0.3.hum1 | 0:24.18.0-0.3.hum1 |
nodejs24-libsRed Hat:hummingbird:1 |
before 0:24.18.0-0.3.hum1 | 0:24.18.0-0.3.hum1 |
nodejs24-npmRed Hat:hummingbird:1 |
before 0:11.16.0-1.24.18.0.0.3.hum1 | 0:11.16.0-1.24.18.0.0.3.hum1 |
nodejs24-npm-binRed Hat:hummingbird:1 |
before 0:24.18.0-0.3.hum1 | 0:24.18.0-0.3.hum1 |
v8-13.6-develRed Hat:hummingbird:1 |
before 0:13.6.233.17-1.24.18.0.0.3.hum1 | 0:13.6.233.17-1.24.18.0.0.3.hum1 |
nodejsRed Hat:enterprise_linux:8::appstream |
before 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 | 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 |
nodejs-debuginfoRed Hat:enterprise_linux:8::appstream |
before 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 | 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 |
nodejs-debugsourceRed Hat:enterprise_linux:8::appstream |
before 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 | 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 |
nodejs-develRed Hat:enterprise_linux:8::appstream |
before 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 | 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 |
nodejs-docsRed Hat:enterprise_linux:8::appstream |
before 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 | 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 |
nodejs-full-i18nRed Hat:enterprise_linux:8::appstream |
before 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 | 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 |
nodejs-libsRed Hat:enterprise_linux:8::appstream |
before 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 | 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 |
nodejs-libs-debuginfoRed Hat:enterprise_linux:8::appstream |
before 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 | 1:24.18.0-1.module+el8.10.0+24481+7a71fac8 |
nodejs-nodemonRed Hat:enterprise_linux:8::appstream |
before 0:3.0.3-1.module+el8.10.0+24190+49a46c75 | 0:3.0.3-1.module+el8.10.0+24190+49a46c75 |
nodejs-packagingRed Hat:enterprise_linux:8::appstream |
before 0:2021.06-6.module+el8.10.0+24190+49a46c75 | 0:2021.06-6.module+el8.10.0+24190+49a46c75 |
nodejs-packaging-bundlerRed Hat:enterprise_linux:8::appstream |
before 0:2021.06-6.module+el8.10.0+24190+49a46c75 | 0:2021.06-6.module+el8.10.0+24190+49a46c75 |
npmRed Hat:enterprise_linux:8::appstream |
before 1:11.16.0-1.24.18.0.1.module+el8.10.0+24481+7a71fac8 | 1:11.16.0-1.24.18.0.1.module+el8.10.0+24481+7a71fac8 |
v8-13.6-develRed Hat:enterprise_linux:8::appstream |
before 3:13.6.233.17-1.24.18.0.1.module+el8.10.0+24481+7a71fac8 | 3:13.6.233.17-1.24.18.0.1.module+el8.10.0+24481+7a71fac8 |
nodejsRed Hat:enterprise_linux:8::appstream |
before 1:22.23.1-1.module+el8.10.0+24500+8eb51621 | 1:22.23.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-debuginfoRed Hat:enterprise_linux:8::appstream |
before 1:22.23.1-1.module+el8.10.0+24500+8eb51621 | 1:22.23.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-debugsourceRed Hat:enterprise_linux:8::appstream |
before 1:22.23.1-1.module+el8.10.0+24500+8eb51621 | 1:22.23.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-develRed Hat:enterprise_linux:8::appstream |
before 1:22.23.1-1.module+el8.10.0+24500+8eb51621 | 1:22.23.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-docsRed Hat:enterprise_linux:8::appstream |
before 1:22.23.1-1.module+el8.10.0+24500+8eb51621 | 1:22.23.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-full-i18nRed Hat:enterprise_linux:8::appstream |
before 1:22.23.1-1.module+el8.10.0+24500+8eb51621 | 1:22.23.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-libsRed Hat:enterprise_linux:8::appstream |
before 1:22.23.1-1.module+el8.10.0+24500+8eb51621 | 1:22.23.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-libs-debuginfoRed Hat:enterprise_linux:8::appstream |
before 1:22.23.1-1.module+el8.10.0+24500+8eb51621 | 1:22.23.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-nodemonRed Hat:enterprise_linux:8::appstream |
before 0:3.0.1-1.module+el8.10.0+24500+8eb51621 | 0:3.0.1-1.module+el8.10.0+24500+8eb51621 |
nodejs-packagingRed Hat:enterprise_linux:8::appstream |
before 0:2021.06-6.module+el8.10.0+24500+8eb51621 | 0:2021.06-6.module+el8.10.0+24500+8eb51621 |
nodejs-packaging-bundlerRed Hat:enterprise_linux:8::appstream |
before 0:2021.06-6.module+el8.10.0+24500+8eb51621 | 0:2021.06-6.module+el8.10.0+24500+8eb51621 |
npmRed Hat:enterprise_linux:8::appstream |
before 1:10.9.8-1.22.23.1.1.module+el8.10.0+24500+8eb51621 | 1:10.9.8-1.22.23.1.1.module+el8.10.0+24500+8eb51621 |
v8-12.4-develRed Hat:enterprise_linux:8::appstream |
before 3:12.4.254.21-1.22.23.1.1.module+el8.10.0+24500+8eb51621 | 3:12.4.254.21-1.22.23.1.1.module+el8.10.0+24500+8eb51621 |
nodejs26Red Hat:hummingbird:1 |
before 0:26.5.0-1.5.hum1 | 0:26.5.0-1.5.hum1 |
nodejs26-binRed Hat:hummingbird:1 |
before 0:26.5.0-1.5.hum1 | 0:26.5.0-1.5.hum1 |
nodejs26-develRed Hat:hummingbird:1 |
before 0:26.5.0-1.5.hum1 | 0:26.5.0-1.5.hum1 |
nodejs26-docsRed Hat:hummingbird:1 |
before 0:26.5.0-1.5.hum1 | 0:26.5.0-1.5.hum1 |
nodejs26-full-i18nRed Hat:hummingbird:1 |
before 0:26.5.0-1.5.hum1 | 0:26.5.0-1.5.hum1 |
nodejs26-libsRed Hat:hummingbird:1 |
before 0:26.5.0-1.5.hum1 | 0:26.5.0-1.5.hum1 |
nodejs26-npmRed Hat:hummingbird:1 |
before 0:11.17.0-1.26.5.0.1.5.hum1 | 0:11.17.0-1.26.5.0.1.5.hum1 |
nodejs26-npm-binRed Hat:hummingbird:1 |
before 0:26.5.0-1.5.hum1 | 0:26.5.0-1.5.hum1 |
nodejs24Rocky Linux:10 |
before 1:24.18.0-1.el10_2 | 1:24.18.0-1.el10_2 |
nodejs22Rocky Linux:10 |
before 1:22.23.1-2.el10_2 | 1:22.23.1-2.el10_2 |
nodejs-nodemonRocky Linux:9 |
before 0:3.0.3-3.module+el9.7.0+40025+0e0cf6b2 | 0:3.0.3-3.module+el9.7.0+40025+0e0cf6b2 |
nodejs-packagingRocky Linux:9 |
before 0:2021.06-6.module+el9.7.0+40153+4d595597 | 0:2021.06-6.module+el9.7.0+40153+4d595597 |
nodejs-packagingRocky Linux:9 |
before 0:2021.06-6.module+el9.7.0+40165+d075e3f2 | 0:2021.06-6.module+el9.7.0+40165+d075e3f2 |
nodejs-packagingRocky Linux:9 |
before 0:2021.06-6.module+el9.7.0+40052+e32ea525 | 0:2021.06-6.module+el9.7.0+40052+e32ea525 |
nodejs-nodemonRocky Linux:9 |
before 0:3.0.1-1.module+el9.7.0+40165+d075e3f2 | 0:3.0.1-1.module+el9.7.0+40165+d075e3f2 |
nodejs-nodemonRocky Linux:9 |
before 0:3.0.1-1.module+el9.7.0+40022+9ecc286c | 0:3.0.1-1.module+el9.7.0+40022+9ecc286c |
nodejs-nodemonRocky Linux:9 |
before 0:3.0.1-1.module+el9.7.0+40153+4d595597 | 0:3.0.1-1.module+el9.7.0+40153+4d595597 |
nodejsRocky Linux:8 |
before 1:24.18.0-1.module+el8.10.0+40252+a58646bc | 1:24.18.0-1.module+el8.10.0+40252+a58646bc |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.3-1.module+el8.10.0+2084+ab509703 | 0:3.0.3-1.module+el8.10.0+2084+ab509703 |
nodejs-packagingRocky Linux:8 |
before 0:2021.06-6.module+el8.10.0+40171+8fa9c325 | 0:2021.06-6.module+el8.10.0+40171+8fa9c325 |
nodejs-packagingRocky Linux:8 |
before 0:2021.06-6.module+el8.10.0+40172+38f6fdd1 | 0:2021.06-6.module+el8.10.0+40172+38f6fdd1 |
nodejs-packagingRocky Linux:8 |
before 0:2021.06-6.module+el8.10.0+40048+6d99f608 | 0:2021.06-6.module+el8.10.0+40048+6d99f608 |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.9.0+1760+903d54b9 | 0:3.0.1-1.module+el8.9.0+1760+903d54b9 |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.10.0+1667+4a788d89 | 0:3.0.1-1.module+el8.10.0+1667+4a788d89 |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.10.0+1824+532140ee | 0:3.0.1-1.module+el8.10.0+1824+532140ee |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.10.0+1823+b5789597 | 0:3.0.1-1.module+el8.10.0+1823+b5789597 |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.10.0+1924+614dc87f | 0:3.0.1-1.module+el8.10.0+1924+614dc87f |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.10.0+1666+930e28e8 | 0:3.0.1-1.module+el8.10.0+1666+930e28e8 |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.10.0+1988+437f3d23 | 0:3.0.1-1.module+el8.10.0+1988+437f3d23 |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.10.0+1989+e60144d9 | 0:3.0.1-1.module+el8.10.0+1989+e60144d9 |
nodejs-nodemonRocky Linux:8 |
before 0:3.0.1-1.module+el8.10.0+1935+d3cbe60f | 0:3.0.1-1.module+el8.10.0+1935+d3cbe60f |
undiciRoot:npm |
before 7.28.0-aikido.1 | 7.28.0-aikido.18.5.0-aikido.17.28.0-aikido.26.27.0-aikido.17.28.0-aikido.37.28.0-aikido.46.27.0-aikido.27.28.0-aikido.56.27.0-aikido.36.27.0-aikido.46.27.0-aikido.56.27.0-aikido.6 |
@rootio/undiciRoot:npm |
before 7.28.0-root.io.1 | 7.28.0-root.io.18.5.0-root.io.17.28.0-root.io.26.27.0-root.io.17.28.0-root.io.37.28.0-root.io.46.27.0-root.io.27.28.0-root.io.56.27.0-root.io.36.27.0-root.io.46.27.0-root.io.56.27.0-root.io.6 |
nodejs22SUSE:Linux Enterprise Server 16.0 |
before 22.23.0-160000.1.1 | 22.23.0-160000.1.1 |
nodejs22SUSE:Linux Enterprise Server for SAP applications 16.0 |
before 22.23.0-160000.1.1 | 22.23.0-160000.1.1 |
nodejs24SUSE:Linux Enterprise Server 16.0 |
before 24.18.0-160000.1.1 | 24.18.0-160000.1.1 |
nodejs24SUSE:Linux Enterprise Server for SAP applications 16.0 |
before 24.18.0-160000.1.1 | 24.18.0-160000.1.1 |
nodejs24SUSE:Linux Enterprise Module for Web and Scripting 15 SP7 |
before 24.17.0-150700.15.11.1 | 24.17.0-150700.15.11.1 |
nodejs22SUSE:Linux Enterprise Server 15 SP6-LTSS |
before 22.23.0-150600.13.18.1 | 22.23.0-150600.13.18.1 |
nodejs22SUSE:Linux Enterprise Server for SAP Applications 15 SP6 |
before 22.23.0-150600.13.18.1 | 22.23.0-150600.13.18.1 |
nodejs22SUSE:Linux Enterprise Module for Web and Scripting 15 SP7 |
before 22.23.0-150700.3.12.1 | 22.23.0-150700.3.12.1 |
nodejs20SUSE:Linux Enterprise Server 15 SP6-LTSS |
before 20.20.2-150600.3.21.1 | 20.20.2-150600.3.21.1 |
nodejs20SUSE:Linux Enterprise Server for SAP Applications 15 SP6 |
before 20.20.2-150600.3.21.1 | 20.20.2-150600.3.21.1 |
nodejs20SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS |
before 20.20.2-150500.11.30.1 | 20.20.2-150500.11.30.1 |
nodejs20SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS |
before 20.20.2-150500.11.30.1 | 20.20.2-150500.11.30.1 |
nodejs20SUSE:Linux Enterprise Server 15 SP5-LTSS |
before 20.20.2-150500.11.30.1 | 20.20.2-150500.11.30.1 |
nodejs20SUSE:Linux Enterprise Server for SAP Applications 15 SP5 |
before 20.20.2-150500.11.30.1 | 20.20.2-150500.11.30.1 |
nodejs18SUSE:Linux Enterprise Server 12 SP5-LTSS |
before 18.20.8-8.44.1 | 18.20.8-8.44.1 |
nodejs18SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 |
before 18.20.8-8.44.1 | 18.20.8-8.44.1 |
nodejs18SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS |
before 18.20.8-150400.9.39.1 | 18.20.8-150400.9.39.1 |
nodejs18SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS |
before 18.20.8-150400.9.39.1 | 18.20.8-150400.9.39.1 |
nodejs18SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS |
before 18.20.8-150400.9.39.1 | 18.20.8-150400.9.39.1 |
nodejs18SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS |
before 18.20.8-150400.9.39.1 | 18.20.8-150400.9.39.1 |
nodejs18SUSE:Linux Enterprise Server 15 SP4-LTSS |
before 18.20.8-150400.9.39.1 | 18.20.8-150400.9.39.1 |
nodejs18SUSE:Linux Enterprise Server 15 SP5-LTSS |
before 18.20.8-150400.9.39.1 | 18.20.8-150400.9.39.1 |
nodejs18SUSE:Linux Enterprise Server for SAP Applications 15 SP4 |
before 18.20.8-150400.9.39.1 | 18.20.8-150400.9.39.1 |
nodejs18SUSE:Linux Enterprise Server for SAP Applications 15 SP5 |
before 18.20.8-150400.9.39.1 | 18.20.8-150400.9.39.1 |
nodejs16SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS |
before 16.20.2-150400.3.42.1 | 16.20.2-150400.3.42.1 |
nodejs16SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS |
before 16.20.2-150400.3.42.1 | 16.20.2-150400.3.42.1 |
nodejs16SUSE:Linux Enterprise Server 15 SP4-LTSS |
before 16.20.2-150400.3.42.1 | 16.20.2-150400.3.42.1 |
nodejs16SUSE:Linux Enterprise Server for SAP Applications 15 SP4 |
before 16.20.2-150400.3.42.1 | 16.20.2-150400.3.42.1 |
node-undiciUbuntu:24.04:LTS |
All versions, plus listed versions 5.22.1+dfsg1+~cs20.10.10.2-1ubuntu15.26.3+dfsg1+~cs23.10.12-2 |
None known |
node-undiciUbuntu:25.10 |
All versions, plus listed versions 7.3.0+dfsg1+~cs24.12.11-17.3.0+dfsg1+~cs24.12.11-2 |
None known |
node-undiciUbuntu:26.10 |
All versions, plus listed versions 7.18.2+dfsg+~cs3.2.0-1build17.24.6+dfsg+~cs3.2.0-38.5.0+dfsg+~cs3.2.0-28.5.0+dfsg+~cs3.2.0-38.9.0+dfsg+~cs3.2.0-1 |
None known |
node-undiciUbuntu:26.04:LTS |
All versions, plus listed versions 7.3.0+dfsg1+~cs24.12.11-27.16.0+dfsg+~cs3.2.0-27.18.2+dfsg+~cs3.2.0-17.18.2+dfsg+~cs3.2.0-1build1 |
None known |
nodejs24openSUSE:Tumbleweed |
before 24.17.0-1.1 | 24.17.0-1.1 |
nodejs22openSUSE:Leap 16.0 |
before 22.23.0-160000.1.1 | 22.23.0-160000.1.1 |
nodejs24openSUSE:Leap 16.0 |
before 24.18.0-160000.1.1 | 24.18.0-160000.1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | OSV | |
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-11525 is a low vulnerability (CVSS 3.7) in Nodejs Undici, published June 17, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.24%, the 15th percentile. Fixed in undici 6.27.0.
References
github.com/nodejs/undici/security/advisories/GHSA-g8m3-5g58-fq7m
cna.openjsf.org/security-advisories.html
nvd.nist.gov/vuln/detail/CVE-2026-11525
github.com/advisories/GHSA-g8m3-5g58-fq7m
access.redhat.com/errata/RHSA-2026:35841
access.redhat.com/security/cve/CVE-2026-11525
Show 194 moreShow less
access.redhat.com/security/cve/CVE-2026-12151
access.redhat.com/security/cve/CVE-2026-42338
access.redhat.com/security/cve/CVE-2026-48615
access.redhat.com/security/cve/CVE-2026-48618
access.redhat.com/security/cve/CVE-2026-48619
access.redhat.com/security/cve/CVE-2026-48928
access.redhat.com/security/cve/CVE-2026-48930
access.redhat.com/security/cve/CVE-2026-48933
access.redhat.com/security/cve/CVE-2026-48934
access.redhat.com/security/cve/CVE-2026-48935
access.redhat.com/security/cve/CVE-2026-6733
access.redhat.com/security/cve/CVE-2026-6734
access.redhat.com/security/cve/CVE-2026-9678
access.redhat.com/security/cve/CVE-2026-9697
bugzilla.redhat.com/2476810
bugzilla.redhat.com/2489980
bugzilla.redhat.com/2490000
bugzilla.redhat.com/2490006
bugzilla.redhat.com/2490008
bugzilla.redhat.com/2490018
bugzilla.redhat.com/2490024
bugzilla.redhat.com/2493325
bugzilla.redhat.com/2493326
bugzilla.redhat.com/2493329
bugzilla.redhat.com/2493331
bugzilla.redhat.com/2493332
bugzilla.redhat.com/2493333
bugzilla.redhat.com/2493335
bugzilla.redhat.com/2493337
errata.almalinux.org/10/ALSA-2026-35841.html
redhat.com/security/data/cve/CVE-2026-48617.html
redhat.com/security/data/cve/CVE-2026-48931.html
redhat.com/security/data/cve/CVE-2026-48937.html
access.redhat.com/errata/RHSA-2026:35842
errata.almalinux.org/10/ALSA-2026-35842.html
access.redhat.com/errata/RHSA-2026:35891
errata.almalinux.org/9/ALSA-2026-35891.html
access.redhat.com/errata/RHSA-2026:35892
errata.almalinux.org/9/ALSA-2026-35892.html
access.redhat.com/errata/RHSA-2026:39868
errata.almalinux.org/8/ALSA-2026-39868.html
access.redhat.com/errata/RHSA-2026:41947
errata.almalinux.org/8/ALSA-2026-41947.html
github.com/CVEProject/cvelistV5/tree/main/cves/2026/11xxx/CVE-2026-11525.json
security-tracker.debian.org/tracker/CVE-2026-11525
github.com/nodejs/undici
access.redhat.com/security/updates/classification
bugzilla.redhat.com/show_bug.cgi?id=2476810
bugzilla.redhat.com/show_bug.cgi?id=2489980
bugzilla.redhat.com/show_bug.cgi?id=2490000
bugzilla.redhat.com/show_bug.cgi?id=2490006
bugzilla.redhat.com/show_bug.cgi?id=2490008
bugzilla.redhat.com/show_bug.cgi?id=2490018
bugzilla.redhat.com/show_bug.cgi?id=2490024
bugzilla.redhat.com/show_bug.cgi?id=2493325
bugzilla.redhat.com/show_bug.cgi?id=2493326
bugzilla.redhat.com/show_bug.cgi?id=2493329
issues.redhat.com/browse/RHEL-186582
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_35841.json
cve.org/CVERecord?id=CVE-2026-6733
nvd.nist.gov/vuln/detail/CVE-2026-6733
github.com/nodejs/undici/security/advisories/GHSA-35p6-xmwp-9g52
hackerone.com/reports/3582376
cve.org/CVERecord?id=CVE-2026-6734
nvd.nist.gov/vuln/detail/CVE-2026-6734
github.com/nodejs/undici/security/advisories/GHSA-hm92-r4w5-c3mj
cve.org/CVERecord?id=CVE-2026-9678
nvd.nist.gov/vuln/detail/CVE-2026-9678
github.com/nodejs/undici/security/advisories/GHSA-pr7r-676h-xcf6
cve.org/CVERecord?id=CVE-2026-9697
nvd.nist.gov/vuln/detail/CVE-2026-9697
github.com/nodejs/undici/security/advisories/GHSA-vmh5-mc38-953g
cve.org/CVERecord?id=CVE-2026-11525
cve.org/CVERecord?id=CVE-2026-12151
nvd.nist.gov/vuln/detail/CVE-2026-12151
github.com/nodejs/undici/security/advisories/GHSA-vxpw-j846-p89q
cve.org/CVERecord?id=CVE-2026-42338
nvd.nist.gov/vuln/detail/CVE-2026-42338
github.com/beaugunderson/ip-address/security/advisories/GHSA-v2v4-37r5-5v8g
cve.org/CVERecord?id=CVE-2026-48615
nvd.nist.gov/vuln/detail/CVE-2026-48615
nodejs.org/en/blog/vulnerability/june-2026-security-releases
access.redhat.com/security/cve/CVE-2026-48617
cve.org/CVERecord?id=CVE-2026-48617
nvd.nist.gov/vuln/detail/CVE-2026-48617
hackerone.com/reports/3692858
cve.org/CVERecord?id=CVE-2026-48618
nvd.nist.gov/vuln/detail/CVE-2026-48618
cve.org/CVERecord?id=CVE-2026-48619
nvd.nist.gov/vuln/detail/CVE-2026-48619
cve.org/CVERecord?id=CVE-2026-48928
nvd.nist.gov/vuln/detail/CVE-2026-48928
cve.org/CVERecord?id=CVE-2026-48930
nvd.nist.gov/vuln/detail/CVE-2026-48930
github.com/nodejs/node/commit/7dafafa2424710ded8b77eb7c878e884c1aef64e
hackerone.com/reports/3656716
access.redhat.com/security/cve/CVE-2026-48931
cve.org/CVERecord?id=CVE-2026-48931
nvd.nist.gov/vuln/detail/CVE-2026-48931
cve.org/CVERecord?id=CVE-2026-48933
nvd.nist.gov/vuln/detail/CVE-2026-48933
cve.org/CVERecord?id=CVE-2026-48934
nvd.nist.gov/vuln/detail/CVE-2026-48934
cve.org/CVERecord?id=CVE-2026-48935
nvd.nist.gov/vuln/detail/CVE-2026-48935
access.redhat.com/security/cve/CVE-2026-48937
cve.org/CVERecord?id=CVE-2026-48937
nvd.nist.gov/vuln/detail/CVE-2026-48937
hackerone.com/reports/3658225
issues.redhat.com/browse/RHEL-186623
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_35842.json
issues.redhat.com/browse/RHEL-186580
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_35891.json
issues.redhat.com/browse/RHEL-186622
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_35892.json
images.redhat.com
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_38236.json
cve.org/CVERecord?id=CVE-2026-5078
nvd.nist.gov/vuln/detail/CVE-2026-5078
github.com/expressjs/morgan/security/advisories/GHSA-4vj7-5mj6-jm8m
cve.org/CVERecord?id=CVE-2026-9679
nvd.nist.gov/vuln/detail/CVE-2026-9679
github.com/nodejs/undici/security/advisories/GHSA-p88m-4jfj-68fv
cve.org/CVERecord?id=CVE-2026-53550
nvd.nist.gov/vuln/detail/CVE-2026-53550
github.com/nodeca/js-yaml/security/advisories/GHSA-h67p-54hq-rp68
cve.org/CVERecord?id=CVE-2026-59869
nvd.nist.gov/vuln/detail/CVE-2026-59869
github.com/nodeca/js-yaml/commit/24f13e79ee1343a7e30bd6f6c9d9cdbf0ac9b2b7
github.com/nodeca/js-yaml/commit/59423c6f8cdc78742ac00e25a4dd39ef16b702e4
github.com/nodeca/js-yaml/releases/tag/3.15.0
github.com/nodeca/js-yaml/releases/tag/4.3.0
github.com/nodeca/js-yaml/security/advisories/GHSA-52cp-r559-cp3m
issues.redhat.com/browse/RHEL-168744
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_39868.json
issues.redhat.com/browse/RHEL-176170
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_41947.json
security.access.redhat.com/data/csaf/v2/advisories/2026/rhsa-2026_45783.json
errata.rockylinux.org/RLSA-2026:35841
errata.rockylinux.org/RLSA-2026:35842
errata.rockylinux.org/RLSA-2026:35891
errata.rockylinux.org/RLSA-2026:35892
errata.rockylinux.org/RLSA-2026:39868
errata.rockylinux.org/RLSA-2026:41947
suse.com/support/update/announcement/2026/suse-su-202622368-1
bugzilla.suse.com/1256576
bugzilla.suse.com/1259853
bugzilla.suse.com/1260455
bugzilla.suse.com/1260462
bugzilla.suse.com/1260463
bugzilla.suse.com/1260480
bugzilla.suse.com/1260482
bugzilla.suse.com/1260494
bugzilla.suse.com/1262274
bugzilla.suse.com/1266318
bugzilla.suse.com/1268097
bugzilla.suse.com/1268477
bugzilla.suse.com/1268479
bugzilla.suse.com/1268481
bugzilla.suse.com/1268482
bugzilla.suse.com/1268554
bugzilla.suse.com/1268555
bugzilla.suse.com/1268592
bugzilla.suse.com/1268593
bugzilla.suse.com/1268598
bugzilla.suse.com/1268605
bugzilla.suse.com/1268606
bugzilla.suse.com/1268608
bugzilla.suse.com/1268609
suse.com/security/cve/CVE-2026-11525
suse.com/security/cve/CVE-2026-12151
suse.com/security/cve/CVE-2026-21637
suse.com/security/cve/CVE-2026-21710
suse.com/security/cve/CVE-2026-21713
suse.com/security/cve/CVE-2026-21714
suse.com/security/cve/CVE-2026-21715
suse.com/security/cve/CVE-2026-21716
suse.com/security/cve/CVE-2026-21717
suse.com/security/cve/CVE-2026-27135
suse.com/security/cve/CVE-2026-40170
suse.com/security/cve/CVE-2026-42338
suse.com/security/cve/CVE-2026-48615
suse.com/security/cve/CVE-2026-48617
suse.com/security/cve/CVE-2026-48618
suse.com/security/cve/CVE-2026-48619
suse.com/security/cve/CVE-2026-48928
suse.com/security/cve/CVE-2026-48930
suse.com/security/cve/CVE-2026-48931
suse.com/security/cve/CVE-2026-48933
suse.com/security/cve/CVE-2026-48934
suse.com/security/cve/CVE-2026-48935
suse.com/security/cve/CVE-2026-48937
suse.com/security/cve/CVE-2026-6733
ubuntu.com/security/CVE-2026-11525
Left out here: 84 references and the rest of 4 source descriptions. The JSON record has them.