YAML Injection in Apache Camel K Custom Resources

Improper Control of Generation of Code ('Code Injection') vulnerability in Apache Camel K. A YAML injection vulnerability in custom resource configuration allows an authorized CR author to inject arbitrary Kubernetes objects, potentially enabling unauthorized resource creation with the privileges of the operator. This issue affects Apache Camel K: from 2.0.0 before 2.9.3, from 2.10.1 before 2.10.2. Users are recommended to upgrade to version 2.9.3, 2.10.2 or 2.11.0, which fixes the issue.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

Apache Camel K versions 2.0.0 through 2.9.2 and 2.10.1 through 2.10.1 contain a critical code injection vulnerability (CVSS 9.8) in custom resource configuration handling. A YAML injection flaw allows authorized custom resource authors to inject arbitrary Kubernetes objects, which are then instantiated with the elevated privileges of the Camel K operator. This means attackers with CR creation permissions can escalate their access and create unauthorized resources across the cluster—potentially compromising the entire Kubernetes environment. The vulnerability affects operators and platform teams managing Camel K deployments, particularly in multi-tenant environments where CR authorship is delegated to developers.

Casky's 323 mapped security skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK techniques TA0001 (Reconnaissance) and TA0043 (Resource Development). Practitioners using Casky would identify suspicious YAML structures in CR definitions, detect attempts to embed Kubernetes API objects outside expected schemas, and spot privilege escalation patterns where low-privileged users create resources that execute under operator service accounts. The platform's skills would flag anomalous custom resource specifications, unauthorized API group references, and injection payloads attempting to instantiate Deployments, DaemonSets, or ClusterRoles—enabling security teams to catch exploitation attempts before operators process malicious configurations.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-80352.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-80352

Casky has 323 skills that investigate the attack patterns behind CVE-2026-80352. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn