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

container escape due to /dev/console mount and related races

opencontainers · runc

Official source article: GitHub GHSA-QW9X-CQR3-WC7R ↗. Check the applicable product and release in the original source.

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

High technical severity with public exploit material referenced by a structured source; 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.56% 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.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

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: Within 30 daysRemediation target: Within 180 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 1.0.0-rc3; 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.0.0-rc3, <= 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.

2 current
CVE-2025-52565 · CSAF 2.0 · revision 60 · interimSUSE Product Security TeamCVE-2025-52565
58 known affected

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

  • nvidia-container-toolkit as component of SLES-LTSS-TERADATA 15 SP2
  • runc as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nvidia-container-toolkit as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • runc as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nvidia-container-toolkit as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
  • nvidia-container-toolkit as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • nvidia-container-toolkit as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • nvidia-container-toolkit as component of SUSE Linux Enterprise High Performance Computing 15 SP4
  • nvidia-container-toolkit as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • nvidia-container-toolkit as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • nvidia-container-toolkit as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • runc as component of SUSE Linux Enterprise High Performance Computing 15
Summary
runc is a CLI tool for spawning and running containers according to the OCI specification. Versions 1.0.0-rc3 through 1.2.7, 1.3.0-rc.1 through 1.3.2, and 1.4.0-rc.1 through 1.4.0-rc.2, due to insufficient checks when bind-mounting `/dev/pts/$n` to `/dev/console` inside the container, an attacker can trick runc into bind-mounting paths which would normally be made read-only or be masked onto a path that the attacker can write to. This attack is very similar in concept and application to CVE-2025-31133, except that it attacks a similar vulnerability in a different target (namely, the bind-mount of `/dev/pts/$n` to `/dev/console` as configured for all containers that allocate a console). This happens after `pivot_root(2)`, so this cannot be used to write to host files directly -- however, as with CVE-2025-31133, this can load to denial of service of the host or a container breakout by providing the attacker with a writable copy of `/proc/sysrq-trigger` or `/proc/sys/kernel/core_pattern` (respectively). This issue is fixed in versions 1.2.8, 1.3.3 and 1.4.0-rc.3.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-52565 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityrunc: container escape with malicious config due to /dev/console mount and related races
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. CVE-2025-52565 is very similar in concept and application toCVE-2025-31133, except that it exploits a flaw in /dev/console bind-mounts. When creating the /dev/console bind-mount (to /dev/pts/$n), if an attacker replaces /dev/pts/$n with a symlink then runc will bind-mount the symlink target over /dev/console.
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-37944

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 with public exploit material referenced by a structured source; 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. Versions 1.0.0-rc3 through 1.2.7, 1.3.0-rc.1 through 1.3.2, and 1.4.0-rc.1 through 1.4.0-rc.2, due to insufficient checks when bind-mounting `/dev/pts/$n` to `/dev/console` inside the container, an attacker can trick runc into bind-mounting paths which would normally be made read-only or be masked onto a path that the attacker can write to. This attack is very similar in concept and application to CVE-2025-31133, except that it attacks a similar vulnerability in a different target (namely, the bind-mount of `/dev/pts/$n` to `/dev/console` as configured for all containers that allocate a console). This happens after `pivot_root(2)`, so this cannot be used to write to host files directly -- however, as with CVE-2025-31133, this can load to denial of service of the host or a container breakout by providing the attacker with a writable copy of `/proc/sysrq-trigger` or `/proc/sys/kernel/core_pattern` (respectively). 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. Versions 1.0.0-rc3 through 1.2.7, 1.3.0-rc.1 through 1.3.2, and 1.4.0-rc.1 through 1.4.0-rc.2, due to insufficient checks when bind-mounting `/dev/pts/$n` to `/dev/console` inside the container, an attacker can trick runc into bind-mounting paths which would normally be made read-only or be masked onto a path that the attacker can write to. This attack is very similar in concept and application to CVE-2025-31133, except that it attacks a similar vulnerability in a different target (namely, the bind-mount of `/dev/pts/$n` to `/dev/console` as configured for all containers that allocate a console). This happens after `pivot_root(2)`, so this cannot be used to write to host files directly -- however, as with CVE-2025-31133, this can load to denial of service of the host or a container breakout by providing the attacker with a writable copy of `/proc/sysrq-trigger` or `/proc/sys/kernel/core_pattern` (respectively). 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 when the stated preconditions are met. If successful, the issue may disrupt the affected service.

