CVE-2026-32828 Kargo: SSRF in Promotion http/http-download Steps Enables Internal Network Access and Data Exfiltration
Authenticated attackers can exploit SSRF in Kargo promotion steps to access internal networks and exfiltrate sensitive cloud metadata credentials.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-32828?
CVE-2026-32828 is a medium-severity server-side request forgery vulnerability in akuity kargo, published on 20 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official 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.
Weakness: CWE-918
Which versions are affected by CVE-2026-32828?
9 open source packages ship an affected version, including github.com/akuity/kargo. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/akuity/kargo Go | From 1.4.0 | 1.6.4, 1.7.9, 1.8.12, 1.9.5 |
github.com/akuity/kargo Go | From 1.4.0 | 1.6.4 |
github.com/akuity/kargo Go | From 1.4.0 | 1.6.4 |
github.com/akuity/kargo Go | From 1.7.0-rc.1 | 1.7.9 |
github.com/akuity/kargo Go | From 1.7.0-rc.1 | 1.7.9 |
github.com/akuity/kargo Go | From 1.8.0-rc.1 | 1.8.12 |
3 more packages
github.com/akuity/kargo Go | From 1.8.0-rc.1 | 1.8.12 |
github.com/akuity/kargo Go | From 1.9.0-rc.1 | 1.9.5 |
github.com/akuity/kargo Go | From 1.9.0-rc.1 | 1.9.5 |
Products include Akuity Kargo.
How do I fix CVE-2026-32828?
Upgrade github.com/akuity/kargo to a fixed version for your release line: 1.6.4, 1.7.9, 1.8.12 or 1.9.5.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-32828 being exploited?
There is no known exploitation of CVE-2026-32828 in the wild and no public exploit code.
Other vulnerabilities in akuity kargo
- CVE-2026-27112 Kargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints
- CVE-2026-24748 Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access
- CVE-2026-27111 Kargo has Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints
Sources
Also known as GHSA-j94x-8wcp-x7hm, GO-2026-4717.