VulnerabilityPublished 9 Nov 2026

CVE-2026-77596: github.com/kubeflow/pipelines · Kubeflow Pipelines API server lacks authorization for shared pipeline uploads

Affects github.com/kubeflow/pipelinesSource GCVE Database

Compare

Authoritative record:CVE-2026-77596· Critical 9.6

Not known to be exploited · CVSS 9.6 Critical : upgrade to 0.0.0-20260909234119-62516d8c525f as a priority.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 3.1 base score

9.6Critical

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

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	9.6

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.0.0-20260909234119-62516d8c525f

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: High
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 9 Nov 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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 github.com/kubeflow/pipelines to 0.0.0-20260909234119-62516d8c525f.

Affected software

Product	Affected	Fixed in
Gogithub.com/kubeflow/pipelines	Affected <0.0.0-20260909234119-62516d8c525f	Fixed in 0.0.0-20260909234119-62516d8c525f

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

AI-suggested

A patch is available in Kubeflow Pipelines API server version 0.0.0-20260909234119-62516d8c525f that corrects the authorization logic to enforce SubjectAccessReview for empty namespaces on pipeline uploads. Users should upgrade to this fixed version to remediate the vulnerability. Alternatively, enabling the REQUIRE_NAMESPACE_FOR_PIPELINES configuration to true would reject empty namespace uploads, enforcing authorization. Until patched, restricting API server access and disabling multi-user mode may reduce exposure.

Description

A critical authorization bypass vulnerability exists in the Kubeflow Pipelines API server's HTTP multipart upload endpoints when operating in multi-user mode with the default configuration. The API server does not perform authorization checks for pipeline uploads targeting the empty namespace, which is used for shared, cluster-wide pipelines. This allows low-privilege or unauthenticated users to create or modify shared pipelines, potentially injecting malicious pipeline versions that other tenants execute. The vulnerability arises because the authorization helper skips SubjectAccessReview for empty namespaces, contrary to intended behavior confirmed by the gRPC sibling code. A fix is available in version 0.0.0-20260909234119-62516d8c525f.

Impact

An attacker with low privileges or no authentication can bypass authorization controls to create and modify shared cluster-wide pipelines in Kubeflow Pipelines. This enables injection of malicious pipeline versions that execute arbitrary container images and commands, potentially compromising the integrity and security of other tenants' workloads. The vulnerability affects multi-user mode installations with default configuration where namespace enforcement is disabled. The CVSS score is 9.6 (critical), reflecting network exploitable, low complexity, low privileges required, no user interaction, and high impact on confidentiality and integrity.

Summary

In multi-user mode, Kubeflow Pipelines API server endpoints POST /apis/v2beta1/pipelines/upload and /upload_version do not authorize requests when the target namespace is empty. The authorization function canUploadVersionedPipeline returns nil without performing SubjectAccessReview if the namespace is empty, which is the default when the namespace query parameter is omitted and REQUIRE_NAMESPACE_FOR_PIPELINES is false (the default). This allows an attacker with low privileges or no authentication to create or inject new versions into shared cluster-wide pipelines, replacing container images and commands executed by other tenants. The gRPC counterpart enforces authorization by mapping empty namespaces to the system namespace, indicating this omission is unintended. The vulnerability was demonstrated against the real API server binary with an unprivileged identity successfully creating shared pipelines. A patch fixing this issue is available in version 0.0.0-20260909234119-62516d8c525f.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
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)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (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 9 Nov 2026, 23:20 UTC

WeaknessesCWE-639, CWE-862

Technical details

References

Community reviews

Related threats