What

runc is a CLI tool for spawning and running containers according to the OCI specification. Versions 1.0.0-rc3 through 1.2.7, 1.3.0-rc.1 through 1.3.2, and 1.4.0-rc.1 through 1.4.0-rc.2, due to insufficient checks when bind-mounting `/dev/pts/$n` to `/dev/console` inside the container, an attacker can trick runc into bind-mounting paths which would normally be made read-only or be masked onto a path that the attacker can write to. This attack is very similar in concept and application to CVE-2025-31133, except that it attacks a similar vulnerability in a different target (namely, the bind-mount of `/dev/pts/$n` to `/dev/console` as configured for all containers that allocate a console). This happens after `pivot_root(2)`, so this cannot be used to write to host files directly -- however, as with CVE-2025-31133, this can load to denial of service of the host or a container breakout by providing the attacker with a writable copy of `/proc/sysrq-trigger` or `/proc/sys/kernel/core_pattern` (respectively). 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 when the stated preconditions are met. If successful, the issue may disrupt the affected service.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
local access → UNIX Symbolic Link (Symlink) Following → disrupt the affected service
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Passive 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:N/PR:N/UI:P/VC:N/VI:H/VA:N/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.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.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.
UnauthenticatedDenial of serviceCWE-61Public exploit reference
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-47907 Référence CVE CVE-2025-47911 https://www.cve.org/CVERecord?id=CVE-2025-47911 Référence CVE CVE-2025-47913 https://www.cve.org/CVERecord?id=CVE-2025-47913 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-49146 https://www.cve.org/CVERecord?id=CVE-2025-49146 Référence CVE CVE-2025-49844 https://www.cve.org/CVERecord?id=CVE-2025-49844 Référence CVE CVE-2025-50059 https://www.cve.org/CVERecord?id=CVE-2025-50059 Référence CVE CVE-2025-50106 https://www.cve.org/CVERecord?id=CVE-2025-50106 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-55130 https://www.cve.org/CVERecord?id=CVE-2025-55130 Référence CVE CVE-2025-55131 https://www.cve.org/CVERecord?id=CVE-2025-55131 Référence CVE CVE-2025-55132 https://www.cve.org/CVERecord?id=CVE-2025-55132 Référence CVE CVE-2025-55159 https://www.cve.org/CVERecord?id=CVE-2025-55159 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=

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

ord?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-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48514 https://www.cve.org/CVERecord?id=CVE-2025-48514 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-5222 https://www.cve.org/CVERecord?id=CVE-2025-5222 Référence CVE CVE-2025-52534 https://www.cve.org/CVERecord?id=CVE-2025-52534 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-5278 https://www.cve.org/CVERecord?id=CVE-2025-5278 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53859 https://www.cve.org/CVERecord?id=CVE-2025-53859 Référence CVE CVE-2025-53864 https://www.cve.org/CVERecord?id=CVE-2025-53864 Référence CVE CVE-2025-54514 https://www.cve.org/CVERecord?id=CVE-2025-54514 Référence CVE CVE-2025-54770 https://www.cve.org/CVERecord?id=CVE-2025-54770 Référence CVE CVE-2025-54771 https://www.cve.org/CVERecord?id=CVE-2025-54771 Référence CVE CVE-2025-55130 https://www.cve.org/CVERecord?id=CV

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

ord?id=CVE-2025-47907 Référence CVE CVE-2025-47908 https://www.cve.org/CVERecord?id=CVE-2025-47908 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-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48514 https://www.cve.org/CVERecord?id=CVE-2025-48514 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-5222 https://www.cve.org/CVERecord?id=CVE-2025-5222 Référence CVE CVE-2025-52534 https://www.cve.org/CVERecord?id=CVE-2025-52534 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-5278 https://www.cve.org/CVERecord?id=CVE-2025-5278 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53859 https://www.cve.org/CVERecord?id=CVE-2025-53859 Référence CVE CVE-2025-54514 https://www.cve.org/CVERecord?id=CVE-2025-54514 Référence CVE CVE-2025-54770 https://www.cve.org/CVERecord?id=CVE-2025-54770 Référence CVE CVE-2025-54771 https://www.cve.org/CVERecord?id=CVE-2025-54771 Référence CVE CVE-2025-55130 https://www.cve.org/CVERecord?id=CVE-2025-55130 Référence CVE CVE-2025-55131 https://www.cve.org/CVERecord?id=CV

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

