ALSA-2026:97533 (CVE-2026-46597)
Vulnerability from osv_almalinux – Published: 2026-11-10 00:00 – Updated: 2026-11-17 10:22 – Source websiteThe podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes.
Security Fix(es):
- golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted AES-GCM packet decoder inputs (CVE-2026-46597)
Bug Fix(es) and Enhancement(s):
- When using
--mountinpodman runresults can be inconsistent, especially on /var/tmp (JIRA:RHEL-154348) - [RFE] SELinux confined users unable to start podman.socket systemd user service (JIRA:RHEL-132875)
- [RFE] Mounting of NFS Quadlet volume fails with permission denied (JIRA:RHEL-145863)
- [RFE] podman API socket to support TLS/mTLS (JIRA:RHEL-91221)
- Rebase podman to the latest upstream release [rhel-9.9] (JIRA:RHEL-168737)
- podman does not clean up all files and leaves orphaned files consuming disk space [rhel-9.9] (JIRA:RHEL-173976)
- [FJ9.8 Bug]: [REG]The "podman-remote save" command fails for rootless users. (JIRA:RHEL-186006)
- podman: rebase to 5.8.5 (JIRA:RHEL-212537)
- [FJ9.9 Bug]: [REG]The "podman rm" command can accidentally delete containers even though it is mounted by Buildah when used by a rootless user in remote. (JIRA:RHEL-211092)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Additional Changes:
For detailed information on changes in this release, see the AlmaLinux 9 Release Notes linked from the References section.
{
"affected": [
{
"package": {
"ecosystem": "AlmaLinux:9",
"name": "podman"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6:5.8.5-2.el9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:9",
"name": "podman-docker"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6:5.8.5-2.el9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:9",
"name": "podman-plugins"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6:5.8.5-2.el9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:9",
"name": "podman-remote"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6:5.8.5-2.el9"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:9",
"name": "podman-tests"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6:5.8.5-2.el9"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"details": "The podman tool manages pods, container images, and containers. It is part of the libpod library, which is for applications that use container pods. Container pods is a concept in Kubernetes. \n\nSecurity Fix(es): \n\n * golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted AES-GCM packet decoder inputs (CVE-2026-46597)\n\n\nBug Fix(es) and Enhancement(s): \n\n * When using `--mount` in `podman run` results can be inconsistent, especially on /var/tmp (JIRA:RHEL-154348)\n * [RFE] SELinux confined users unable to start podman.socket systemd user service (JIRA:RHEL-132875)\n * [RFE] Mounting of NFS Quadlet volume fails with permission denied (JIRA:RHEL-145863)\n * [RFE] podman API socket to support TLS/mTLS (JIRA:RHEL-91221)\n * Rebase podman to the latest upstream release [rhel-9.9] (JIRA:RHEL-168737)\n * podman does not clean up all files and leaves orphaned files consuming disk space [rhel-9.9] (JIRA:RHEL-173976)\n * [FJ9.8 Bug]: [REG]The \"podman-remote save\" command fails for rootless users. (JIRA:RHEL-186006)\n * podman: rebase to 5.8.5 (JIRA:RHEL-212537)\n * [FJ9.9 Bug]: [REG]The \"podman rm\" command can accidentally delete containers even though it is mounted by Buildah when used by a rootless user in remote. (JIRA:RHEL-211092)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. \n\nAdditional Changes: \n\nFor detailed information on changes in this release, see the AlmaLinux 9 Release Notes linked from the References section.\n",
"id": "ALSA-2026:97533",
"modified": "2026-11-17T10:22:14Z",
"published": "2026-11-10T00:00:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2026:97533"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-46597"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2480678"
},
{
"type": "ADVISORY",
"url": "https://errata.almalinux.org/9/ALSA-2026-97533.html"
}
],
"related": [
"CVE-2026-46597"
],
"schema_version": "1.7.0",
"summary": "Important: podman security, bug fix, and enhancement update",
"upstream": [
"CVE-2026-46597"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.