CVE-2026-33414

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% 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, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

Podman is a tool for managing OCI containers and pods. Versions 4.8.0 through 5.8.1 contain a command injection vulnerability in the HyperV machine backend in pkg/machine/hyperv/stubber.go, where the VM image path is inserted into a PowerShell double-quoted string without sanitization, allowing $() subexpression injection. Because PowerShell evaluates subexpressions inside double-quoted strings before executing the outer command, an attacker who can control the VM image path through a crafted machine name or image directory can execute arbitrary PowerShell commands with the privileges of the Podman process. On typical Windows installations this means SYSTEM-level code execution, and only Windows is affected as the code is exclusive to the HyperV backend. This issue has been patched in version 5.8.2.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
50(Track)
EG Risk 50/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
Severity78% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

April 14, 2026

Last Modified

July 24, 2026

Advisory Details (2)

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

PowerShell Command Injection in Podman HyperV Machine · Advisory · podman-container-tools/podman · GitHub

https://github.com/containers/podman/security/advisories/GHSA-hc8w-h2mf-hp59
github_commit

commit 571c842bd357 (containers/podman)

Fix landed in containers/podman commit 571c842bd357 — awaiting tagged release

https://github.com/containers/podman/commit/571c842bd357ee626019ea97d030fb772fc654ed

Vendor Advisories for CVE-2026-33414(1)

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-5.8.2-1.hum12026-04-14redhat

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

(7 across 3 ecosystems)
Go(5)
PackageVulnerable rangeFixed inDependents
github.com/containers/podman———
github.com/containers/podman/v2———
github.com/containers/podman/v3———
github.com/containers/podman/v4———
github.com/containers/podman/v5—5.8.2—
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.1+ds1-3 (17 versions)5.8.2+ds1-1—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33414?
CVE-2026-33414 is a high vulnerability published on April 14, 2026. Podman is a tool for managing OCI containers and pods. Versions 4.8.0 through 5.8.1 contain a command injection vulnerability in the HyperV machine backend in pkg/machine/hyperv/stubber.go, where the VM image path is inserted into a PowerShell double-quoted string without sanitization, allowing $()…
When was CVE-2026-33414 disclosed?
CVE-2026-33414 was first published in the National Vulnerability Database on April 14, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33414 actively exploited?
CVE-2026-33414 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.3% of all scored CVEs.
What is the CVSS score of CVE-2026-33414?
CVE-2026-33414 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-33414?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33414, 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-33414

Explore →

Is Your Infrastructure Affected by CVE-2026-33414?

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

Start Free Scan →Browse All CVEs