CVE-2022-36035 — flux2
HIGHCVE-2022-36035 is a high-severity (CVSS 7.7) Path Traversal vulnerability in github.com/fluxcd/flux2. A fix is available for github.com/fluxcd/flux2 — see the affected versions and patch details below.
Flux CLI Workload Injection
Exploitation Status
No confirmed exploitation observed yet
- 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-2022-36035.
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/fluxcd/flux2Real-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
Flux CLI allows users to deploy Flux components into a Kubernetes cluster via command-line. The vulnerability allows other applications to replace the Flux deployment information with arbitrary content which is deployed into the target Kubernetes cluster instead.
The vulnerability is due to the improper handling of user-supplied input, which results in a path traversal that can be controlled by the attacker.
Impact
Users sharing the same shell between other applications and the Flux CLI commands could be affected by this vulnerability.
In some scenarios no errors may be presented, which may cause end users not to realise that something is amiss.
Workarounds
A safe workaround is to execute Flux CLI in ephemeral and isolated shell environments, which can ensure no persistent values exist from previous processes. However, upgrading to the latest version of the CLI is still the recommended mitigation strategy.
Credits
The Flux engineering team found and patched this vulnerability.
For more information
If you have any questions or comments about this advisory:
- Open an issue in any of the affected repositories.
- Contact us at the CNCF Flux Channel.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/fluxcd/flux2 | ≥ 0.21.0&&< 0.32.0 | 0.32.0go get github.com/fluxcd/flux2@v0.32.0 |
Affected Products
flux2fluxcdDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/fluxcd/flux2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/fluxcd/flux2 to 0.32.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36035 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2022-36035 in your dependencies?
Find it across Go, including transitive dependencies.