CVE-2026-46453

{
  "id": "CVE-2026-46453",
  "sourceIdentifier": "[email protected]",
  "published": "2026-07-06T09:16:36.317",
  "lastModified": "2026-10-25T15:10:00.147",
  "vulnStatus": "Analyzed",
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel ElasticSearch Rest Client.\n\nThe 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.\nThis issue affects Apache Camel: from 4.3.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.\n\nUsers are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix renames the camel-elasticsearch-rest-client Exchange header constant string values (ID, SEARCH_QUERY, INDEX_SETTINGS, INDEX_NAME, OPERATION) to carry the Camel prefix (CamelElasticsearchId, CamelElasticsearchSearchQuery, CamelElasticsearchIndexSettings, CamelElasticsearchIndexName, CamelElasticsearchOperation) so that they are blocked by the inbound HttpHeaderFilterStrategy; the Java field names are unchanged. For deployments that cannot upgrade immediately, strip the affected headers from untrusted inbound messages before they reach the producer (for example removeHeader('SEARCH_QUERY'), removeHeader('OPERATION'), removeHeader('INDEX_NAME'), removeHeader('INDEX_SETTINGS') and removeHeader('ID') in front of the elasticsearch-rest-client endpoint), or apply a custom HeaderFilterStrategy that blocks these names."
    },
    {
      "lang": "es",
      "value": "Validación de entrada incorrecta, vulnerabilidad de omisión de autorización a través de clave controlada por el usuario en Apache Camel ElasticSearch Rest Client.\n\nEl componente camel-elasticsearch-rest-client lee varias cabeceras de Exchange para controlar su comportamiento - SEARCH_QUERY (un cuerpo de consulta avanzado), OPERATION (qué operación de Elasticsearch ejecutar), INDEX_NAME, INDEX_SETTINGS e ID. Los valores de cadena de estas constantes de cabecera, definidas en ElasticSearchRestClientConstant, son nombres simples sin prefijo (’SEARCH_QUERY’, ’OPERATION’, ’INDEX_NAME’, ’INDEX_SETTINGS’, ’ID’) en lugar de los nombres con prefijo ’Camel’ utilizados por cualquier otro componente de Camel (por ejemplo, CamelSqlQuery, CamelMongoDbCriteria, CamelCqlQuery). El filtro de cabeceras HTTP de entrada de Camel, HttpHeaderFilterStrategy, bloquea solo los nombres de cabecera que comienzan con ’Camel’ o ’camel’. Debido a que los nombres de las cabeceras de Elasticsearch no llevan ese prefijo, pasan a través del filtro de entrada sin cambios. Cuando una ruta de Camel expone un punto de entrada HTTP (por ejemplo, platform-http) delante de un productor elasticsearch-rest-client, un cliente HTTP no confiable puede establecer estas cabeceras directamente en su solicitud y anular la consulta y la operación que el autor de la ruta configuró: leyendo cada documento en el índice (SEARCH_QUERY con una consulta match_all), eliminando documentos (OPERATION establecido en Delete junto con ID), o exfiltrando campos seleccionados. No se requieren credenciales y el productor lee las cabeceras incondicionalmente.\nEste problema afecta a Apache Camel: desde 4.3.0 antes de 4.14.8, desde 4.15.0 antes de 4.18.3, desde 4.19.0 antes de 4.21.0.\n\nSe recomienda a los usuarios actualizar a la versión 4.21.0, que corrige el problema. Si los usuarios están en la rama de versiones LTS 4.14.x, entonces se sugiere que actualicen a 4.14.8. Si los usuarios están en la rama de versiones 4.18.x, entonces se sugiere que actualicen a 4.18.3. La corrección renombra los valores de cadena constantes de las cabeceras de Exchange de camel-elasticsearch-rest-client (ID, SEARCH_QUERY, INDEX_SETTINGS, INDEX_NAME, OPERATION) para que lleven el prefijo Camel (CamelElasticsearchId, CamelElasticsearchSearchQuery, CamelElasticsearchIndexSettings, CamelElasticsearchIndexName, CamelElasticsearchOperation) para que sean bloqueados por el HttpHeaderFilterStrategy de entrada; los nombres de los campos Java no se modifican. Para implementaciones que no pueden actualizarse inmediatamente, elimine las cabeceras afectadas de los mensajes de entrada no confiables antes de que lleguen al productor (por ejemplo, removeHeader(’SEARCH_QUERY’), removeHeader(’OPERATION’), removeHeader(’INDEX_NAME’), removeHeader(’INDEX_SETTINGS’) y removeHeader(’ID’) delante del punto final elasticsearch-rest-client), o aplique una HeaderFilterStrategy personalizada que bloquee estos nombres."
    }
  ],
  "affected": [
    {
      "source": "[email protected]",
      "affectedData": [
        {
          "vendor": "Apache Software Foundation",
          "product": "Apache Camel",
          "defaultStatus": "unaffected",
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "packageName": "org.apache.camel:camel-elasticsearch-rest-client",
          "versions": [
            {
              "version": "4.3.0",
              "lessThan": "4.14.8",
              "versionType": "semver",
              "status": "affected"
            },
            {
              "version": "4.15.0",
              "lessThan": "4.18.3",
              "versionType": "semver",
              "status": "affected"
            },
            {
              "version": "4.19.0",
              "lessThan": "4.21.0",
              "versionType": "semver",
              "status": "affected"
            }
          ]
        }
      ]
    }
  ],
  "metrics": {
    "cvssMetricV31": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary",
        "cvssData": {
          "version": "3.1",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "attackVector": "NETWORK",
          "attackComplexity": "LOW",
          "privilegesRequired": "NONE",
          "userInteraction": "NONE",
          "scope": "UNCHANGED",
          "confidentialityImpact": "LOW",
          "integrityImpact": "NONE",
          "availabilityImpact": "NONE"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "timestamp": "2026-07-06T18:44:05.942781Z",
          "id": "CVE-2026-46453",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "version": "2.0.3"
        }
      }
    ]
  },
  "weaknesses": [
    {
      "source": "[email protected]",
      "type": "Secondary",
      "description": [
        {
          "lang": "en",
          "value": "CWE-20"
        },
        {
          "lang": "en",
          "value": "CWE-639"
        }
      ]
    },
    {
      "source": "[email protected]",
      "type": "Primary",
      "description": [
        {
          "lang": "en",
          "value": "CWE-639"
        }
      ]
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "operator": "OR",
          "negate": false,
          "cpeMatch": [
            {
              "vulnerable": true,
              "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
              "versionStartIncluding": "4.3.0",
              "versionEndExcluding": "4.14.8",
              "matchCriteriaId": "C35BE0C9-865B-451A-80EE-D483CB7AD822"
            },
            {
              "vulnerable": true,
              "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
              "versionStartIncluding": "4.15.0",
              "versionEndExcluding": "4.18.3",
              "matchCriteriaId": "0AEE4159-4465-4ACD-B94A-1E4682C85270"
            },
            {
              "vulnerable": true,
              "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
              "versionStartIncluding": "4.19.0",
              "versionEndExcluding": "4.21.0",
              "matchCriteriaId": "1C2A1A7A-FADC-470F-8265-FA126AFD94ED"
            }
          ]
        }
      ]
    }
  ],
  "references": [
    {
      "url": "https://camel.apache.org/security/CVE-2026-46453.html",
      "source": "[email protected]",
      "tags": [
        "Mitigation",
        "Vendor Advisory"
      ]
    },
    {
      "url": "http://www.openwall.com/lists/oss-security/2026/07/05/6",
      "source": "af854a3a-2127-422b-91ae-364da2661108",
      "tags": [
        "Mailing List",
        "Third Party Advisory"
      ]
    }
  ]
}