dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2025-7424

HIGH · 7.5 CVSS v3.1 Published 2025-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in the libxslt library. The same memory field, psvi, is used for both stylesheet and input data, which can lead to type confusion during XML transformations. This vulnerability allows an attacker to crash the application or corrupt memory. In some cases, it may lead to denial of service or unexpected behavior.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A type confusion vulnerability exists in libxslt where the psvi memory field is incorrectly reused between stylesheet and input data contexts during XML transformations. This improper memory handling allows an attacker to corrupt memory or crash the application by supplying specially crafted XML content, potentially leading to denial of service.

MitigationUpgrade libxslt to the latest patched version when available; until then, sanitize or reject untrusted XML stylesheets and input documents from external sources to prevent exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0= 10.0
LibxsltApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if libxslt is installed
    Run 'rpm -qa | grep libxslt' (RHEL/OCP) or check library files in /usr/lib/libxslt* or /usr/lib64/libxslt*
    Affected if libxslt package or library file exists on the system
  2. Determine installed libxslt version
    Run 'rpm -q libxslt' (RHEL) or 'xsltproc --version' to see the linked libxslt version
    Affected if Any version of libxslt is installed (vulnerable to CVE-2025-7424)
  3. Verify XSLT transformation capability is in use
    Search application code or configuration for xsltproc, xsltTransform, xsltNewStylesheet, or similar libxslt API calls; check for .xsl or .xslt file usage
    Affected if Applications perform XSLT transformations using libxslt functions
  4. Confirm processing of external or untrusted XML content
    Review whether XML stylesheets or input documents from external or untrusted sources are processed by the XSLT processor
    Affected if Untrusted XML/XSLT content is transformed using the libxslt library

If libxslt is installed and used to transform untrusted XML or XSLT content, the environment is affected by this type confusion vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade libxslt to the latest patched version when available; until then, sanitize or reject untrusted XML stylesheets and input documents from external sources to prevent exploitation.

Recommended fix High confidence

Upgrade to the latest libxslt package version available from Red Hat via RHN or your RHEL subscription channels

  1. Identify the libxslt package version currently installed using: rpm -qa | grep libxslt or dnf list installed | grep libxslt
  2. Check for available updates by running: dnf check-update (RHEL 8/9) or yum check-update (RHEL 6/7)
  3. Apply the security update: dnf update libxslt or yum update libxslt
  4. Restart any services or applications that use libxslt to ensure the updated library is loaded
  5. Verify the updated version is installed: rpm -qa | grep libxslt
Caveat Standard library updates may require restart of dependent services; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7424 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7424 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data