cve.bz

CVE-2026-95664 apache camel: Expression Language Injection

5.4 mediumEPSS 0.8%Fix available

Medium (5.4) in apache camel. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') vulnerability in Apache Camel AWS2-s3 component. This issue affects Apache Camel: from 4.8.0 before 4.18.5, from 4.19.0 before 4.22.2. For the object it uploads, reads or deletes, the camel-aws2-s3 producer takes the key from the CamelAwsS3Key message header and falls back to the keyName option configured on the endpoint only when that header is absent. Since 4.8.0, AWS2S3Utils.determineKey() also passed the resulting value to the Simple language whenever it contained ${ or $simple{, so that a route could use a dynamic key, and the evaluation applied to a value taken from the header as well as to the configured option. The header is not route configuration, however: the aws2-s3 consumer sets CamelAwsS3Key on the exchanges it creates to the key of the object it read, that is, the name of the object in the bucket. In a route that does nothing more than consume from one aws2-s3 endpoint and produce to another, the name of each consumed object therefore reached the producer, and a name containing either marker was evaluated as an expression, although the route author never asked for any evaluation, and configuring keyName on the producer did not prevent it, because the header took precedence. A key that a route copied into the header from other message content was evaluated in the same way. Anyone able to choose the name of an object in a bucket that such a route consumes, typically a principal allowed to upload to that bucket, could therefore have Simple expressions of their choosing evaluated in the Camel process. The Simple language can read JVM system properties, environment variables and configuration properties, which commonly carry credentials, and, where camel-bean is on the classpath, invoke methods on beans in the registry. The evaluated result became the key the producer used, so reading a value back additionally required the ability to see object names in the destination bucket, while a method invocation took effect without it; together with the need to name an object in a consumed bucket, this is why the severity is assessed medium. The bucket name went through the same evaluation, but the consumer only ever places the bucket configured on its own endpoint in a bucket header, never a value derived from a remote object, so the bucket name was not reachable in this way. Releases before 4.8.0 used the key from the header as given and are not affected. Users are recommended to upgrade to version 4.23.0, which fixes the issue. If users are on the 4.22.x releases stream, then they are suggested to upgrade to 4.22.2. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.5. The 4.8.x to 4.17.x and 4.19.x to 4.21.x release lines reached end of life before this issue was resolved and will not receive a fix, so deployments on them must move to a supported release. After upgrading, a key or bucket name supplied through a message header is used literally, so a route that put an unevaluated Simple expression in the CamelAwsS3Key or CamelAwsS3OverrideBucketName header must evaluate it in the route instead, for example with setHeader and simple(), or configure it as the keyName or bucketName option of the endpoint. For deployments that cannot upgrade immediately, do not let a key derived from an object name or from other untrusted message content reach an aws2-s3 producer unchecked: in routes that pass exchanges from an aws2-s3 consumer to an aws2-s3 producer, either remove the CamelAwsS3Key header before the producer with removeHeader(“CamelAwsS3Key”), so that the keyName configured on the endpoint is used, or reject exchanges whose CamelAwsS3Key header contains ${ or $simple{. Configuring keyName alone is not a workaround, because the header takes precedence over it. As defence in depth, allow only trusted principals to write to buckets that Camel routes consume.

Severity

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.8% (unchanged from 0.8% a week ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-917 Improper Neutralization of Special Elements used in an Expression Language Statement (Expression Language 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-95664 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95664?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95664?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-95664 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-95664

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-95664](https://cve.bz/cve/badge/CVE-2026-95664.svg)](https://cve.bz/cve/CVE-2026-95664)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.8.0 before 4.18.5
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.22.2

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat Product Security rates the impact of this vulnerability as Moderate because exploitation requires authenticated or authorized access to upload or manipulate object names in the source storage bucket. In affected Red Hat builds of Apache Camel and OpenShift Serverless Knative integrations, routes that transfer data directly between S3 consumers and producers without sanitizing exchange headers may evaluate embedded Simple language syntax within the object key. Successful evaluation could expose environment variables or execute registry bean methods within the running integration context, though exfiltration is constrained by destination bucket visibility and the permissions granted to the application runtime.

Red Hat's mitigation

To mitigate this vulnerability without replacing component packages, configure Camel routes to prevent untrusted S3 object keys from reaching the aws2-s3 producer:

1. In routes transferring messages from an aws2-s3 consumer to an aws2-s3 producer, explicitly remove the `CamelAwsS3Key` header prior to the producer step using `<removeHeader name="CamelAwsS3Key"/>` in XML DSL or `.removeHeader("CamelAwsS3Key")` in Java DSL. Define the intended object destination via the producer endpoint's `keyName` option.

2. Alternatively, insert route validation logic to reject or filter out exchanges whose `CamelAwsS3Key` header contains expression markers such as `${` or `$simple{`.

3. As an operational control, restrict write and upload permissions on source S3 buckets strictly to trusted principals.

Warning: Modifying and applying route configuration changes requires reloading or restarting the affected integration services, which may cause a temporary service disruption.

ProductPackageStateAdvisory
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9Fix deferred
Red Hat build of Apache Camel 4 for Quarkus 3camel-aws2-s3Fix deferred
Red Hat build of Apache Camel for Spring Boot 4camel-aws2-s3Fix deferred
Red Hat Fuse 7camel-aws2-s3Not affected

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-95664.

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-95664 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-95664 — Apache Camel camel-aws2-s3 evaluated a header-supplied object key as a Simple expression (CWE-917). Camel S…

References

Check your stackJSON