BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-31133High confidence

runc container escape via "masked path" abuse due to mount race conditions

opencontainers · runc

Official source article: GitHub GHSA-9493-H29P-RFM2 ↗. Check the applicable product and release in the original source.

7.3HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 6 Nov 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.84% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs opencontainers runc and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communityruncVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.3.3-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · communityruncVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.3.3-r0Alpine Security Database ↗Source updated 11 Sep 2026
Debian trixietrixie · sourceruncAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceruncAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceruncVendor fix publishedDebian records a fixed source-package version for this release.1.3.3+ds1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceruncVendor fix publishedDebian records a fixed source-package version for this release.1.3.3+ds1-2Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiveruncUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archiverunc-appVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1.3.3-0ubuntu1~24.04.2Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogithub.com/opencontainers/runcSEMVER: introduced 0; fixed 1.2.81.2.8OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/opencontainers/runcSEMVER: introduced 1.3.0-rc.1; fixed 1.3.31.3.3OSV record ↗aggregator derived · 10 Sep 2026
Gogithub.com/opencontainers/runcSEMVER: introduced 1.4.0-rc.1; fixed 1.4.0-rc.31.4.0-rc.3OSV record ↗aggregator derived · 10 Sep 2026
gogithub.com/opencontainers/runc<= 1.2.71.2.8GitHub advisory ↗upstream repository advisory · 6 Nov 2025
gogithub.com/opencontainers/runc>= 1.3.0-rc.1, <= 1.3.21.3.3GitHub advisory ↗upstream repository advisory · 6 Nov 2025
gogithub.com/opencontainers/runc>= 1.4.0-rc.1, <= 1.4.0-rc.21.4.0-rc.3GitHub advisory ↗upstream repository advisory · 6 Nov 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-31133 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityrunc: container escape via 'masked path' abuse due to mount race conditions
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in runc. This flaw exploits an issue with how masked paths are implementedin runc. When masking files, runc will bind-mount the container's /dev/null inode on top of the file. However, if an attacker can replace /dev/null with a symlink to some other procfs file, runc will instead bind-mount the symlink target read-write.
Remediation
For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:4e989978ab0e24d7148f08e939800502370b761efea1005d87522884d1a3f595 All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-37945

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7 and below, 1.3.0-rc.1 through 1.3.1, 1.4.0-rc.1 and 1.4.0-rc.2 files, runc would not perform sufficient verification that the source of the bind-mount (i.e., the container's /dev/null) was actually a real /dev/null inode when using the container's /dev/null to mask. This exposes two methods of attack: an arbitrary mount gadget, leading to host information disclosure, host denial of service, container escape, or a bypassing of maskedPaths. This issue is fixed in versions 1.2.8, 1.3.3 and 1.4.0-rc.3.

What

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7 and below, 1.3.0-rc.1 through 1.3.1, 1.4.0-rc.1 and 1.4.0-rc.2 files, runc would not perform sufficient verification that the source of the bind-mount (i.e., the container's /dev/null) was actually a real /dev/null inode when using the container's /dev/null to mask. This exposes two methods of attack: an arbitrary mount gadget, leading to host information disclosure, host denial of service, container escape, or a bypassing of maskedPaths. This issue is fixed in versions 1.2.8, 1.3.3 and 1.4.0-rc.3.

Why

The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.

What

runc is a CLI tool for spawning and running containers according to the OCI specification. In versions 1.2.7 and below, 1.3.0-rc.1 through 1.3.1, 1.4.0-rc.1 and 1.4.0-rc.2 files, runc would not perform sufficient verification that the source of the bind-mount (i.e., the container's /dev/null) was actually a real /dev/null inode when using the container's /dev/null to mask. This exposes two methods of attack: an arbitrary mount gadget, leading to host information disclosure, host denial of service, container escape, or a bypassing of maskedPaths. This issue is fixed in versions 1.2.8, 1.3.3 and 1.4.0-rc.3.

Why

The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may obtain information outside the intended access boundary.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → UNIX Symbolic Link (Symlink) Following → obtain information outside the intended access boundary
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
Active interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-61 ↗

CWE-61: UNIX Symbolic Link (Symlink) Following. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRLowPrivileges required: The attacker needs basic user-level privileges.UIActiveUser interaction: A user must take a deliberate action for exploitation to succeed.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCHighSubsequent-system confidentiality: A successful attack can cause a major loss.SIHighSubsequent-system integrity: A successful attack can cause a major loss.SAHighSubsequent-system availability: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-61
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-0778Dell Secure Connect Gateway Policy Manager: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway Policy Manager ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-2563Microsoft Azure Linux: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Microsoft Azure Linux und Microsoft Windows ausnutzen um erhöhte Privilegien zu erlangen, beliebigen Code auszuführen, die Authentifizierung zu umgehen, Spoofing-Angriffe durchzuführen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht näher spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-2518Red Hat Enterprise Linux (runc): Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

Ein lokaler Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux und Red Hat OpenShift ausnutzen, um Sicherheitsvorkehrungen zu umgehen und einen Denial of Service herbeizuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251112Security Bulletin 12 Nov 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Nov 2025, published on 12 November 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2025-28164 Référence CVE CVE-2025-29774 https://www.cve.org/CVERecord?id=CVE-2025-29774 Référence CVE CVE-2025-29775 https://www.cve.org/CVERecord?id=CVE-2025-29775 Référence CVE CVE-2025-30065 https://www.cve.org/CVERecord?id=CVE-2025-30065 Référence CVE CVE-2025-30153 https://www.cve.org/CVERecord?id=CVE-2025-30153 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-30749 https://www.cve.org/CVERecord?id=CVE-2025-30749 Référence CVE CVE-2025-30754 https://www.cve.org/CVERecord?id=CVE-2025-30754 Référence CVE CVE-2025-30761 https://www.cve.org/CVERecord?id=CVE-2025-30761 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-37731 https://www.cve.org/CVERecord?id=CVE-2025-37731 Référence CVE CVE-2025-4138 https://www.cve.org/CVERecord?id=CVE-2025-4138 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4432 https://www.cve.org/CVERecord?id=CVE-2025-4432 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 Référence CVE CVE-2025-4565 https://www.cve.org/CVERecord?id=CVE-2025-4565

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

rd?id=CVE-2025-2668 Référence CVE CVE-2025-27111 https://www.cve.org/CVERecord?id=CVE-2025-27111 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CVE-2025-27516 Référence CVE CVE-2025-27558 https://www.cve.org/CVERecord?id=CVE-2025-27558 Référence CVE CVE-2025-27610 https://www.cve.org/CVERecord?id=CVE-2025-27610 Référence CVE CVE-2025-29481 https://www.cve.org/CVERecord?id=CVE-2025-29481 Référence CVE CVE-2025-29934 https://www.cve.org/CVERecord?id=CVE-2025-29934 Référence CVE CVE-2025-29943 https://www.cve.org/CVERecord?id=CVE-2025-29943 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-31648 https://www.cve.org/CVERecord?id=CVE-2025-31648 Référence CVE CVE-2025-32441 https://www.cve.org/CVERecord?id=CVE-2025-32441 Référence CVE CVE-2025-34034 https://www.cve.org/CVERecord?id=CVE-2025-34034 Référence CVE CVE-2025-36001 https://www.cve.org/CVERecord?id=CVE-2025-36001 Référence CVE CVE-2025-36009 https://www.cve.org/CVERecord?id=CVE-2025-36009 Référence CVE CVE-2025-36070 https://www.cve.org/CVERecord?id=CVE-2025-36070 Référence CVE CVE-2025-36098 https://www.cve.org/CVERecord?id=CVE-2025-36098 Référence CVE CVE-2025-36123 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2025-23155 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-23162 https://www.cve.org/CVERecord?id=CVE-2025-23162 Référence CVE CVE-2025-2668 https://www.cve.org/CVERecord?id=CVE-2025-2668 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CVE-2025-27516 Référence CVE CVE-2025-27558 https://www.cve.org/CVERecord?id=CVE-2025-27558 Référence CVE CVE-2025-29481 https://www.cve.org/CVERecord?id=CVE-2025-29481 Référence CVE CVE-2025-29934 https://www.cve.org/CVERecord?id=CVE-2025-29934 Référence CVE CVE-2025-29943 https://www.cve.org/CVERecord?id=CVE-2025-29943 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-31648 https://www.cve.org/CVERecord?id=CVE-2025-31648 Référence CVE CVE-2025-34034 https://www.cve.org/CVERecord?id=CVE-2025-34034 Référence CVE CVE-2025-36001 https://www.cve.org/CVERecord?id=CVE-2025-36001 Référence CVE CVE-2025-36009 https://www.cve.org/CVERecord?id=CVE-2025-36009 Référence CVE CVE-2025-36070 https://www.cve.org/CVERecord?id=CVE-2025-36070 Référence CVE CVE-2025-36098 https://www.cve.org/CVERecord?id=CVE-2025-36098 Référence CVE CVE-2025-36123 https://www.cve.org/CVERecord?id=CVE-2025-36123 Référence CVE CVE-2025-36184 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0249Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-27901 Référence CVE CVE-2025-27903 https://www.cve.org/CVERecord?id=CVE-2025-27903 Référence CVE CVE-2025-27904 https://www.cve.org/CVERecord?id=CVE-2025-27904 Référence CVE CVE-2025-29927 https://www.cve.org/CVERecord?id=CVE-2025-29927 Référence CVE CVE-2025-30691 https://www.cve.org/CVERecord?id=CVE-2025-30691 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Référence CVE CVE-2025-30749 https://www.cve.org/CVERecord?id=CVE-2025-30749 Référence CVE CVE-2025-30754 https://www.cve.org/CVERecord?id=CVE-2025-30754 Référence CVE CVE-2025-30761 https://www.cve.org/CVERecord?id=CVE-2025-30761 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-32386 https://www.cve.org/CVERecord?id=CVE-2025-32386 Référence CVE CVE-2025-32387 https://www.cve.org/CVERecord?id=CVE-2025-32387 Référence CVE CVE-2025-32421 https://www.cve.org/CVERecord?id=CVE-2025-32421 Référence CVE CVE-2025-36001 https://www.cve.org/CVERecord?id=CVE-2025-36001 Référence CVE CVE-2025-36009 https://www.cve.org/CVERecord?id=CVE-2025-36009 Référence CVE CVE-2025-36070 https://www.cve.org/CVERecord?id=CVE-2025-36070 Référence CVE CVE-2025-36098 https://www.cve.org/CVERecord?id=CVE-2025-36098 Référence CVE CVE-2025-36123 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-27113 Référence CVE CVE-2025-27587 https://www.cve.org/CVERecord?id=CVE-2025-27587 Référence CVE CVE-2025-27817 https://www.cve.org/CVERecord?id=CVE-2025-27817 Référence CVE CVE-2025-27818 https://www.cve.org/CVERecord?id=CVE-2025-27818 Référence CVE CVE-2025-28162 https://www.cve.org/CVERecord?id=CVE-2025-28162 Référence CVE CVE-2025-28164 https://www.cve.org/CVERecord?id=CVE-2025-28164 Référence CVE CVE-2025-29480 https://www.cve.org/CVERecord?id=CVE-2025-29480 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-30258 https://www.cve.org/CVERecord?id=CVE-2025-30258 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-3198 https://www.cve.org/CVERecord?id=CVE-2025-3198 Référence CVE CVE-2025-32414 https://www.cve.org/CVERecord?id=CVE-2025-32414 Référence CVE CVE-2025-32415 https://www.cve.org/CVERecord?id=CVE-2025-32415 Référence CVE CVE-2025-32988 https://www.cve.org/CVERecord?id=CVE-2025-32988 Référence CVE CVE-2025-32989 https://www.cve.org/CVERecord?id=CVE-2025-32989 Référence CVE CVE-2025-32990 https://www.cve.org/CVERecord?id=CVE-2025-32990 Référence CVE CVE-2025-3360 https://www.cve.org/CVERecord?id=CVE-2025-3360 Référence CVE CVE-2025-37738 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0209Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-15469 Référence CVE CVE-2025-21861 https://www.cve.org/CVERecord?id=CVE-2025-21861 Référence CVE CVE-2025-22058 https://www.cve.org/CVERecord?id=CVE-2025-22058 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=CVE-2025-22873 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23143 https://www.cve.org/CVERecord?id=CVE-2025-23143 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-3360 https://www.cve.org/CVERecord?id=CVE-2025-3360 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=CVE-2025-38248 Référence CVE CVE-2025-38561 https://www.cve.org/CVERecord?id=CVE-2025-38561 Référence CVE CVE-2025-38584 https://www.cve.org/CVERecord?id=CVE-2025-38584 Référence CVE CVE-2025-39869 https://www.cve.org/CVERecord?id=CVE-2025-39869 Référence CVE CVE-2025-39873 https://www.cve.org/CVERecord?id=CVE-2025-39873 Référence CVE CVE-2025-39876 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-25193 Référence CVE CVE-2025-26646 https://www.cve.org/CVERecord?id=CVE-2025-26646 Référence CVE CVE-2025-27144 https://www.cve.org/CVERecord?id=CVE-2025-27144 Référence CVE CVE-2025-30204 https://www.cve.org/CVERecord?id=CVE-2025-30204 Référence CVE CVE-2025-30215 https://www.cve.org/CVERecord?id=CVE-2025-30215 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Référence CVE CVE-2025-30749 https://www.cve.org/CVERecord?id=CVE-2025-30749 Référence CVE CVE-2025-30754 https://www.cve.org/CVERecord?id=CVE-2025-30754 Référence CVE CVE-2025-30761 https://www.cve.org/CVERecord?id=CVE-2025-30761 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-31651 https://www.cve.org/CVERecord?id=CVE-2025-31651 Référence CVE CVE-2025-32414 https://www.cve.org/CVERecord?id=CVE-2025-32414 Référence CVE CVE-2025-32415 https://www.cve.org/CVERecord?id=CVE-2025-32415 Référence CVE CVE-2025-32988 https://www.cve.org/CVERecord?id=CVE-2025-32988 Référence CVE CVE-2025-32989 https://www.cve.org/CVERecord?id=CVE-2025-32989 Référence CVE CVE-2025-32990 https://www.cve.org/CVERecord?id=CVE-2025-32990 Référence CVE CVE-2025-38236 https://www.cve.org/CVERecord?id=CVE-2025-38236 Référence CVE CVE-2025-38248 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0112Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23419 https://www.cve.org/CVERecord?id=CVE-2025-23419 Référence CVE CVE-2025-28162 https://www.cve.org/CVERecord?id=CVE-2025-28162 Référence CVE CVE-2025-28164 https://www.cve.org/CVERecord?id=CVE-2025-28164 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-3360 https://www.cve.org/CVERecord?id=CVE-2025-3360 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=CVE-2025-39993 Référence CVE CVE-2025-40018 https://www.cve.org/CVERecord?id=CVE-2025-40018 Référence CVE CVE-2025-41242 https://www.cve.org/CVERecord?id=CVE-2025-41242 Référence CVE CVE-2025-41249 https://www.cve.org/CVERecord?id=CVE-2025-41249 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1138Multiples vulnérabilités dans VMware Tanzu Platform

port.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36640 Référence CVE CVE-2022-29526 https://www.cve.org/CVERecord?id=CVE-2022-29526 Référence CVE CVE-2023-48022 https://www.cve.org/CVERecord?id=CVE-2023-48022 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-34351 https://www.cve.org/CVERecord?id=CVE-2025-34351 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-2025-47907 Référence CVE CVE-2025-47910 https://www.cve.org/CVERecord?id=CVE-2025-47910 Référence CVE CVE-2025-47912 https://www.cve.org/CVERecord?id=CVE-2025-47912 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1129Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-24294 https://www.cve.org/CVERecord?id=CVE-2025-24294 Référence CVE CVE-2025-25184 https://www.cve.org/CVERecord?id=CVE-2025-25184 Référence CVE CVE-2025-25186 https://www.cve.org/CVERecord?id=CVE-2025-25186 Référence CVE CVE-2025-27111 https://www.cve.org/CVERecord?id=CVE-2025-27111 Référence CVE CVE-2025-27219 https://www.cve.org/CVERecord?id=CVE-2025-27219 Référence CVE CVE-2025-27220 https://www.cve.org/CVERecord?id=CVE-2025-27220 Référence CVE CVE-2025-27221 https://www.cve.org/CVERecord?id=CVE-2025-27221 Référence CVE CVE-2025-31133 https://www.cve.org/CVERecord?id=CVE-2025-31133 Référence CVE CVE-2025-32441 https://www.cve.org/CVERecord?id=CVE-2025-32441 Référence CVE CVE-2025-3573 https://www.cve.org/CVERecord?id=CVE-2025-3573 Référence CVE CVE-2025-43857 https://www.cve.org/CVERecord?id=CVE-2025-43857 Référence CVE CVE-2025-46727 https://www.cve.org/CVERecord?id=CVE-2025-46727 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-2025-4674 Référence CVE CVE-2025-47906 https://www.cve.org/CVERecord?id=CVE-2025-47906 Référence CVE CVE-2025-47907 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2025-021095Linux Foundation の runc における UNIX Symbolic Link のフォローに関する脆弱性

Linux Foundation の runc には、UNIX Symbolic Link のフォローに関する脆弱性、リンクフォロー時の競合状態に関する脆弱性が存在します。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6641MS 12월 보안 위협에 따른 정기 보안 업데이트 권고

cu() in get_netdev_for_sock(). | | Mariner | CVE-2025-40146 | blk-mq: fix potential deadlock while nr_requests grown | | Mariner | CVE-2025-40139 | smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set(). | | Mariner | CVE-2025-40136 | crypto: hisilicon/qm - request reserved interrupt for virtual function | | Mariner | CVE-2025-40135 | ipv6: use RCU in ip6_xmit() | | Mariner | CVE-2025-40111 | drm/vmwgfx: Fix Use-after-free in validation | | Mariner | CVE-2025-40110 | drm/vmwgfx: Fix a null-ptr access in the cursor snooper | | Mariner | CVE-2025-34297 | KissFFT Integer Overflow Heap Buffer Overflow via kiss_fft_alloc | | Mariner | CVE-2025-31133 | runc container escape via "masked path" abuse due to mount race conditions | | Mariner | CVE-2025-13837 | Out-of-memory when loading Plist | | Mariner | CVE-2025-13836 | Excessive read buffering DoS in http.client | | Microsoft Edge (Chromium-based) | CVE-2025-13721 | Chromium: CVE-2025-13721 v8에서 경합 | | Microsoft Edge (Chromium-based) | CVE-2025-13720 | Chromium: CVE-2025-13720 로더에서 잘못된 캐스트 | | Microsoft Edge (Chromium-based) | CVE-2025-13640 | Chromium: CVE-2025-13640 암호에서 부적절한 구현 | | Microsoft Edge (Chromium-based) | CVE-2025-13639 | Chromium: CVE-2025-13639 WebRTC에서 부적절한 구현 | | Microsoft Edge (Chromium-based) | CVE-2025-13638 | Chromiu

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6621MS 11월 보안 위협에 따른 정기 보안 업데이트 권고

-2025-52881 | runc: LSM labels can be bypassed with malicious config using dummy procfs files | | Mariner | CVE-2025-52565 | container escape due to /dev/console mount and related races | | Windows File Explorer | CVE-2025-50154 | Microsoft Windows 파일 탐색기 스푸핑 취약성 | | Windows Secure Boot | CVE-2025-47827 | MITRE CVE-2025-47827: IGEL OS 11 이전 버전에서 보안 부팅 바이패스 | | Microsoft Configuration Manager | CVE-2025-47179 | 구성 관리자 권한 상승 취약성 | | Mariner | CVE-2025-40109 | crypto: rng - Ensure set_ent is always present | | Mariner | CVE-2025-40107 | can: hi311x: fix null pointer dereference when resuming from sleep before interface was enabled | | Mariner | CVE-2025-31133 | runc container escape via "masked path" abuse due to mount race conditions | | Nuance PowerScribe | CVE-2025-30398 | Nuance PowerScribe 360 정보 공개 취약성 | | Microsoft PowerShell | CVE-2025-25004 | PowerShell 권한 상승 취약성 | | Mariner | CVE-2025-12875 | mruby array.c ary_fill_exec out-of-bounds write | | Mariner | CVE-2025-12863 | Libxml2: namespace use-after-free in xmlsettreedoc() function of libxml2 | | Microsoft Edge (Chromium-based) | CVE-2025-12729 | Chromium: CVE-2025-12729 Omnibox에서 부적절한 구현 | | Microsoft Edge (Chromium-based) | CVE-2025-12728 | Chromium: CVE-2025-12728 Omnibox에서 부적절한 구현 | | Microsoft Edge (Chromium-based) | CVE-2025-12727

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 6 Nov 2025 · Last source change 6 Nov 2025, 19:22 UTC · CWE-61 · UNIX Symbolic Link (Symlink) Following

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-37945
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.2.8; >= 1.3.0-rc.1, < 1.3.3; >= 1.4.0-rc.1, <= 1.4.0-rc.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 1.2.8; >= 1.3.0-rc.1, < 1.3.3; >= 1.4.0-rc.1, <= 1.4.0-rc.3 · Fixed: For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:4e989978ab0e24d7148f08e939800502370b761efea1005d87522884d1a3f595 All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor.
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed: rhcos-x86_64-412.86.202604010116-0 as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.s390x as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.src as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.12; runc-debuginfo-4:1.2.9-1.rhaos4.17.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.12; runc-debuginfo-4:1.2.9-1.rhaos4.17.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.12; runc-debuginfo-4:1.2.9-1.rhaos4.17.el8.s390x as a component of Red Hat OpenShift Container Platform 4.12; runc-debuginfo-4:1.2.9-1.rhaos4.17.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.12; runc-debugsource-4:1.2.9-1.rhaos4.17.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.12; runc-debugsource-4:1.2.9-1.rhaos4.17.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.12; runc-debugsource-4:1.2.9-1.rhaos4.17.el8.s390x as a component of Red Hat OpenShift Container Platform 4.12; runc-debugsource-4:1.2.9-1.rhaos4.17.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.9-1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.9-1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.9-1.rhaos4.16.el8.src as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.9-1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.13; runc-debuginfo-4:1.2.9-1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.13; runc-debuginfo-4:1.2.9-1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.13; runc-debuginfo-4:1.2.9-1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.13; runc-debuginfo-4:1.2.9-1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.13; runc-debugsource-4:1.2.9-1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.13; runc-debugsource-4:1.2.9-1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.13; runc-debugsource-4:1.2.9-1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.13; runc-debugsource-4:1.2.9-1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.5-2.rhaos4.17.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.14; runc-4:1.2.5-2.rhaos4.17.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.14; runc-4:1.2.5-2.rhaos4.17.el8.s390x as a component of Red Hat OpenShift Container Platform 4.14; and 1187 more
    After
    openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4 · Fixed: rhcos-x86_64-412.86.202604010116-0 as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.s390x as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.src as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.17.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.12; runc-debuginfo-4:1.2.9-1.rhaos4.17.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.12; runc-debuginfo-4:1.2.9-1.rhaos4.17.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.12; runc-debuginfo-4:1.2.9-1.rhaos4.17.el8.s390x as a component of Red Hat OpenShift Container Platform 4.12; runc-debuginfo-4:1.2.9-1.rhaos4.17.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.12; runc-debugsource-4:1.2.9-1.rhaos4.17.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.12; runc-debugsource-4:1.2.9-1.rhaos4.17.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.12; runc-debugsource-4:1.2.9-1.rhaos4.17.el8.s390x as a component of Red Hat OpenShift Container Platform 4.12; runc-debugsource-4:1.2.9-1.rhaos4.17.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.12; runc-4:1.2.9-1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.9-1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.9-1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.9-1.rhaos4.16.el8.src as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.9-1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.13; runc-debuginfo-4:1.2.9-1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.13; runc-debuginfo-4:1.2.9-1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.13; runc-debuginfo-4:1.2.9-1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.13; runc-debuginfo-4:1.2.9-1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.13; runc-debugsource-4:1.2.9-1.rhaos4.16.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.13; runc-debugsource-4:1.2.9-1.rhaos4.16.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.13; runc-debugsource-4:1.2.9-1.rhaos4.16.el8.s390x as a component of Red Hat OpenShift Container Platform 4.13; runc-debugsource-4:1.2.9-1.rhaos4.16.el8.x86_64 as a component of Red Hat OpenShift Container Platform 4.13; runc-4:1.2.5-2.rhaos4.17.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.14; runc-4:1.2.5-2.rhaos4.17.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.14; runc-4:1.2.5-2.rhaos4.17.el8.s390x as a component of Red Hat OpenShift Container Platform 4.14; and 1187 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-37945↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-9493-H29P-RFM2↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-31133 · cve.blacktree.nl