Gentoo Portage missing PGP validation of executed codeGHSA-pw5x-x5jw-ccmh
CRITICALFix: gentoo/portage@28cd240GHSA-pw5x-x5jw-ccmh is a critical-severity (CVSS 9.8) CWE-347 vulnerability in portage. A fix is available for portage — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-pw5x-x5jw-ccmh.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
portageReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
In Gentoo Portage before 3.0.47, there is missing PGP validation of executed code: the standalone emerge-webrsync downloads a .gpgsig file but does not perform signature verification. Unless emerge-webrsync is used, Portage is not vulnerable.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | portage | all versions | 3.0.47pip install --upgrade 'portage==3.0.47' |
Affected Products
portagegentooDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for portage, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update portage to 3.0.47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pw5x-x5jw-ccmh 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.
Frequently Asked Questions
Is GHSA-pw5x-x5jw-ccmh in your dependencies?
Find it across PyPI, including transitive dependencies.