ecord?id=CVE-2025-47944 Référence CVE CVE-2025-48068 https://www.cve.org/CVERecord?id=CVE-2025-48068 Référence CVE CVE-2025-48387 https://www.cve.org/CVERecord?id=CVE-2025-48387 Référence CVE CVE-2025-48997 https://www.cve.org/CVERecord?id=CVE-2025-48997 Référence CVE CVE-2025-49128 https://www.cve.org/CVERecord?id=CVE-2025-49128 Référence CVE CVE-2025-50106 https://www.cve.org/CVERecord?id=CVE-2025-50106 Référence CVE CVE-2025-50537 https://www.cve.org/CVERecord?id=CVE-2025-50537 Référence CVE CVE-2025-5187 https://www.cve.org/CVERecord?id=CVE-2025-5187 Référence CVE CVE-2025-5222 https://www.cve.org/CVERecord?id=CVE-2025-5222 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-53547 https://www.cve.org/CVERecord?id=CVE-2025-53547 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-55173 https://www.cve.org/CVERecord?id=CVE-2025-55173 Référence CVE CVE-2025-55183 https://www.cve.org/CVERecord?id=

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

g/CVERecord?id=CVE-2025-49795 Référence CVE CVE-2025-49796 https://www.cve.org/CVERecord?id=CVE-2025-49796 Référence CVE CVE-2025-50181 https://www.cve.org/CVERecord?id=CVE-2025-50181 Référence CVE CVE-2025-50182 https://www.cve.org/CVERecord?id=CVE-2025-50182 Référence CVE CVE-2025-5025 https://www.cve.org/CVERecord?id=CVE-2025-5025 Référence CVE CVE-2025-5115 https://www.cve.org/CVERecord?id=CVE-2025-5115 Référence CVE CVE-2025-5222 https://www.cve.org/CVERecord?id=CVE-2025-5222 Référence CVE CVE-2025-5244 https://www.cve.org/CVERecord?id=CVE-2025-5244 Référence CVE CVE-2025-5245 https://www.cve.org/CVERecord?id=CVE-2025-5245 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-53864 https://www.cve.org/CVERecord?id=CVE-2025-53864 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-55198 https://www.cve.org/CVERecord?id=CVE-2025-55198 Référence CVE CVE-2025-55199 https://www.cve.org/CVERecord?id=CVE-2025-55199 Référence CVE CVE-2025-58056 https://www.cve.org/CVERecord?id=

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

ERecord?id=CVE-2025-41253 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 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-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=CVE-2025-58181 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=CVE-2025-58185 Référence CVE CVE-2025-58186 https://www.cve.org/CVERecord?id=CVE-2025-58186 Référence CVE CVE-2025-58187 https://www.cve.org/CVERecord?id=CVE-2025-58187 Référence CVE CVE-2025-58188 https://www.cve.org/CVERecord?id=CVE-2025-58188 Référence CVE CVE-2025-58189 https://www.cve.org/CVERecord?id=

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

ecord?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-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-4947 https://www.cve.org/CVERecord?id=CVE-2025-4947 Référence CVE CVE-2025-50059 https://www.cve.org/CVERecord?id=CVE-2025-50059 Référence CVE CVE-2025-50106 https://www.cve.org/CVERecord?id=CVE-2025-50106 Référence CVE CVE-2025-5025 https://www.cve.org/CVERecord?id=CVE-2025-5025 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-52999 https://www.cve.org/CVERecord?id=CVE-2025-52999 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-55752 https://www.cve.org/CVERecord?id=CVE-2025-55752 Référence CVE CVE-2025-55753 https://www.cve.org/CVERecord?id=

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

cord?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-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48060 https://www.cve.org/CVERecord?id=CVE-2025-48060 Référence CVE CVE-2025-48989 https://www.cve.org/CVERecord?id=CVE-2025-48989 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-53547 https://www.cve.org/CVERecord?id=CVE-2025-53547 Référence CVE CVE-2025-54388 https://www.cve.org/CVERecord?id=CVE-2025-54388 Référence CVE CVE-2025-54410 https://www.cve.org/CVERecord?id=CVE-2025-54410 Référence CVE CVE-2025-55198 https://www.cve.org/CVERecord?id=CVE-2025-55198 Référence CVE CVE-2025-55199 https://www.cve.org/CVERecord?id=

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

