VulnerabilityPublished 26 Oct 2026

CVE-2026-95664: Apache Camel · Expression Language Injection

Affects Apache CamelSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 4.22.2 or 4.18.5 when convenient.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.22.2, 4.18.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache to 4.22.2 or 4.18.5.

Affected software

Product	Affected	Fixed in
Apache Camelorg.apache.camel:camel-aws2-s3	Affected >=4.19.0 <4.22.2	Fixed in 4.22.2
Apache Camelorg.apache.camel:camel-aws2-s3	Affected >=4.8.0 <4.18.5	Fixed in 4.18.5
MavenApache Software Foundation/org.apache.camel:camel-aws2-s3`pkg:maven/Apache Software Foundation/org.apache.camel:camel-aws2-s3`Other threats	Affected >=4.8.0 <4.18.5 >=4.19.0 <4.22.2	Fixed in 4.18.5 4.22.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Apache Camel versions 4.18.5, 4.22.2, and later (including 4.23.0). Users should upgrade to one of these versions to resolve the vulnerability. For users unable to upgrade immediately, it is recommended to prevent untrusted keys from reaching the aws2-s3 producer by removing the CamelAwsS3Key header before the producer or rejecting exchanges where the header contains '${' or '$simple{'. Configuring the keyName option alone is not sufficient because the header takes precedence. Additionally, restrict write permissions on buckets consumed by Camel routes to trusted principals only. After upgrading, any expressions in headers must be explicitly evaluated within the route using safe methods.

Description

CVE-2026-95664 is an Expression Language Injection vulnerability in the Apache Camel AWS2-s3 component affecting versions from 4.8.0 before 4.18.5 and from 4.19.0 before 4.22.2. The issue arises because the key used by the aws2-s3 producer is taken from a message header and evaluated as a Simple language expression if it contains certain markers, allowing untrusted input to be executed. This can lead to unauthorized access to JVM system properties, environment variables, and invocation of methods on beans, potentially exposing sensitive information. The vulnerability is fixed in versions 4.18.5 and 4.22.2. Users are advised to upgrade to these versions or 4.23.0 or later. Workarounds include removing or validating the CamelAwsS3Key header to prevent untrusted expressions from being evaluated.

Impact

An attacker who can control the name of objects in an S3 bucket consumed by an affected Apache Camel route can cause arbitrary Simple language expressions to be evaluated in the Camel process. This can lead to unauthorized disclosure of JVM system properties, environment variables, and configuration properties, which often contain sensitive credentials. Additionally, if camel-bean is on the classpath, the attacker can invoke methods on beans in the registry, potentially causing further impact. The severity is medium because exploitation requires the ability to name objects in the consumed bucket and, for some impacts, to read object names in the destination bucket. There is no known exploitation in the wild.

CWE-917Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.
Architecture and Design
Avoid adding user-controlled data into an expression interpreter when possible.
Implementation
If user-controlled data must be added to an expression interpreter, one or more of the following should be performed: Validate that the user input will not evaluate as an expression; Encode the user input in a way that ensures it is not evaluated as an expression
System Configuration · Operation
The framework or tooling might allow the developer to disable or deactivate the processing of EL expressions, such as setting the isELIgnored attribute for a JSP page to "true".
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 09:01 UTC

WeaknessesCWE-917

Technical details

References

Community reviews

Related threats