CVE-2026-118761 kubeflow CVE debrief

Who should care

Kubeflow Pipelines administrators and users, as well as security teams responsible for monitoring and protecting API-server resources. These stakeholders should assess exposure, prioritize upgrading to Kubeflow Pipelines 2.18.0, and monitor API-server resources and service availability. They should also review and adjust deployment resource limits and concurrent activity to prevent resource exhaustion and service interruption. Additionally, they should be

Why it matters

The vulnerability in Kubeflow Pipelines API server allows for decompression bomb attacks, potentially leading to resource exhaustion and service interruption. Administrators and users should assess exposure, prioritize upgrading to Kubeflow Pipelines 2.18.0, and monitor API-server resources and service availability.

• Potential exhaustion of API-server resources
• Interruption of service due to decompression bomb attacks
• Need for verification of affected versions and deployment resource limits
• Priority for upgrading to Kubeflow Pipelines 2.18.0

Technical summary

The Kubeflow Pipelines API server decompresses uploaded pipeline archives without adequately bounding expanded data, potentially leading to resource exhaustion and service interruption. This vulnerability can be triggered by a small ZIP or gzip-compressed tar archive that consumes disproportionately large amounts of memory. The API server's decompression of uploaded pipeline archives without adequate bounding of expanded data can cause resource exhaustion and service interruption. External authentication and network controls can restrict reachability.

Defensive priority

Upgrade to Kubeflow Pipelines 2.18.0 to prevent decompression bomb attacks

Recommended defensive actions

• Upgrade the API server to Kubeflow Pipelines 2.18.0
• Review and adjust deployment resource limits and concurrent activity
• Monitor API-server resources and service availability
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The source corpus provides details on the vulnerability, its impact, and the remediation. However, the exact versions affected are not clearly stated, and the first affected release has not been established.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.