CyberSecBulletin
CVE-2025-56005NVD status: Modified

Fence Agents Remediation Operator: Deserialization of Untrusted Data

CVE-2025-56005 is a high-severity deserialization of untrusted data vulnerability in Fence Agents Remediation Operator from Red Hat, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 18.8% chance of exploitation within 30 days, which is in the top 2.67% of all scored CVEs.

Patch this week

EPSS places it among the vulnerabilities most likely to be exploited soon.

What to do

  1. Check which version of Fence Agents Remediation Operator you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatFence Agents Remediation OperatorNot specified in the recordNot stated
Red HatMigration Toolkit for ContainersNot specified in the recordNot stated
Red HatMigration Toolkit for VirtualizationNot specified in the recordNot stated
Red HatOpenShift Developer Tools and ServicesNot specified in the recordNot stated
Red HatOpenShift PipelinesNot specified in the recordNot stated
Red HatOpenShift Service Mesh 2Not specified in the recordNot stated
Red HatOpenShift Service Mesh 3Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Security 4Not specified in the recordNot stated
Red HatRed Hat Ansible Automation Platform Ansible Core 2Not specified in the recordNot stated
Red HatRed Hat Ceph Storage 7Not specified in the recordNot stated
Red HatRed Hat Ceph Storage 8Not specified in the recordNot stated
Red HatRed Hat Certification Program for Red Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Directory Server 13Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 7Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux AI (RHEL AI) 3Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4Not specified in the recordNot stated
Red HatRed Hat Openshift Data Foundation 4Not specified in the recordNot stated
Red HatRed Hat OpenShift GitOpsNot specified in the recordNot stated
Red HatRed Hat OpenStack Platform 13 (Queens)Not specified in the recordNot stated
Red HatRed Hat OpenStack Platform 16.2Not specified in the recordNot stated
Red HatRed Hat OpenStack Platform 17.1Not specified in the recordNot stated
Red HatRed Hat OpenStack Platform 18.0Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 3 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Scoring systemScoreSeverityScored by
CVSS 3.19.8CriticalCISA (ADP)
CVSS 3.17.8HighCNA

Official description

An undocumented and unsafe feature in the PLY (Python Lex-Yacc) library 3.11 allows Remote Code Execution (RCE) via the `picklefile` parameter in the `yacc()` function. This parameter accepts a `.pkl` file that is deserialized with `pickle.load()` without validation. Because `pickle` allows execution of embedded code via `__reduce__()`, an attacker can achieve code execution by passing a malicious pickle file. The parameter is not mentioned in official documentation or the GitHub repository, yet it is active in the PyPI version. This introduces a stealthy backdoor and persistence risk. NOTE: A third-party states that this vulnerability should be rejected because the proof of concept does not demonstrate arbitrary code execution and fails to complete successfully.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Deserialization of Untrusted Data

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

How developers prevent this class of flaw

  • If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
  • When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
  • Explicitly define a final object() to prevent deserialization.

More Deserialization of Untrusted Data vulnerabilities (CWE-502)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Patches and release notes

Technical write-ups (may include proof of concept)

Other vulnerabilities in Fence Agents Remediation Operator

All Fence Agents Remediation Operator vulnerabilities

Recent Deserialization of Untrusted Data vulnerabilities

Spotted an error? Tell us.