CVE-2026-32828 — kargo
Fix: akuity/kargo@fd25620CVE-2026-32828 is a Server-Side Request Forgery (SSRF) vulnerability in github.com/akuity/kargo. A fix is available for github.com/akuity/kargo — see the affected versions and patch details below.
Kargo: SSRF in Promotion http/http-download Steps Enables Internal Network Access and Data Exfiltration
Exploitation Status
No confirmed exploitation observed yet
- 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-2026-32828.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
github.com/akuity/kargo🐹github.com/akuity/kargo🐹github.com/akuity/kargo🐹github.com/akuity/kargoReal-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
Kargo manages and automates the promotion of software artifacts. In versions 1.4.0 through 1.6.3, 1.7.0-rc.1 through 1.7.8, 1.8.0-rc.1 through 1.8.11, and 1.9.0-rc.1 through 1.9.4, the http and http-download promotion steps allow Server-Side Request Forgery (SSRF) against link-local addresses, most critically the cloud instance metadata endpoint (169.254.169.254), enabling exfiltration of sensitive data such as IAM credentials. These steps provide full control over request headers and methods, rendering cloud provider header-based SSRF mitigations ineffective. An authenticated attacker with permissions to create/update Stages or craft Promotion resources can exploit this by submitting a malicious Promotion manifest, with response data retrievable via Promotion status fields, Git repositories, or a second http step. This issue has been fixed in versions 1.6.4, 1.7.9, 1.8.12 and 1.9.5.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/akuity/kargo | ≥ 1.4.0&&< 1.6.4 | 1.6.4go get github.com/akuity/kargo@v1.6.4 |
| 🐹Go | github.com/akuity/kargo | ≥ 1.7.0-rc.1&&< 1.7.9 | 1.7.9go get github.com/akuity/kargo@v1.7.9 |
| 🐹Go | github.com/akuity/kargo | ≥ 1.8.0-rc.1&&< 1.8.12 | 1.8.12go get github.com/akuity/kargo@v1.8.12 |
| 🐹Go | github.com/akuity/kargo | ≥ 1.9.0-rc.1&&< 1.9.5 | 1.9.5go get github.com/akuity/kargo@v1.9.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/akuity/kargo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/akuity/kargo to 1.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32828 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-32828 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-32828. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-32828 in your dependencies?
O3 Security finds CVE-2026-32828 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.