cve.bz

CVE-2026-63621 apache camel: Injection

5.3 mediumEPSS 0.5%Fix available

Medium (5.3) in apache camel. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-knative 4.14.9, 4.18.4, 4.22.0.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component (Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-63621 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63621?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63621?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63621 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-63621

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-63621](https://cve.bz/cve/badge/CVE-2026-63621.svg)](https://cve.bz/cve/CVE-2026-63621)

HTML:

<a href="https://cve.bz/cve/CVE-2026-63621"><img src="https://cve.bz/cve/badge/CVE-2026-63621.svg" alt="CVE-2026-63621"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 3.15.0 before 4.14.9
Apache Software Foundation Apache Camelfrom 4.15.0 before 4.18.4
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.21.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vvwm-3j43-7pfmMavenorg.apache.camel:camel-knative>=3.15.0 <4.14.94.14.9
GHSA-vvwm-3j43-7pfmMavenorg.apache.camel:camel-knative>=4.15.0 <4.18.44.18.4
GHSA-vvwm-3j43-7pfmMavenorg.apache.camel:camel-knative>=4.19.0 <4.22.04.22.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This is an Important vulnerability in Apache Camel Knative that allows an unauthenticated, remote attacker to perform server-side request forgery, path traversal, or message-dispatch redirection. The flaw occurs because the Knative consumer in camel-knative improperly processes CloudEvent extension fields in structured content mode, allowing the injection of internal Camel headers. This can lead to an attacker controlling internal routing or file access within affected Red Hat OpenShift Serverless and Red Hat build of Apache Camel deployments.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4.18.4 for Spring Boot 3.5.16camel-knativeFixed 2026-09-24RHSA-2026:71675
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-log-sink-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-timer-source-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-63621.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-63621 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-63621 (Apache Camel camel-knative structured CloudEvent header injection) — Camel Spring Boot + Camel Quarkus

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-74 (37), CWE-20 (51).

References

Check your stackJSON