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 83% 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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)
EPSS
17.4%
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(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 45× 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.

  1. 2026-07-07 00:49 UTCEG score recompute
  2. 2026-07-07 00:49 UTCVendor advisory
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:50 UTCEG score recompute
  6. 2026-07-06 11:50 UTCVendor advisory
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 22:48 UTCEG score recompute
  10. 2026-07-05 22:48 UTCVendor advisory
  11. 2026-07-05 09:49 UTCEG score recompute
  12. 2026-07-05 09:49 UTCVendor advisory
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 20:45 UTCEG score recompute
  16. 2026-07-04 20:45 UTCVendor advisory
  17. 2026-07-04 07:46 UTCEG score recompute
  18. 2026-07-04 07:46 UTCVendor advisory
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-03 18:38 UTCEG score recompute
  22. 2026-07-03 18:38 UTCVendor advisory
  23. 2026-07-03 05:39 UTCEG score recompute
  24. 2026-07-03 05:39 UTCVendor advisory
  25. 2026-07-02 16:40 UTCEG score recompute
Show 20 more
  1. 2026-07-02 16:40 UTCVendor advisory
  2. 2026-07-02 03:40 UTCEG score recompute
  3. 2026-07-02 03:40 UTCVendor advisory
  4. 2026-07-01 15:07 UTCEPSS rescore
  5. 2026-07-01 14:41 UTCEG score recompute
  6. 2026-07-01 01:42 UTCEG score recompute
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 12:43 UTCEG score recompute
  9. 2026-06-29 23:38 UTCEG score recompute
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 10:39 UTCEG score recompute
  12. 2026-06-28 21:39 UTCEG score recompute
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 08:39 UTCEG score recompute
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 19:41 UTCEG score recompute
  18. 2026-06-27 06:41 UTCEG score recompute
  19. 2026-06-26 17:41 UTCEG score recompute
  20. 2026-06-26 17:41 UTCNVD updatefirst tracked

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 17.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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