Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-46453 medium CVSS 5.3

Vulnerability in org.apache.camel:camel-elasticsearch-rest-client (CVE-2026-46453)

Summary

Vulnerability in org.apache.camel:camel-elasticsearch-rest-client (CVE-2026-46453). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.21.0 or later.

Original description

The description as published by the source.

Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel ElasticSearch Rest Client.

The camel-elasticsearch-rest-client component reads several Exchange headers to control its behaviour - SEARCH_QUERY (an advanced query body), OPERATION (which Elasticsearch operation to run), INDEX_NAME, INDEX_SETTINGS and ID. The string values of these header constants, defined in ElasticSearchRestClientConstant, are plain unprefixed names ('SEARCH_QUERY', 'OPERATION', 'INDEX_NAME', 'INDEX_SETTINGS', 'ID') rather than the 'Camel'-prefixed names used by every other Camel component (for example CamelSqlQuery, CamelMongoDbCriteria, CamelCqlQuery). Camel's inbound HTTP header filter, HttpHeaderFilterStrategy, blocks only header names that begin with 'Camel' or 'camel'. Because the Elasticsearch header names do not carry that prefix, they pass through the inbound filter unchanged. When a Camel route exposes an HTTP entry point (for example platform-http) in front of an elasticsearch-rest-client producer, an untrusted HTTP client can set these headers directly on its request and override the query and operation that the route author configured: reading every document in the index (SEARCH_QUERY with a match_all query), deleting documents (OPERATION set to Delete together with ID), or exfiltrating selected fields. No credentials are required and the producer reads the headers unconditionally.
This issue affects Apache Camel: from 4.3.0 before 4.14.8,…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-46453 has been found in org.apache.camel:camel-elasticsearch-rest-client.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade org.apache.camel:camel-elasticsearch-rest-client to 4.21.0 or later.
If unsure, ask your IT team or search "org.apache.camel:camel-elasticsearch-rest-client CVE-2026-46453" on the vendor's site.

CVE-2026-46453 (org.apache.camel:camel-elasticsearch-rest-client) — CWE-20 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.21.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-20) exists in org.apache.camel:camel-elasticsearch-rest-client.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.camel:camel-elasticsearch-rest-client.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.21.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.camel:camel-elasticsearch-rest-client を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.camel:camel-elasticsearch-rest-client to 4.21.0

    ステージング環境で 4.21.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.apache.camel:camel-elasticsearch-rest-client
[{"type":"ECOSYSTEM","events":[{"introduced":"4.19.0"},{"fixed":"4.21.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details