Improper input validation vulnerability in Apache Camel Karavan.



When a deployment was started, Karavan unmarshalled a project's `kubernetes.yaml` and applied every resource it contained to the cluster without restricting the resource kinds, without rejecting security-sensitive pod options, and without pinning the target namespace. An authenticated user of any role could therefore have Karavan apply arbitrary Kubernetes resources within the reach of its service account, including pods requesting hostNetwork, hostPID, hostIPC, hostPath volumes, host ports, privileged containers, privilege escalation or added capabilities.



This issue affects Apache Camel Karavan: from 4.0.0 before 4.22.1.



Users are recommended to upgrade to version 4.22.1, which fixes the issue.

Project Subscriptions

Vendors Products
Camel Karavan Subscribe
Advisories

No advisories yet.

Fixes

Solution

Upgrade to Apache Camel Karavan 4.22.1. Apache Camel Karavan has no maintenance branches, so 4.22.1 is the only release containing the fix. Operators should also ensure PodSecurity admission is enforced on the namespace Karavan deploys into, and keep the service account's RBAC no wider than Karavan requires.


Workaround

No workaround given by the vendor.

History

Thu, 15 Oct 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Sun, 11 Oct 2026 12:45:00 +0000

Type Values Removed Values Added
First Time appeared Apache
Apache camel Karavan
Vendors & Products Apache
Apache camel Karavan

Fri, 09 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
References

Fri, 09 Oct 2026 13:15:00 +0000

Type Values Removed Values Added
Description Improper input validation vulnerability in Apache Camel Karavan. When a deployment was started, Karavan unmarshalled a project's `kubernetes.yaml` and applied every resource it contained to the cluster without restricting the resource kinds, without rejecting security-sensitive pod options, and without pinning the target namespace. An authenticated user of any role could therefore have Karavan apply arbitrary Kubernetes resources within the reach of its service account, including pods requesting hostNetwork, hostPID, hostIPC, hostPath volumes, host ports, privileged containers, privilege escalation or added capabilities. This issue affects Apache Camel Karavan: from 4.0.0 before 4.22.1. Users are recommended to upgrade to version 4.22.1, which fixes the issue.
Title Apache Camel Karavan: unvalidated Kubernetes resources applied from a project's kubernetes.yaml
Weaknesses CWE-20
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-10-15T18:11:10.412Z

Reserved: 2026-09-30T14:36:48.954Z

Link: CVE-2026-103413

cve-icon Vulnrichment

Updated: 2026-10-09T15:07:26.504Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-09T13:17:07.633

Modified: 2026-10-15T19:17:13.957

Link: CVE-2026-103413

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-11T12:27:24Z

Weaknesses