CVE-2026-27112: Kargo manages and automates the promotion of software artifacts

This month

CRITICAL 9.9UPGRADE

CVE-2026-27112 is a critical-severity flaw (CVSS 9.9) affecting kargo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Kargo manages and automates the promotion of software artifacts. From 1.7.0 to before v1.7.8, v1.8.11, and v1.9.3, the batch resource creation endpoints of both Kargo's legacy gRPC API and newer REST API accept multi-document YAML payloads. Specially crafted payloads can manifest a bug present in the logic of both endpoints to inject arbitrary resources (of specific types only) into the underlying namespace of an existing Project using the API se

Why this priority

Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score	9.9 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 58%)
CISA exploited list	No
Weakness	CWE-863
Published	2026-02-20
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: akuity

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-02-20 22:16 UTCPublished CVE record published
2026-06-17 10:26 UTCUpdated Record last modified

akuity kargo UPGRADE

Affected: >= 1.7.0 and < 1.7.8 · >= 1.8.0 and < 1.8.11 · >= 1.9.0 and < 1.9.3

Fixed in: 1.7.8, 1.8.11, 1.9.3

Safe to downgrade to: a release before 1.7.0

1. Check installed version

apt-cache policy kargo || rpm -q kargo || kargo --version

2. UPGRADE to 1.7.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade kargo

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade kargo

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.7.0 (Debian / Ubuntu)

apt-cache madison kargo sudo apt install kargo=<VERSION_BEFORE_1.7.0> sudo apt-mark hold kargo

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list kargo sudo dnf downgrade kargo-<VERSION_BEFORE_1.7.0> sudo dnf versionlock add kargo

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-27112?

kargo: upgrade to 1.7.8, 1.8.11, 1.9.3. Exact commands for each OS are on this page.

Is CVE-2026-27112 being exploited?

CVE-2026-27112 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-27112 affect?

CVE-2026-27112 affects kargo. Severity is critical (CVSS 9.9). Kargo manages and automates the promotion of software artifacts. From 1.7.0 to before v1.7.8, v1.8.11, and v1.9.3, the batch resource creation endpoints of both Kargo's legacy gRPC API and newer REST API accept multi-document YAML payloads.

How urgent is CVE-2026-27112?

Priority 45/100. Critical severity

Related CVEs

CVE-2026-32828 MEDIUM 4.9 UPGRADE Kargo manages and automates the promotion of software artifacts
CVE-2026-27111 MEDIUM 5.0 UPGRADE Kargo manages and automates the promotion of software artifacts
CVE-2026-24748 HIGH 7.2 UPGRADE Kargo manages and automates the promotion of software artifacts

References

← Back to latest CVEs