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.0%, top 97% 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
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.8Exploit: NoneExposed: 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)
EPSS
45.0%
KEV
Not listed

Published

April 14, 2026

Last Modified

July 15, 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

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/containers/podman/v4———
github.com/containers/podman/v5—5.8.2—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× 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.

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

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