GHSA-66vw-v2x9-hw75
HIGHGHSA-66vw-v2x9-hw75 is a high-severity (CVSS 8.8) CWE-281 vulnerability in github.com/containers/podman/v3. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-66vw-v2x9-hw75 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Podman publishes a malicious image to public registries
Blast Radius
github.com/containers/podman/v3🐹github.com/containers/psgoReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Podman is a tool for managing OCI containers and pods. A privilege escalation flaw was found in Podman. This flaw allows an attacker to publish a malicious image to a public registry. Once this image is downloaded by a potential victim, the vulnerability is triggered after a user runs the 'podman top' command. This action gives the attacker access to the host filesystem, leading to information disclosure or denial of service.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/containers/podman/v3 | all versions | 3.4 |
| 🐹Go | github.com/containers/psgo | all versions | 1.7.2 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/containers/podman/v3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/containers/podman/v3 to 3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-66vw-v2x9-hw75 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-66vw-v2x9-hw75 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-66vw-v2x9-hw75. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-66vw-v2x9-hw75 in your dependencies?
O3 detects GHSA-66vw-v2x9-hw75 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.