CVE-2021-20259 is a high-severity (CVSS 7.8) Information Exposure vulnerability in foreman_fog_proxmox. A fix is available for foreman_fog_proxmox — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor in foreman_fog_proxmox
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-20259 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
foreman_fog_proxmoxReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.
Description
A flaw was found in the Foreman project. The Proxmox compute resource exposes the password through the API to an authenticated local attacker with view_hosts permission. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. Versions of foreman_fog_proxmox prior to 0.13.1 are affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 💎RubyGems | foreman_fog_proxmox | all versions | 0.13.1bundle update foreman_fog_proxmox --conservative |
Affected Products
foremanfogproxmoxtheforemanDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for foreman_fog_proxmox, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update foreman_fog_proxmox to 0.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-20259 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2021-20259 in your dependencies?
Find it across RubyGems, including transitive dependencies.