CVE-2026-53550VulnerabilityPublished 10 Jul 2026Updated 27 Oct 2026

Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

Affects Red Hat node-js-yamlSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-59869

Authoritative record:CVE-2026-53550· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 26.10node-js-yaml`pkg:deb/ubuntu/node-js-yaml?arch=source&distro=stonking`Other threats	Affected =4.1.1+dfsg+~4.0.9-1 =4.2.0+~4.0.9-1 =4.2.0+~4.0.9-2	Fixed in–
Ubuntu 26.04 LTSnode-js-yaml`pkg:deb/ubuntu/node-js-yaml?arch=source&distro=resolute`Other threats	Affected =4.1.0+dfsg+~4.0.5-7 =4.1.1+dfsg+~4.0.9-1	Fixed in–
Ubuntu 25.10node-js-yaml`pkg:deb/ubuntu/node-js-yaml?arch=source&distro=questing`Other threats	Affected =4.1.0+dfsg+~4.0.5-7	Fixed in–
Ubuntu 24.04 LTSnode-js-yaml`pkg:deb/ubuntu/node-js-yaml?arch=source&distro=noble`Other threats	Affected =4.1.0+dfsg+~4.0.5-7	Fixed in–
Ubuntu 22.04 LTSnode-js-yaml`pkg:deb/ubuntu/node-js-yaml?arch=source&distro=jammy`Other threats	Affected 3.14.1+dfsg+~3.12.6-2 – 4.1.0+dfsg+~4.0.5-6 4 affected builds	Fixed in–
Ubuntu 20.04 LTSnode-js-yaml`pkg:deb/ubuntu/node-js-yaml?arch=source&distro=focal`Other threats	Affected =3.13.1+dfsg-2	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To reduce exposure, restrict the processing of untrusted YAML documents by applications using js-yaml. Implement robust input validation and sanitization for all YAML data from untrusted sources. Additionally, limit network access to services that parse YAML content to trusted clients or networks using firewall rules. Monitor Red Hat advisories for updates regarding an official fix.

Description

This update includes the following RPMs: nodejs25: * nodejs25-25.9.0-1.3.hum1 (aarch64, x86_64) * nodejs25-bin-25.9.0-1.3.hum1 (noarch) * nodejs25-devel-25.9.0-1.3.hum1 (aarch64, x86_64) * nodejs25-docs-25.9.0-1.3.hum1 (noarch) * nodejs25-full-i18n-25.9.0-1.3.hum1 (aarch64, x86_64) * nodejs25-libs-25.9.0-1.3.hum1 (aarch64, x86_64) * nodejs25-npm-11.12.1-1.25.9.0.1.3.hum1 (noarch) * nodejs25-npm-bin-25.9.0-1.3.hum1 (noarch) * v8-14.1-devel-14.1.146.11-1.25.9.0.1.3.hum1 (aarch64, x86_64) * nodejs25-25.9.0-1.3.hum1.src (src) Security Fix(es): nodejs25: * CVE-2026-59869

Impact

The vulnerability allows remote attackers to cause a denial of service by consuming excessive CPU resources when parsing specially crafted YAML documents. This can disrupt services that rely on js-yaml for YAML processing without requiring authentication or complex attack vectors. There is no impact on confidentiality or integrity, only availability is affected.

Summary

The vulnerability CVE-2026-59869 is a denial of service (DoS) issue in the js-yaml library, a JavaScript YAML parser and dumper used by Red Hat Hardened Images RPMs, specifically nodejs25 packages. An attacker can exploit this by submitting a crafted YAML document with a chain of mappings using merge keys, which causes the parser to consume excessive CPU resources, resulting in a DoS condition. Red Hat has classified this vulnerability as Important and rated its impact as high availability impact with no confidentiality or integrity impact. The affected versions are nodejs25 packages >=25.0.0 and <25.9.0. The advisory does not indicate an official patch release yet, and Red Hat recommends mitigation by restricting untrusted YAML processing and applying input validation and network restrictions.

CWE-1333Inefficient Regular Expression Complexity (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.
Architecture and Design
Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers.
System Configuration
Set backtracking limits in the configuration of the regular expression implementation, such as PHP's pcre.backtrack_limit. Also consider limits on execution time for the process.
Implementation
Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
Regular Expression Exponential Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-606Unchecked Input for Loop Condition (opens in a new tab)
Base weakness
The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.
Implementation
Do not use user-controlled data for loop conditions.
Implementation
Perform input validation.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Aug 2026, 15:41 UTC

WeaknessesCWE-1333, CWE-606

Technical details

References

Community reviews

Related threats