Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1

Kargo Vulnerable to SSRF in Promotion http/http-download Steps Enables Internal Network Access and Data Exfiltration

CVE-2026-32828GHSA-j94x-8wcp-x7hm

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/akuity/kargo 1.9.5, 1.8.12, 1.7.9, 1.6.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/akuity/kargo

    Affected
    >= 1.4.0, < 1.6.4>= 1.7.0-rc.1, < 1.7.9>= 1.8.0-rc.1, < 1.8.12>= 1.9.0-rc.1, < 1.9.5
    Fixed in
    1.6.4, 1.7.9, 1.8.12, 1.9.5

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N · score source
EPSS
  • CVE-2026-32828: 0.33% estimated exploitation activity in the next 30 days; percentile 26.76 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Kargo's built-in http and http-download promotion steps execute outbound HTTP requests from the Kargo controller. By design, these steps do not restrict destination addresses, as there are legitimate use cases for requests to internal and private endpoints. However, this also permits requests to link-local addresses, for which there are no known, legitimate use cases. Of particular concern is the cloud instance metadata endpoint (often 169.254.169.254), which is unauthenticated and can expose sensitive configuration data including IAM credentials. While cloud providers typically implement header-based SSRF mitigations for these endpoints, the http step provides full control over request method and headers, rendering these protections ineffective. The http-download step provides control over headers only (not method), but this is still sufficient for exfiltrating data from metadata endpoints. There are two vectors for exploitation. A user with permission to create or update a…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-j94x-8wcp-x7hm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32828

Advisory: Kargo Vulnerable to SSRF in Promotion http/http-download Steps Enables Internal Network Access and Data Exfiltration
IDs: CVE-2026-32828, GHSA-j94x-8wcp-x7hm
Record: https://patchnext.com/advisories/cve-2026-32828 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/akuity/kargo 1.9.5, 1.8.12, 1.7.9, 1.6.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/akuity/kargo: affected >= 1.4.0, < 1.6.4; >= 1.7.0-rc.1, < 1.7.9; >= 1.8.0-rc.1, < 1.8.12; >= 1.9.0-rc.1, < 1.9.5; fixed in 1.6.4, 1.7.9, 1.8.12, 1.9.5

## Suggested inspection (read-only)
- Go github.com/akuity/kargo: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/akuity/kargo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j94x-8wcp-x7hm (GitHub-reviewed advisory GHSA-j94x-8wcp-x7hm lists affected ranges: Go github.com/akuity/kargo >=1.4.0 =1.7.0-rc.1 =1.8.0-rc.1 =1.9.0-rc.1 <1.9.5)

Commands are suggestions: review each one before running it.

Loading voting…