CVE-2025-55130VulnerabilityPublished 17 Feb 2026Updated 3 Jul 2026

Red Hat Security Advisory: nodejs:22 security update

Affects Red Hat nodejs:22Source GCVE Database

Mentioned vulnerabilities

Authoritative record:CVE-2025-55130· High 7.1

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.0 base score

7.1High

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

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

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

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
nodejsnode	Affected >=20.19.6 <=20.19.6 >=22.21.1 <=22.21.1 >=24.12.0 <=24.12.0 >=25.2.1 <=25.2.1	Fixed in–

AI-suggested

Red Hat has released updated Node.js 22 packages for Red Hat Enterprise Linux 9 that address these vulnerabilities. Users should apply the security update as described in the Red Hat advisory RHSA-2026:2782 and the referenced article https://access.redhat.com/articles/11258. No indication of temporary fixes or workarounds is provided, so applying the official update is the recommended mitigation.

Description

This Red Hat security advisory addresses multiple vulnerabilities in the Node.js 22 module for Red Hat Enterprise Linux 9. The issues include filesystem permissions bypass, denial of service, and uninitialized memory exposure. The update fixes six CVEs related to these vulnerabilities. The advisory rates the security impact as Important (high severity).

Impact

The vulnerabilities impact Node.js 22 on Red Hat Enterprise Linux 9 and could allow attackers to bypass filesystem permissions, cause denial of service, or expose uninitialized memory, potentially leading to unauthorized access or service disruption. The advisory rates the impact as Important, indicating a high security risk if unpatched.

Summary

Red Hat issued a security update for the Node.js 22 module in Red Hat Enterprise Linux 9 to fix six vulnerabilities: two filesystem permissions bypasses (CVE-2025-55130, CVE-2025-55132), three denial of service issues (CVE-2025-59465, CVE-2025-59466, CVE-2026-21637), and one uninitialized memory exposure (CVE-2025-55131). These vulnerabilities could allow unauthorized access to filesystem permissions, cause denial of service conditions, or expose uninitialized memory. The advisory references Red Hat Bugzilla entries for each CVE and provides updated packages to remediate the issues.

CWE-281Improper Preservation of Permissions (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-248Uncaught Exception (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
An exception is thrown from a function, but it is not caught.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (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 5 Jul 2026, 00:01 UTC

WeaknessesCWE-281, CWE-497, CWE-248 +1

Technical details

References

Community reviews

Related threats