CVE-2025-13465VulnerabilityPublished 10 Feb 2026Updated 31 Oct 2026

Red Hat Security Advisory: pcs security update

Affects Red Hat pcsSource GCVE Database

Compare

Not known to be exploited.

Data as of 31 Oct 2026, 20:20 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

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

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 31 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

AI-suggested

Red Hat has released updated pcs packages that fix the prototype pollution vulnerability. Users of affected Red Hat Enterprise Linux 9 products should apply the provided security update as described in the Red Hat advisory (RHSA-2026:2452) and the referenced update article. No additional mitigation steps are indicated beyond applying the official patch.

Description

A prototype pollution vulnerability (CVE-2025-13465) exists in the lodash library functions _.unset and _.omit, affecting the pcs packages used for configuring Pacemaker and Corosync utilities in Red Hat Enterprise Linux 9. This security flaw has been rated as important by Red Hat Product Security. An update addressing this issue is available for multiple Red Hat Enterprise Linux 9 variants including High Availability and Resilient Storage editions across various architectures.

Impact

The vulnerability allows prototype pollution via lodash functions _.unset and _.omit, which can lead to security issues such as data manipulation or application instability in the pcs configuration system. Red Hat rates the impact as important, indicating a significant security concern but not necessarily critical. There are no known exploits in the wild at this time.

Summary

The pcs packages in Red Hat Enterprise Linux 9 provide command-line configuration for Pacemaker and Corosync. They were found to include a prototype pollution vulnerability in lodash's _.unset and _.omit functions, tracked as CVE-2025-13465. Prototype pollution can allow attackers to manipulate object prototypes, potentially leading to unexpected behavior or security issues. Red Hat has issued an important security advisory with updated pcs packages to fix this vulnerability. The advisory covers multiple Red Hat Enterprise Linux 9 product variants and architectures, and references a detailed vendor article for applying the update.

CWE-1321Improperly Controlled Modification of Object Prototype Attributes (Prototype Pollution) (opens in a new tab)
Variant weakness
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
Implementation
By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
Architecture and Design
By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
Implementation · Input Validation
When handling untrusted objects, validating using a schema can be used.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Manipulating User-Controlled Variables (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

Description

AI analysisMachine-generated, updated 31 Oct 2026, 17:51 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-1321

Technical details

References

Community reviews

Related threats