CVE-2026-80351
Camel K tenant repositories reach Maven execution inside the operator pod
Apache disclosed CVE-2026-80351 in Camel K on 8 September 2026. Maven configuration built from tenant-controlled repository content is evaluated inside the operator pod, so a tenant could run code with the operator's privileges. Apache rates it Critical but published no CVSS score. Fixed in 2.9.3, 2.10.2 and 2.11.0. Not in CISA KEV. No public PoC found.
By ThreatWire Desk · Published 10 Sept 2026 · Updated 26 Oct 2026
- CVSS
- Unknown
- Vector
- Not recorded
- Class
- RCE
- Status
- No PoC
- KEV
- Not in CISA KEV
- 0-day
- No
- Vendor
- Apache
- Products
- Apache Camel K
- Affected
- Apache Camel K from 2.0.0 before 2.9.3, and the 2.10.x line before 2.10.2. The Apache advisory table and NVD list 2.10.0 as the start of the 2.10 range; the CVE record text says 2.10.1. Treat every 2.10 release before 2.10.2 as affected.
- Fixed
- Camel K 2.9.3, 2.10.2 and 2.11.0 (all tagged 31 August 2026).
- CWE
- CWE-95
- Published
- 10 Sept 2026
- Updated
- 26 Oct 2026
No public PoC is confirmed on this record.
CVE-2026-80351 is a flaw in Apache Camel K, the Kubernetes operator that builds and runs Camel integrations. The Apache Camel PMC published the advisory on 8 September 2026. The CVE record and the oss-security post followed on 10 September.
The operator runs Maven to build integrations. Apache says the Maven configuration it evaluates did not neutralize directives coming from tenant-controlled repository content. Apache classifies it as eval injection.
The result is code execution inside the operator pod, with the operator's privileges. A tenant should not be able to reach that level.
The attacker is a tenant who can point Camel K at repository content they control. The advisory does not describe an unauthenticated path.
Affected: Camel K 2.0.0 before 2.9.3, and the 2.10 line before 2.10.2. The Apache table and NVD start the 2.10 range at 2.10.0, while the CVE record text says 2.10.1. Fixed: 2.9.3, 2.10.2 and 2.11.0.
Apache labels the severity Critical but published no CVSS score. CISA's ADP enrichment added a CVSS 3.1 score of 9.8 that assumes no privileges are needed. Apache's text describes a tenant, so we keep the score field empty.
The advisory credits internal analysis and lists no workaround beyond the upgrade.
The CVE is not in the CISA KEV catalog (catalog 2026.10.23, checked 26 October 2026). CISA's SSVC entry sets exploitation to none. ThreatWire found no public proof of concept.
Read the full explainer on the eight Camel and Camel K flaws. The sibling Camel K flaw is CVE-2026-80352.
Sources
Related on ThreatWire
- NewsApache Camel and Camel K: eight high and critical flaws, from OAuth bypass to deserialization RCE
- VendorAll Apache CVEs in the ThreatWire tracker
- CVE recordCVE-2026-80352: Camel K Master trait serviceAccountName YAML injection lets a CR author apply arbitrary Kubernetes objects
- CVE recordCVE-2026-71895: DolphinScheduler lets non-admin users retrieve Kubernetes credentials
- CVE recordCVE-2026-88900: Camel-JGroups consumer deserializes cluster messages without a filter, leading to code execution
- CVE recordCVE-2026-78164: Camel HTTP producers resolve property placeholders in message-supplied URI headers, exposing secrets
- CVE recordCVE-2026-78165: Camel-Spring-Redis default serializer deserializes Redis payloads without a filter, enabling code execution
- CVE recordCVE-2026-80312: Camel-OAuth processors fail open, letting requests that failed authentication through