VulnerabilityPublished 30 Oct 2026

CVE-2026-118761: Kubeflow Pipelines · Pipeline archive upload allows decompression bomb to exhaust server memory

Affects github.com/kubeflow/pipelinesSource GCVE Database

Compare

Authoritative record:CVE-2026-118761· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.0.0-20260831164314-ba9ae72cc860 soon.

Data as of 31 Oct 2026, 01:54 UTC

CVSS 3.1 base score

7.5High

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	7.5

Patch: Available – fixed in 0.0.0-20260831164314-ba9ae72cc860

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

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

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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 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 30 Oct 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-20260831164314-ba9ae72cc860.

Affected software

Product	Affected	Fixed in
Gogithub.com/kubeflow/pipelines	Affected <0.0.0-20260831164314-ba9ae72cc860	Fixed in 0.0.0-20260831164314-ba9ae72cc860
Gogithub.com/kubeflow/pipelines	Affected =1.7.0-alpha.3	Fixed in–

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

AI-suggested

Upgrade the Kubeflow Pipelines API server to version 2.18.0 or later, which includes fixes bounding decompression resource usage. Until upgrade, restrict network access to pipeline upload and import endpoints and apply deployment-level request and resource limits. Note that limiting compressed upload size alone is insufficient to prevent decompression amplification attacks. Review and configure the new upload and specification limits introduced in 2.18.0 to further mitigate risk.

Description

Kubeflow Pipelines API server versions through 2.17.3 decompress uploaded pipeline archives without sufficient limits on expanded data size. This allows a crafted compressed archive (ZIP or gzip tar) to consume excessive memory during decompression, potentially exhausting server resources and causing service interruption. The vulnerability can be triggered by unauthenticated callers who can reach the upload endpoints, as decompression occurs before authorization. The issue is fixed in version 2.18.0, which introduces bounds on compressed input and extracted data sizes.

Impact

An attacker able to upload pipeline archives to the Kubeflow Pipelines API server can cause excessive memory consumption by submitting specially crafted compressed archives. This can lead to exhaustion of server memory resources, resulting in denial of service (service interruption). The vulnerability does not impact confidentiality or integrity but affects availability. The severity is high with a CVSS 3.1 score of 7.5 (Network attack vector, low complexity, no privileges or user interaction required, impacts availability).

Summary

The Kubeflow Pipelines API server improperly bounds the decompression of uploaded pipeline archives, allowing a decompression bomb attack that can exhaust server memory and disrupt service. The decompression occurs before namespace authorization, enabling unauthenticated attackers with network access to upload endpoints to trigger the issue. The fix in 2.18.0 adds limits on compressed input size, extracted pipeline data, and tar traversal budgets to mitigate decompression amplification. Operators are advised to restrict access and apply resource controls until upgrading.

CWE-409Improper Handling of Highly Compressed Data (Data Amplification) (opens in a new tab)
Base weakness
The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.2 (opens in a new tab)
V12.1.1 (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 31 Oct 2026, 01:54 UTC

WeaknessesCWE-409

Technical details

References

Community reviews

Related threats