CVE-2024-36533 is a critical-severity (CVSS 9.8) CWE-1259 vulnerability in github.com/volcano-sh/volcano. A fix is available for github.com/volcano-sh/volcano — see the affected versions and patch details below.
Volcano has insecure permissions
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 CVE-2024-36533.
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
github.com/volcano-sh/volcano🐹volcano.sh/volcanoReal-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
Insecure permissions in volcano v1.8.2 allows attackers to access sensitive data and escalate privileges by obtaining the service account's token.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/volcano-sh/volcano | all versions | 1.10.0-alpha.0go get github.com/volcano-sh/volcano@v1.10.0-alpha.0 |
| 🐹Go | volcano.sh/volcano | all versions | 1.10.0-alpha.0go get volcano.sh/volcano@v1.10.0-alpha.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/volcano-sh/volcano, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/volcano-sh/volcano to 1.10.0-alpha.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-36533 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 CVE-2024-36533 in your dependencies?
Find it across Go, including transitive dependencies.