What is the CVSS score of CVE-2026-24748?

CVE-2026-24748 has a CVSS 3.1 base score of 7.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L. EPSS exploitation probability: 0.1%.

How to fix or mitigate CVE-2026-24748?

Within 24 hours: Identify all Kargo deployments and confirm installed versions against the affected baseline (pre-1.8.7, pre-1.7.7, pre-1.6.3). Within 7 days: Apply available patches to all affected instances or implement compensating controls listed below if patching is blocked. Within 30 days: Complete remediation across all environments and validate patch deployment through security testing.

Kargo CVE-2026-24748

HIGH

Incorrect Authorization (CWE-863)

2026-01-27 security-advisories@github.com

GHSA-w5wv-wvrp-v5m5

Information Disclosure Kubernetes Golang Kargo Suse Akuity

7.2

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Send HTTP request to GetConfig() endpoint
Exploit

Include Authorization header with arbitrary Bearer token
Execution

Bypass authentication checks
Impact

Retrieve sensitive configuration data

Vulnerability Assessment

Weakness	CWE CWE-863 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V8 - Authorization Authorization logic validation MITRE ATT&CK 1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Exploitation Conditions	Kargo versions before 1.8.7, 1.7.7, or 1.6.3 with GetConfig() API endpoint exposed. Attacker must craft HTTP request with any non-empty Bearer token in Authorization header. No valid credentials required. Remote unauthenticated access to unpatched Kargo instances.
Impact	CVSS 7.2 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: None. User interaction: None. Exploitation no authentication required.
Exploit ScenarioDerived	An attacker without authentication could exploit this vulnerability to enumerate cluster URLs and namespaces for use in subsequent attacks.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Kargo's GetConfig() API endpoint fails to validate Bearer token authenticity, allowing unauthenticated attackers to retrieve sensitive configuration data including Argo CD cluster endpoints and namespaces that could facilitate further attacks. The same authentication bypass affects the RefreshResource endpoint, which can be leveraged for denial-of-service attacks. Versions 1.6.3, 1.7.7, and 1.8.7 and later include patches for this vulnerability.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:55 CVSS 7.2

RemediationAI

A vendor patch is available — apply it immediately. Restrict network access to the affected service where possible.

Affected Packages

go github.com/akuity/kargo fix: 1.6.3, 1.7.7, 1.8.7

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in go

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-863 (Incorrect Authorization). Affects Kargo. 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 attack

Know when Kargo gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.2 HIGH

AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L

SUSE 6.9 MEDIUM

Primary rating from GitHub Advisory.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

None

Availability

Low

Lifecycle Timeline

Patch released

Feb 25, 2026 - 17:59 nvd

Patch available

CVE Published

Jan 27, 2026 - 22:15 nvd

HIGH 7.2

DescriptionGitHub Advisory

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.

Executive ViewAI

Why It Matters

Kargo artifact management systems running versions prior to 1.8.7, 1.7.7, or 1.6.3 contain an authentication bypass vulnerability in the GetConfig() API endpoint, potentially allowing unauthorized access to sensitive deployment configurations. Organizations using affected versions should prioritize patching to prevent credential exposure and unauthorized software promotion activities.

Business Impact: High

Compensating Controls

Apply vendor patch. If patching cannot be completed immediately: (1) Implement network access controls restricting GetConfig() API calls to authenticated internal systems only; (2) Deploy WAF rules to require valid authentication tokens on all GetConfig() requests; (3) Enable API logging and monitoring to detect unauthorized access attempts; (4) Restrict Kargo service account permissions to minimum necessary scope; (5) Isolate affected Kargo instances from production promotion pipelines until patched.

Threat Intelligence Overview

EPSS Score

0.1%

Top 67% exploitable

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS Vendor

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.1%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Open

Automatable· derived

Yes

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +36

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.