Operator-pod code execution via Maven directive injection
Published Sep 10, 2026 · Updated Sep 10, 2026
Eval injection in Apache Camel K 2.0.0 through 2.9.2 and 2.10.1 allows remote authenticated users to execute code in the operator pod. Dynamically evaluated Maven configuration fails to neutralize directives from tenant-controlled repository content before processing it. Exploitation requires control of repository content consumed by a tenant build, and resulting code inherits the operator pod's privileges.
Summary
What happened
Eval injection in Apache Camel K 2.0.0 through 2.9.2 and 2.10.1 allows remote authenticated users to execute code in the operator pod. Dynamically evaluated Maven configuration fails to neutralize directives from tenant-controlled repository content before processing it. Exploitation requires control of repository content consumed by a tenant build, and resulting code inherits the operator pod's privileges.
The record
- CVE
- CVE-2026-80351
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Camel K
- Classifications
- CWE-95, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.9.3
- Affected versionversion=2.10.1 <2.10.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo