GPU VulnDB

Database/Container, Kubernetes & orchestration

Apache Camel K: YAML injection in custom resources creates arbitrary Kubernetes objects as the operator

CVSS 9.8CVE-2026-80352Container, Kubernetes & orchestrationcurated

Impact

A user who can author a Camel K custom resource can inject arbitrary Kubernetes objects into the manifest the operator renders, and those objects are created with the operator's service account privileges. Camel K operators are typically granted broad create rights across their namespaces or cluster-wide, so this turns namespaced CR-author access into resource creation the author was never authorized for - including pods with host mounts or privileged security contexts on GPU nodes if the operator's role permits it. It is a namespace-boundary escape on any shared cluster where tenants can submit integrations.

Who can reach it

Any user authorized to create or edit Camel K custom resources in a namespace the operator watches. Authenticated Kubernetes API access is required; no cluster-admin.

What to do

Upgrade Camel K to 2.9.3, 2.10.2 or 2.11.0 (affected: 2.0.0 before 2.9.3, and 2.10.1 before 2.10.2) - this is an operator deployment rollout, no node disruption. Until then, restrict RBAC on Camel K CRs to trusted principals and tighten the operator's own service account to the minimum resource types it needs.

References

Related entries

All Container, Kubernetes & orchestration entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.