CVE-2026-32828: CWE-918: Server-Side Request Forgery (SSRF) in akuity kargo
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.
AI Analysis
Technical Summary
CVE-2026-32828 is a Server-Side Request Forgery (SSRF) vulnerability affecting multiple versions of akuity kargo, a tool used to manage and automate software artifact promotion. The vulnerability resides in the http and http-download promotion steps, which allow an attacker to craft requests that the server executes internally. Specifically, the flaw permits SSRF attacks targeting link-local IP addresses, including the cloud instance metadata service at 169.254.169.254. This metadata endpoint typically contains sensitive information such as IAM credentials and other cloud instance details. The vulnerability is exacerbated by the attacker's ability to fully control HTTP request headers and methods, rendering common cloud provider SSRF mitigations ineffective. Exploitation requires authentication with permissions to create or update Stages or Promotion resources, which means the attacker must have some level of authorized access. The attacker can submit a malicious Promotion manifest that triggers the SSRF and retrieve the response data through Promotion status fields, Git repositories, or subsequent http steps. This data exfiltration can lead to credential compromise and further cloud environment infiltration. The vulnerability affects 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 of akuity kargo. Fixed versions include 1.6.4, 1.7.9, 1.8.12, and 1.9.5. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no user interaction, and requires high privileges, resulting in a medium severity rating. No public exploits have been reported to date.
Potential Impact
The primary impact of this SSRF vulnerability is the unauthorized access and exfiltration of sensitive cloud instance metadata, including IAM credentials. Compromise of these credentials can lead to privilege escalation, lateral movement, and full cloud environment takeover. Organizations using vulnerable versions of akuity kargo risk exposure of their cloud infrastructure secrets, potentially resulting in data breaches, service disruptions, and financial loss. Since the attacker must have authenticated access with permissions to create or update promotion resources, insider threats or compromised accounts pose significant risk. The ability to bypass cloud provider SSRF mitigations increases the attack's effectiveness. This vulnerability can undermine trust in the software supply chain automation process, as attackers could manipulate artifact promotion to further compromise systems. Overall, the impact extends beyond the immediate SSRF to broader cloud security and operational integrity.
Mitigation Recommendations
1. Upgrade akuity kargo to the fixed versions: 1.6.4, 1.7.9, 1.8.12, or 1.9.5 immediately to eliminate the vulnerability. 2. Restrict permissions to create or update Stages or Promotion resources strictly to trusted and necessary personnel to reduce the attack surface. 3. Implement network segmentation and firewall rules to block internal access from the kargo server to sensitive link-local IP addresses such as 169.254.169.254, where feasible. 4. Monitor and audit promotion manifests and status fields for unusual or unexpected HTTP requests or responses that could indicate exploitation attempts. 5. Employ strong authentication and session management to prevent account compromise of users with promotion resource privileges. 6. Consider implementing additional application-layer SSRF protections such as request validation, allowlisting of external URLs, and limiting HTTP methods and headers allowed in promotion steps. 7. Conduct regular security reviews and penetration tests focusing on internal request handling and metadata service protections. 8. Educate developers and operators about the risks of SSRF and the importance of least privilege in artifact promotion workflows.
Affected Countries
United States, Germany, United Kingdom, Canada, Australia, Netherlands, France, Japan, South Korea, India
CVE-2026-32828: CWE-918: Server-Side Request Forgery (SSRF) in akuity kargo
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-32828 is a Server-Side Request Forgery (SSRF) vulnerability affecting multiple versions of akuity kargo, a tool used to manage and automate software artifact promotion. The vulnerability resides in the http and http-download promotion steps, which allow an attacker to craft requests that the server executes internally. Specifically, the flaw permits SSRF attacks targeting link-local IP addresses, including the cloud instance metadata service at 169.254.169.254. This metadata endpoint typically contains sensitive information such as IAM credentials and other cloud instance details. The vulnerability is exacerbated by the attacker's ability to fully control HTTP request headers and methods, rendering common cloud provider SSRF mitigations ineffective. Exploitation requires authentication with permissions to create or update Stages or Promotion resources, which means the attacker must have some level of authorized access. The attacker can submit a malicious Promotion manifest that triggers the SSRF and retrieve the response data through Promotion status fields, Git repositories, or subsequent http steps. This data exfiltration can lead to credential compromise and further cloud environment infiltration. The vulnerability affects 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 of akuity kargo. Fixed versions include 1.6.4, 1.7.9, 1.8.12, and 1.9.5. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no user interaction, and requires high privileges, resulting in a medium severity rating. No public exploits have been reported to date.
Potential Impact
The primary impact of this SSRF vulnerability is the unauthorized access and exfiltration of sensitive cloud instance metadata, including IAM credentials. Compromise of these credentials can lead to privilege escalation, lateral movement, and full cloud environment takeover. Organizations using vulnerable versions of akuity kargo risk exposure of their cloud infrastructure secrets, potentially resulting in data breaches, service disruptions, and financial loss. Since the attacker must have authenticated access with permissions to create or update promotion resources, insider threats or compromised accounts pose significant risk. The ability to bypass cloud provider SSRF mitigations increases the attack's effectiveness. This vulnerability can undermine trust in the software supply chain automation process, as attackers could manipulate artifact promotion to further compromise systems. Overall, the impact extends beyond the immediate SSRF to broader cloud security and operational integrity.
Mitigation Recommendations
1. Upgrade akuity kargo to the fixed versions: 1.6.4, 1.7.9, 1.8.12, or 1.9.5 immediately to eliminate the vulnerability. 2. Restrict permissions to create or update Stages or Promotion resources strictly to trusted and necessary personnel to reduce the attack surface. 3. Implement network segmentation and firewall rules to block internal access from the kargo server to sensitive link-local IP addresses such as 169.254.169.254, where feasible. 4. Monitor and audit promotion manifests and status fields for unusual or unexpected HTTP requests or responses that could indicate exploitation attempts. 5. Employ strong authentication and session management to prevent account compromise of users with promotion resource privileges. 6. Consider implementing additional application-layer SSRF protections such as request validation, allowlisting of external URLs, and limiting HTTP methods and headers allowed in promotion steps. 7. Conduct regular security reviews and penetration tests focusing on internal request handling and metadata service protections. 8. Educate developers and operators about the risks of SSRF and the importance of least privilege in artifact promotion workflows.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-16T17:35:36.698Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69bc9abfe32a4fbe5f1030fe
Added to database: 3/20/2026, 12:54:23 AM
Last enriched: 3/27/2026, 6:49:36 PM
Last updated: 5/4/2026, 12:18:30 AM
Views: 108
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.