CVE-2026-63621
Received Received - Intake

Header Injection in Apache Camel Knative Component

Vulnerability report for CVE-2026-63621, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-24

Last updated on: 2026-08-24

Assigner: Apache Software Foundation

Description

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode the HTTP-header path filters Camel-internal headers through KnativeHttpHeaderFilterStrategy, but in structured content mode (Content-Type application/cloudevents+json) the CloudEvent extension fields are read directly from the JSON body and every extension key is copied into the Exchange headers without applying any HeaderFilterStrategy (CloudEventProcessors, spec versions 1.0, 1.0.1 and 1.0.2). As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelHttpUri, CamelHttpPath, CamelFileName) via a structured-mode CloudEvent request, matched case-insensitively against Camel's header map. When a route forwards messages from a Knative consumer to a header-driven component such as camel-http or camel-file, the injected headers override configured values, enabling server-side request forgery (SSRF), path traversal or message-dispatch redirection depending on the route. This is an incomplete fix of the inbound header filtering previously added for the binary content-mode path, and is the same pattern addressed in camel-cxf/camel-knative (CVE-2026-47323), camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and the non-HTTP strategies (CVE-2026-40453). This issue affects Apache Camel: from 3.15.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.4. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. The non-LTS releases 4.15.0 through 4.17.0 and 4.19.0 through 4.21.0 are affected but do not receive a maintenance fix; users on those versions should upgrade to 4.18.4 or 4.22.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-24
AI Q&A
2026-08-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 9 associated CPEs
Vendor Product Version / Range
apache camel From 3.15.0 (inc) to 4.14.9 (exc)
apache camel From 4.15.0 (inc) to 4.18.4 (exc)
apache camel From 4.19.0 (inc) to 4.21.0 (exc)
apache camel 4.22.0
apache camel 4.18.4
apache camel 4.14.9
apache camel to 4.14.9 (exc)
apache camel to 4.18.4 (exc)
apache camel to 4.22.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability involves improper input validation in Apache Camel's Knative component. In structured content mode, CloudEvent extension fields are copied directly into message headers without filtering. This allows attackers to inject Camel-internal headers like CamelHttpUri or CamelHttpPath, which can override route configurations and lead to attacks such as server-side request forgery or path traversal.

Detection Guidance

To detect this vulnerability, check if your Apache Camel version is within the affected range (3.15.0 to 4.14.8, 4.15.0 to 4.18.3, or 4.19.0 to 4.21.0). Run: 'camel --version' to verify. Inspect logs for CloudEvent requests with structured content mode (Content-Type: application/cloudevents+json) that inject Camel-internal headers like CamelHttpUri or CamelHttpPath.

Impact Analysis

An attacker could exploit this to manipulate HTTP requests, redirect file operations, or alter message routing by injecting malicious headers. This could result in unauthorized access to internal systems, data exfiltration, or disruption of services if the route interacts with sensitive components like HTTP endpoints or file systems.

Compliance Impact

This vulnerability could lead to unauthorized data access or exfiltration, violating confidentiality requirements in GDPR and HIPAA. If exploited, it may result in data breaches, triggering compliance violations, regulatory penalties, and reputational damage for organizations handling sensitive data.

Mitigation Strategies

Upgrade Apache Camel to a fixed version: 4.14.9, 4.18.4, or 4.22.0. If using LTS streams, upgrade to 4.14.9 or 4.18.4. As a temporary measure, strip Camel-internal headers at route start or enable bridgeEndpoint on HTTP producers.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-63621. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart