CVE-2026-24748: Kargo's `GetConfig()` and `RefreshResource()` API endpoints allow unauthenticated access
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/akuity/kargo (Go) 1.7.7, 1.8.7, 1.6.3.
Low priority for now. Upgrade to github.com/akuity/kargo (Go) 1.7.7, 1.8.7, 1.6.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Kargo manages and automates the promotion of software artifacts. Prior to versions 1.8.7, 1.7.7, and 1.6.3, a bug was found with authentication checks on the `GetConfig()` API endpoint. This allowed unauthenticated users to access this endpoint by specifying an `Authorization` header with any non-empty `Bearer` token value, regardless of validity. This vulnerability did allow for exfiltration of configuration data such as endpoints for connected Argo CD clusters. This data could allow an attacker to enumerate cluster URLs and namespaces for use in subsequent attacks. Additionally, the same bug affected the `RefreshResource` endpoint. This endpoint does not lead to any information disclosure, but could be used by an unauthenticated attacker to perform a denial-of-service style attack against the Kargo API. `RefreshResource` sets an annotation on specific Kubernetes resources to trigger reconciliations. If run on a constant loop, this could also slow down legitimate requests to the Kubernetes API server. This problem has been patched in Kargo versiosn 1.8.7, 1.7.7, and 1.6.3. There are no workarounds for this issue.
- Published
- Jan 27, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 33th percentile
- CWE
- CWE-863
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| akuity | kargo | cpe:2.3:a:akuity:kargo |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- akuity kargobefore 1.6.3
- akuity kargo1.7.0 and later · before 1.7.7
- akuity kargo1.8.0 and later · before 1.8.7
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
akuity kargo
- < 1.6.3, >= 1.7.0, < 1.7.7, <= 1.8.0, < 1.8.7affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/akuity/kargo | from 1.7.0-rc.1 · before 1.7.7 | 1.7.7 |
| Go | github.com/akuity/kargo | from 1.8.0-rc.1 · before 1.8.7 | 1.8.7 |
| Go | github.com/akuity/kargo | before 1.6.3 | 1.6.3 |
Same product
akuity: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-61850Kargo: Privilege escalation via Project RBAC management in the Kargo API37Monitor
- CVE-2026-27112Kargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints37Monitor
- CVE-2026-27111Kargo has Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints21Monitor
Published before and after this one in the same product
- Later →CVE-2026-32828Mar 19, 2026 · Kargo: SSRF in Promotion http/http-download Steps Enables Internal Network Access and Data Exfiltration20Monitor
- Later →CVE-2026-42350May 8, 2026 · Kargo: Open Redirect in UI OIDC Login Flow via redirectTo Query Parameter20Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/akuity/kargo | 1.6.3 | Package registry (OSV) |
| Go:github.com/akuity/kargo | 1.7.7 | Package registry (OSV) |
| Go:github.com/akuity/kargo | 1.8.7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-2711224 days apartKargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints37Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-2711224 days apartKargo has an Authorization Bypass Vulnerability in Batch Resource Creation API Endpoints37Monitor
- CVE-2026-3282851 days apartKargo: SSRF in Promotion http/http-download Steps Enables Internal Network Access and Data Exfiltration20Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.