CVE-2026-24748VulnerabilityPublished 27 Jan 2026

CVE-2026-24748: akuity kargo · Incorrect Authorization

Affects akuity kargoSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium · fixed in 1.8.7 : update akuity kargo when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.8.7, 1.7.7, 1.6.3

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Subsequent System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Subsequent System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade kargo to 1.8.7, 1.7.7 or 1.6.3; akuity/kargo to 1.6.3.

Affected software

Product	Affected	Fixed in
akuitykargo	Affected <1.6.3 >=1.7.0 <1.7.7 <=1.8.0 <1.8.7	Fixed in 1.8.7 1.7.7 1.6.3
GitHubakuity/kargo`pkg:github/akuity/kargo`Other threats	Affected <1.6.3	Fixed in 1.6.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify their Kargo deployment versions and upgrade to at least 1.6.3, 1.7.7, or 1.8.7 as applicable. Since no workarounds exist, patching is critical. Additionally, organizations should restrict network access to Kargo API endpoints using firewall rules or network segmentation to limit exposure to trusted internal hosts. Implementing strict ingress controls and monitoring API usage patterns can help detect anomalous access attempts. Kubernetes clusters connected to Kargo should have robust role-based access controls (RBAC) and audit logging enabled to identify suspicious reconciliation triggers. Organizations should also review and rotate any credentials or tokens that may have been exposed due to this vulnerability. Finally, integrating vulnerability scanning and continuous monitoring for Kargo and related GitOps tools will help prevent future exploitation.

Description

CVE-2026-24748 is an incorrect authorization vulnerability in akuity's Kargo software versions prior to 1.8.7, 1.7.7, and 1.6.3. It allows unauthenticated attackers to access the GetConfig() API endpoint by providing any non-empty Bearer token, leading to exposure of configuration data such as Argo CD cluster endpoints. This information can be leveraged to enumerate cluster URLs and namespaces for further attacks. Additionally, the RefreshResource endpoint is vulnerable to unauthenticated denial-of-service attacks by triggering excessive Kubernetes resource reconciliations, potentially degrading API server performance.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and availability of Kubernetes cluster management infrastructure. Exposure of Argo CD cluster endpoints and namespaces can lead to targeted attacks such as unauthorized access, lateral movement, or supply chain compromise within Kubernetes environments. The denial-of-service potential on the RefreshResource endpoint can degrade cluster performance, impacting critical software deployment pipelines and automation workflows. Organizations relying on Kargo for artifact promotion and cluster management may experience operational disruptions and increased attack surface. Given the widespread adoption of Kubernetes and GitOps tools like Argo CD in Europe’s technology sectors, including finance, manufacturing, and government, exploitation could have cascading effects on service availability and data integrity. The lack of authentication requirements and ease of exploitation increase the likelihood of opportunistic attacks, especially in environments exposed to the internet or insufficiently segmented networks.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 09:14 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats