Official source article: Red Hat RHSA-2026:69961 ↗. Check the applicable product and release in the original source.
4.2MediumCVSS 3.1
Recommended action
Within 7 days
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Published severityMedium→Operational priority:Medium, 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.
Exploitation requires an existing local or physical foothold with privileges.
EPSS is 0.16% 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
Confirm that the asset runs Red Hat Red Hat Enterprise Linux 10 and falls inside the recorded affected range.
Verify the installed build against the product-specific fixed version after deployment.
Validate exposure, authentication requirements and compensating controls in the actual environment.
Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
Release-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
3 package states
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 release
Source package
Vendor state
Fixed version
Evidence
Debian trixietrixie · source
podman
Not affectedDebian marks this release not affected (fixed-version marker 0).
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.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products or versions as containing the fix.
podman-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-7:5.8.2-9.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-debugsource-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-debugsource-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
podman-debugsource-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
Summary
The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning. There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would only lead to invalid Quadlet files. However, security-related options from the end of the old Quadlet could be included in the new Quadlet, and if the truncation resulted in a valid Quadlet file, this could result in undesirable behavior. For example, running podman quadlet install --replace to remove a single line from the end of a Quadlet - including security-sensitive content, like AddCapability - will fail, and the option will continue to be used. Further, with Volume Quadlets, this can include additional mounts which can cause content to be unintentionally exposed into containers. If, later, the image is updated then compromised content might be leaked to an attacker. The vulnerable code paths are in pkg/domain/infra/abi/quadlet.go (lines 338-360, O_CREATE|O_WRONLY without O_TRUNC) and vendor/go.podman.io/storage/pkg/fileutils/reflink_linux.go (lines 12-19, non-truncating io.Copy fallback).
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
The vendor explicitly identifies these products as affected by this CVE.
podman as component of SUSE Linux Enterprise Server 16.1
podman-docker as component of SUSE Linux Enterprise Server 16.1
podman-remote as component of SUSE Linux Enterprise Server 16.1
podmansh as component of SUSE Linux Enterprise Server 16.1
podman as component of SUSE Linux Enterprise Server for SAP applications 16.1
podman-docker as component of SUSE Linux Enterprise Server for SAP applications 16.1
podman-remote as component of SUSE Linux Enterprise Server for SAP applications 16.1
podmansh as component of SUSE Linux Enterprise Server for SAP applications 16.1
Summary
The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning. There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would only lead to invalid Quadlet files. However, security-related options from the end of the old Quadlet could be included in the new Quadlet, and if the truncation resulted in a valid Quadlet file, this could result in undesirable behavior. For example, running podman quadlet install --replace to remove a single line from the end of a Quadlet - including security-sensitive content, like AddCapability - will fail, and the option will continue to be used. Further, with Volume Quadlets, this can include additional mounts which can cause content to be unintentionally exposed into containers. If, later, the image is updated then compromised content might be leaked to an attacker. The vulnerable code paths are in pkg/domain/infra/abi/quadlet.go (lines 338-360, O_CREATE|O_WRONLY without O_TRUNC) and vendor/go.podman.io/storage/pkg/fileutils/reflink_linux.go (lines 12-19, non-truncating io.Copy fallback).
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-2026-58187
No EUVD known-exploited evidence
The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning.
There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would only lead to invalid Quadlet files. However, security-related options from the end of the old Quadlet could be included in the new Quadlet, and if the truncation resulted in a valid Quadlet file, this could result in undesirable behavior. For example, running podman quadlet install --replace to remove a single line from the end of a Quadlet - including security-sensitive content, like AddCapability - will fail, and the option will continue to be used. Further, with Volume Quadlets, this can include additional mounts which can cause content to be unintentionally exposed into containers. If, later, the image is updated then compromised content might be leaked to an attacker.
The vulnerable code paths are in pkg/domain/infra/abi/quadlet.go (lines 338-360, O_CREATE|O_WRONLY without O_TRUNC) and vendor/go.podman.io/storage/pkg/fileutils/reflink_linux.go (lines 12-19, non-truncating io.Copy fallback).
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
4.2 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Patch available
01
What, why and how
The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning.
There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would only lead to invalid Quadlet files. However, security-related options from the end of the old Quadlet could be included in the new Quadlet, and if the truncation resulted in a valid Quadlet file, this could result in undesirable behavior. For example, running podman quadlet install --replace to remove a single line from the end of a Quadlet - including security-sensitive content, like AddCapability - will fail, and the option will continue to be used. Further, with Volume Quadlets, this can include additional mounts which can cause content to be unintentionally exposed into containers. If, later, the image is updated then compromised content might be leaked to an attacker.
The vulnerable code paths are in pkg/domain/infra/abi/quadlet.go (lines 338-360, O_CREATE|O_WRONLY without O_TRUNC) and vendor/go.podman.io/storage/pkg/fileutils/reflink_linux.go (lines 12-19, non-truncating io.Copy fallback).
What
The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning.
There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would only lead to invalid Quadlet files. However, security-related options from the end of the old Quadlet could be included in the new Quadlet, and if the truncation resulted in a valid Quadlet file, this could result in undesirable behavior. For example, running podman quadlet install --replace to remove a single line from the end of a Quadlet - including security-sensitive content, like AddCapability - will fail, and the option will continue to be used. Further, with Volume Quadlets, this can include additional mounts which can cause content to be unintentionally exposed into containers. If, later, the image is updated then compromised content might be leaked to an attacker.
The vulnerable code paths are in pkg/domain/infra/abi/quadlet.go (lines 338-360, O_CREATE|O_WRONLY without O_TRUNC) and vendor/go.podman.io/storage/pkg/fileutils/reflink_linux.go (lines 12-19, non-truncating io.Copy fallback).
Why
The product does not properly clean up and remove temporary or supporting resources after they have been used.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning.
There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would only lead to invalid Quadlet files. However, security-related options from the end of the old Quadlet could be included in the new Quadlet, and if the truncation resulted in a valid Quadlet file, this could result in undesirable behavior. For example, running podman quadlet install --replace to remove a single line from the end of a Quadlet - including security-sensitive content, like AddCapability - will fail, and the option will continue to be used. Further, with Volume Quadlets, this can include additional mounts which can cause content to be unintentionally exposed into containers. If, later, the image is updated then compromised content might be leaked to an attacker.
The vulnerable code paths are in pkg/domain/infra/abi/quadlet.go (lines 338-360, O_CREATE|O_WRONLY without O_TRUNC) and vendor/go.podman.io/storage/pkg/fileutils/reflink_linux.go (lines 12-19, non-truncating io.Copy fallback).
Why
The product does not properly clean up and remove temporary or supporting resources after they have been used.
How
An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
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
CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
Likely attack path
local access → Incomplete Cleanup → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-459: Incomplete Cleanup. The product does not properly clean up and remove temporary or supporting resources after they have been used.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited 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.
CWE-459Public exploit reference
A
Official authority intelligence
Only matched European and national findings are included. Language selectors and unavailable sources are omitted.
ENISA EUVD · EUVD-2026-58187Official EUVD mapping
The 'podman quadlet install --replace' command opens the existing destination file with O_CREATE|O_WRONLY but omits O_TRUNC. When the initial reflink copy attempt fails (common on non-reflink-capable filesystems including many RHEL default XFS configurations), the fallback in ReflinkOrCopy uses io.Copy which performs a non-truncating write. If the original Quadlet is larger than the new Quadlet, the file is not truncated and content from the original is preserved. The command completes with no warning.
There is no risk of information leakage as the user already had access to the Quadlet in order to replace it, and in most cases, this would only lead to invalid Quadlet files. However, security-related options from the end of the old Quadlet could be included in the new Quadlet, and if the truncation resulted in a valid Quadlet file, this could result in undesirable behavior. For example, running podman quadlet install --replace to remove a single line from the end of a Quadlet - including security-sensitive content, like AddCapability - will fail, and the option will continue to be used. Further, with Volume Quadlets, this can include additional mounts which can cause content to be unintentionally exposed into containers. If, later, the image is updated then compromised content might be leaked to an attacker.
The vulnerable code paths are in pkg/domain/infra/abi/quadlet.go (lines 338-360, O_CREATE|O_WRONLY without O_TRUNC) and vendor/go.podman.io/storage/pkg/fileutils/reflink_linux.go (lines 12-19, non-truncating io.Copy fallback).
Official EUVD record ↗BSI · German · WID-SEC-2026-2846Podman: Schwachstelle ermöglicht nicht spezifizierten Angriff und Offenlegung von Informationen
Ein lokaler Angreifer kann eine Schwachstelle in Podman ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, und um Informationen offenzulegen..
Official advisory ↗Cyber Security Agency of Singapore · English · CSA-SB-20260819Security Bulletin 19 Aug 2026
The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 19 Aug 2026, published on 19 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.
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.
Affected versionsThe structured affected or fixed version information changed.
Before
podman.src as a component of Red Hat Hardened Images · Fixed: podman-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-docker-7:5.8.2-9.el10_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-6:5.8.2-7.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.src as a component of Red Hat Enterprise Linux AppStream (v. 9); and 54 more
After
Fixed: podman-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-docker-7:5.8.2-9.el10_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-6:5.8.2-7.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.src as a component of Red Hat Enterprise Linux AppStream (v. 9); and 54 more
Affected versionsThe structured affected or fixed version information changed.
Before
See the vendor and CVE records for the affected range. · Fixed: Red Hat Enterprise Linux 10: 7:5.8.2-9.el10_2 < *
After
See the vendor and CVE records for the affected range. · Fixed: Red Hat Enterprise Linux 10: 7:5.8.2-9.el10_2 < *; Red Hat Enterprise Linux 9: 6:5.8.2-7.el9_8 < *
Affected versionsThe structured affected or fixed version information changed.
Before
podman as a component of Red Hat Enterprise Linux 9; podman-catatonit as a component of Red Hat Enterprise Linux 9; podman-docker as a component of Red Hat Enterprise Linux 9; podman-gvproxy as a component of Red Hat Enterprise Linux 9; podman-plugins as a component of Red Hat Enterprise Linux 9; podman-remote as a component of Red Hat Enterprise Linux 9; podman-tests as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Hardened Images · Fixed: podman-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-docker-7:5.8.2-9.el10_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); and 16 more
After
podman.src as a component of Red Hat Hardened Images · Fixed: podman-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-docker-7:5.8.2-9.el10_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-6:5.8.2-7.el9_8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9); podman-6:5.8.2-7.el9_8.src as a component of Red Hat Enterprise Linux AppStream (v. 9); and 54 more
Affected versionsThe structured affected or fixed version information changed.
Before
podman as a component of Red Hat Enterprise Linux 10; podman-docker as a component of Red Hat Enterprise Linux 10; podman-remote as a component of Red Hat Enterprise Linux 10; podman-tests as a component of Red Hat Enterprise Linux 10; podman.src as a component of Red Hat Enterprise Linux 10; podman as a component of Red Hat Enterprise Linux 9; podman-catatonit as a component of Red Hat Enterprise Linux 9; podman-docker as a component of Red Hat Enterprise Linux 9; podman-gvproxy as a component of Red Hat Enterprise Linux 9; podman-plugins as a component of Red Hat Enterprise Linux 9; podman-remote as a component of Red Hat Enterprise Linux 9; podman-tests as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Hardened Images
After
podman as a component of Red Hat Enterprise Linux 9; podman-catatonit as a component of Red Hat Enterprise Linux 9; podman-docker as a component of Red Hat Enterprise Linux 9; podman-gvproxy as a component of Red Hat Enterprise Linux 9; podman-plugins as a component of Red Hat Enterprise Linux 9; podman-remote as a component of Red Hat Enterprise Linux 9; podman-tests as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Enterprise Linux 9; podman.src as a component of Red Hat Hardened Images · Fixed: podman-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debugsource-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-docker-7:5.8.2-9.el10_2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-remote-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-tests-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.aarch64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.ppc64le as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.s390x as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); podman-debuginfo-7:5.8.2-9.el10_2.x86_64 as a component of Red Hat Enterprise Linux CodeReady Linux Builder (v. 10); and 16 more
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.
BlackTreeCVE Intelligence