ecord?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-2025-48924 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=CVE-2025-58185 Référence CVE CVE-2025-58186 https://www.cve.org/CVERecord?id=CVE-2025-58186 Référence CVE CVE-2025-58187 https://www.cve.org/CVERecord?id=CVE-2025-58187 Référence CVE CVE-2025-58188 https://www.cve.org/CVERecord?id=CVE-2025-58188 Référence CVE CVE-2025-58189 https://www.cve.org/CVERecord?id=CVE-2025-58189 Référence CVE CVE-2025-61723 https://www.cve.org/CVERecord?id=

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

ecord?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-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-47914 https://www.cve.org/CVERecord?id=CVE-2025-47914 Référence CVE CVE-2025-48924 https://www.cve.org/CVERecord?id=CVE-2025-48924 Référence CVE CVE-2025-52565 https://www.cve.org/CVERecord?id=CVE-2025-52565 Référence CVE CVE-2025-52881 https://www.cve.org/CVERecord?id=CVE-2025-52881 Référence CVE CVE-2025-53057 https://www.cve.org/CVERecord?id=CVE-2025-53057 Référence CVE CVE-2025-53066 https://www.cve.org/CVERecord?id=CVE-2025-53066 Référence CVE CVE-2025-54388 https://www.cve.org/CVERecord?id=CVE-2025-54388 Référence CVE CVE-2025-55163 https://www.cve.org/CVERecord?id=CVE-2025-55163 Référence CVE CVE-2025-57352 https://www.cve.org/CVERecord?id=CVE-2025-57352 Référence CVE CVE-2025-58056 https://www.cve.org/CVERecord?id=CVE-2025-58056 Référence CVE CVE-2025-58181 https://www.cve.org/CVERecord?id=

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

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

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

ted File System | CVE-2025-55233 | Windows 예상 파일 시스템 권한 상승 취약성 | | Mariner | CVE-2025-54771 | Grub2: use-after-free in grub_file_close() | | Mariner | CVE-2025-54770 | Grub2: use-after-free in net_set_vlan | | Windows Connected Devices Platform Service | CVE-2025-54114 | Windows Connected Devices Platform Service Elevation of Privilege Vulnerability | | Windows PowerShell | CVE-2025-54100 | PowerShell 원격 코드 실행 취약성 | | Windows Ancillary Function Driver for WinSock | CVE-2025-54099 | WinSock용 Windows 보조 기능 드라이버 권한 상승 취약성 | | Mariner | CVE-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 | | Software for Open Networking in the Cloud (SONiC) | CVE-2025-49752 | Azure Bastion 권한 상승 취약성 | | Mariner | CVE-2025-47913 | Potential denial of service in golang.org/x/crypto/ssh/agent | | Mariner | CVE-2025-40324 | NFSD: Fix crash in nfsd4_read_release() | | Mariner | CVE-2025-40323 | fbcon: Set fb_display[i]->mode to NULL when the mode is released | | Mariner | CVE-2025-40322 | fbdev: bitblit: bound-check glyph index in bit_putcs* | | Mariner | CVE-2025-40321 | wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode | | Mariner | CVE-2025-40319 | bpf: Sy

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

원격 코드 실행 취약성 | | Microsoft Office Excel | CVE-2025-53739 | Microsoft Excel 원격 코드 실행 취약성 | | Microsoft Office Word | CVE-2025-53738 | Microsoft Word 원격 코드 실행 취약성 | | Microsoft Office Excel | CVE-2025-53737 | Microsoft Excel 원격 코드 실행 취약성 | | Microsoft Office Word | CVE-2025-53736 | Microsoft Word 정보 유출 취약성 | | Microsoft Office Excel | CVE-2025-53735 | Microsoft Excel 원격 코드 실행 취약성 | | Microsoft Office Word | CVE-2025-53733 | Microsoft Word 원격 코드 실행 취약성 | | Microsoft Office | CVE-2025-53731 | Microsoft Office 원격 코드 실행 취약성 | | Mariner | CVE-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-2

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
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.
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, 21:32 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-37944
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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.0.0-rc3, < 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.0.0-rc3, < 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 1199 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 1199 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-37944↗Vendor CSAF · SUSE Product Security Team↗Red Hat Product Security security advisory↗Public exploit reference · GitHub GHSA-QW9X-CQR3-WC7R↗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-52565 · cve.blacktree.nl