CVE Professor — Güvenlik Açığı Takip & Analiz
›
CVE-2026-95664

CWE-917

ORTA CVSS 5.4 ⚡ EPSS 0.8% NVD

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.

Yayınlanma 26.10.2026
ISO Tarih 2026-10-26
CVSS Sürüm v3.1
Kaynak NVD
CVSS v3.1 Metrikleri
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Attack Vector Network AV:N
Attack Complexity Low AC:L
Privileges Req. Low PR:L
User Interaction None UI:N
Scope Unchanged S:U
Confidentiality Low C:L
Integrity Low I:L
Availability None A:N
EPSS — Exploit Olasılık Skoru
0.8%
30 günlük olasılık
Tüm CVElerin 58. yüzdeliğinde — Bu açığın istismar edilme ihtimali çoğu CVEden yüksek.
AI Güvenlik Analizi

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-95664
CVSS 5.4/10 · ORTA · 26.10.2026
CWE: CWE-917
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 AÇIK NEDİR?
Açıklama: 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 t…
Etkilenen: apache:camel

⚡ SALDIRI ZİNCİRİ
İnternet üzerinden uzaktan | düşük yetkili hesap | kullanıcı etkileşimi YOK | düşük karmaşıklık.

🌍 GERÇEK DÜNYA ETKİSİ

🛡️ ÇÖZÜM VE MİTİGASYON
→ apache:camel için üretici güvenlik güncellemesini uygula.
→ WAF kuralı ekle, anormal trafik için IDS alert oluştur.

⚠️ ACİLİYET
📋 Rutin güncelleme (30 gün)

────────────────────────────────────────
[Kural Tabanlı Analiz] [💡 config.json dosyasına ai_key (Claude: sk-ant-... veya Groq: gsk_...) ekleyerek gerçek AI analizi kullanabilirsiniz]

[⚠️ AI key mevcut ancak istek başarısız — kural tabanlı analiz kullanıldı]

Hedef Keşif Sorguları

FOFA Sorgusu

app="apache camel"
CVSS Skoru
5.4 / 10 · CVSS ORTA
Zayıflık Türleri (CWE)
CWE-917
Etkilenen Ürünler (1)
apache:camel (tüm sürümler)
İlgili CVE'ler
9.8
CVE-2026-109432
Camunda 7.24.0 before 7.24.14 and 7.23.0 before 7.23.17 contains an expression injection vulnerability where A
9.8
CVE-2026-104711
Improper neutralization of special elements used in an expression language statement ('Expression Language Inj
9.1
CVE-2026-87830
In the StAX streaming WS-SecurityPolicy validator, certain relative or unsupported XPath expressions can be co
8.8
CVE-2026-82912
Improper Neutralization of Special Elements Used in an Expression Language Statement ('Expression Language Inj
8.8
CVE-2026-83531
Improper Control of Generation of Code ('Code Injection'), Improper Neutralization of Special Elements used in