CVE-2026-57231

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Podman is a tool for managing OCI containers and pods. From 1.8.1 until 5.8.4, a container image that contains a environment variable with just a key and no value can trick podman into passing that variable from the host into the container. This is made worse by the fact that using an asterisk (*) will cause podman to pass all host variables into the container. So essentially a malicious image can exfiltrate all podman environment variables that are set in the session from where the container is launched. This vulnerability is fixed in 5.8.4 and 6.0.0.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Malformed Image can trick podman run into leaking host environment variables into the container · Advisory · podman-container-tools/podman · GitHub

https://github.com/podman-container-tools/podman/security/advisories/GHSA-4hq8-gpf5-8p68
github_commit

commit 6c431b73dbf8 (podman-container-tools/podman)

Fix landed in podman-container-tools/podman commit 6c431b73dbf8 — awaiting tagged release

https://github.com/podman-container-tools/podman/commit/6c431b73dbf8e4b20b778644d7a80caebdb75050

Vendor Advisories for CVE-2026-57231(9)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatquay/quay-rhel8:17863950652026-08-11redhat
redhatquay/quay-rhel8:17861706352026-08-10redhat
redhatquay/quay-rhel8:17859500042026-08-05redhat
redhatrhcos-4.22.9.8.202607220526-02026-07-28redhat
redhatcontainer-tools:rhel8-8100020260709093628.afee755d2026-07-13redhat
redhatpodman-7:5.8.2-4.el10_22026-07-09redhat
redhatpodman-6:5.8.2-4.el9_82026-07-09redhat
redhatpodman-main-6.0.0-1.hum12026-06-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
podman5.4.2+ds1-2 ... 5.8.3+ds1-1 (21 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
podman5.4.2+ds1-2 ... 5.8.3+ds1-1 (21 versions)——

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 104× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 19:49 UTCVendor advisory
  3. 2026-08-20 06:50 UTCEG score recompute
  4. 2026-08-20 06:50 UTCVendor advisory
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-19 12:53 UTCVendor advisory
  7. 2026-08-18 23:55 UTCEG score recompute
  8. 2026-08-18 23:55 UTCVendor advisory
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 14:35 UTCEG score recompute
  11. 2026-08-17 14:35 UTCVendor advisory
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 01:36 UTCEG score recompute
  14. 2026-08-17 01:36 UTCVendor advisory
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 12:37 UTCEG score recompute
  17. 2026-08-16 12:37 UTCVendor advisory
  18. 2026-08-16 02:14 UTCEPSS rescore
  19. 2026-08-15 23:38 UTCVendor advisory
  20. 2026-08-15 10:39 UTCEG score recompute
  21. 2026-08-15 10:39 UTCVendor advisory
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 21:39 UTCVendor advisory
  24. 2026-08-14 08:40 UTCEG score recompute
  25. 2026-08-14 08:40 UTCVendor advisory
Show 75 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 19:41 UTCVendor advisory
  3. 2026-08-13 06:42 UTCVendor advisory
  4. 2026-08-12 17:43 UTCEG score recompute
  5. 2026-08-12 17:43 UTCVendor advisory
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-12 04:44 UTCVendor advisory
  8. 2026-08-11 15:45 UTCEG score recompute
  9. 2026-08-11 15:45 UTCVendor advisory
  10. 2026-08-11 02:46 UTCEG score recompute
  11. 2026-08-11 02:46 UTCVendor advisory
  12. 2026-08-11 00:00 UTCEPSS rescore
  13. 2026-08-10 13:47 UTCVendor advisory
  14. 2026-08-10 00:48 UTCEG score recompute
  15. 2026-08-10 00:48 UTCVendor advisory
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-09 11:49 UTCVendor advisory
  18. 2026-08-08 22:50 UTCEG score recompute
  19. 2026-08-08 22:50 UTCVendor advisory
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-08 09:50 UTCVendor advisory
  22. 2026-08-07 20:51 UTCEG score recompute
  23. 2026-08-07 20:51 UTCVendor advisory
  24. 2026-08-07 07:52 UTCVendor advisory
  25. 2026-08-06 18:53 UTCEG score recompute
  26. 2026-08-06 18:53 UTCVendor advisory
  27. 2026-08-06 13:47 UTCEPSS rescore
  28. 2026-08-06 05:54 UTCEG score recompute
  29. 2026-08-06 05:54 UTCVendor advisory
  30. 2026-08-05 19:17 UTCEPSS rescore
  31. 2026-08-05 16:55 UTCVendor advisory
  32. 2026-08-05 03:56 UTCEG score recompute
  33. 2026-08-05 03:56 UTCVendor advisory
  34. 2026-08-04 15:10 UTCEPSS rescore
  35. 2026-08-04 14:57 UTCEG score recompute
  36. 2026-08-04 14:57 UTCVendor advisory
  37. 2026-08-04 10:39 UTCEPSS rescore
  38. 2026-08-03 21:41 UTCEG score recompute
  39. 2026-08-03 21:41 UTCVendor advisory
  40. 2026-08-03 10:36 UTCEPSS rescore
  41. 2026-08-03 08:41 UTCVendor advisory
  42. 2026-08-02 19:37 UTCVendor advisory
  43. 2026-08-02 06:38 UTCEG score recompute
  44. 2026-08-02 06:38 UTCVendor advisory
  45. 2026-08-02 02:27 UTCEPSS rescore
  46. 2026-08-01 17:38 UTCVendor advisory
  47. 2026-08-01 04:38 UTCEG score recompute
  48. 2026-08-01 04:38 UTCVendor advisory
  49. 2026-08-01 04:16 UTCEPSS rescore
  50. 2026-07-31 15:39 UTCVendor advisory
  51. 2026-07-31 02:22 UTCEG score recompute
  52. 2026-07-31 02:22 UTCVendor advisory
  53. 2026-07-30 16:28 UTCEPSS rescore
  54. 2026-07-30 13:23 UTCEG score recompute
  55. 2026-07-30 13:23 UTCVendor advisory
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-30 01:30 UTCEPSS rescore
  58. 2026-07-30 00:17 UTCVendor advisory
  59. 2026-07-29 09:25 UTCVendor advisory
  60. 2026-07-28 20:26 UTCEG score recompute
  61. 2026-07-28 20:26 UTCVendor advisory
  62. 2026-07-28 15:37 UTCEPSS rescore
  63. 2026-07-28 06:06 UTCVendor advisory
  64. 2026-07-27 17:06 UTCEG score recompute
  65. 2026-07-27 17:06 UTCVendor advisory
  66. 2026-07-27 14:14 UTCEPSS rescore
  67. 2026-07-27 03:40 UTCEG score recompute
  68. 2026-07-27 03:40 UTCVendor advisory
  69. 2026-07-26 14:54 UTCEPSS rescore
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-26 14:34 UTCEG score recompute
  72. 2026-07-26 14:34 UTCVendor advisory
  73. 2026-07-25 14:18 UTCEPSS rescore
  74. 2026-07-25 14:18 UTCEPSS rescore
  75. 2026-07-24 14:18 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57231?
CVE-2026-57231 is a high vulnerability published on June 26, 2026. Podman is a tool for managing OCI containers and pods. From 1.8.1 until 5.8.4, a container image that contains a environment variable with just a key and no value can trick podman into passing that variable from the host into the container. This is made worse by the fact that using an asterisk (*)…
When was CVE-2026-57231 disclosed?
CVE-2026-57231 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57231 actively exploited?
CVE-2026-57231 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.0% of all scored CVEs.
What is the CVSS score of CVE-2026-57231?
CVE-2026-57231 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-57231?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57231, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57231

Explore →

Is Your Infrastructure Affected by CVE-2026-57231?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs