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
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.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100

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%
EPSS PROB
0.4%
EPSS %ILE
35th
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(14)

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
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

(9 across 3 ecosystems)
Go(7)
PackageVulnerable rangeFix by version rangeDependents
github.com/containers/libpod—
  • 1.8.1 on: no fix on record
—
github.com/containers/podman—
  • 1.8.1 on: no fix on record
  • every version on: no fix on record
—
github.com/containers/podman/v2—
  • every version through 2.2.1: no fix on record
  • every version on: no fix on record
—
github.com/containers/podman/v3—
  • every version through 3.4.7: no fix on record
  • every version on: no fix on record
—
github.com/containers/podman/v4—
  • every version through 4.9.5: no fix on record
  • every version on: no fix on record
—
github.com/containers/podman/v5—
  • every version up to 5.8.4: fixed in 5.8.4
—
go.podman.io/podman/v6—
  • every version up to 6.0.0: fixed in 6.0.0
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
podman5.4.2+ds1-2 ... 6.1.1+ds1-1 (26 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
podman5.4.2+ds1-2 ... 5.8.3+ds1-1 (21 versions)
  • every version up to 5.8.4+ds1-1: fixed in 5.8.4+ds1-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 227 total refreshes for this CVE.

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

Related CVEs(same product + 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 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.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57231?
CVE-2026-57231 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57231?
A fix for CVE-2026-57231 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57231 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs