Empresa
¿Quiénes somos? Visión y Valores
Herramientas
Email Checker Vigía DNS SSL Checker Password Strength HTTP Headers Password Generator VPN PSK Generator
Alertas
Todas las alertas Vulnerabilidades Incidentes Solo críticas En CISA KEV Vigía LATAM
Editorial
Análisis técnico ¿Cuál es mi IP?
Blog
Blog 2MCI Noticias ISO 27001 Amenazas LATAM Recursos Gratuitos eBook Gratuito Newsletter Podcast / YouTube
Empresa
Servicios Contacto Suscribirse al Newsletter
Nuevo en 2MCI
Crear cuenta gratis Ver herramientas sin registro
Ya tengo cuenta
Iniciar sesión
Equipo
Portal interno 2MCI
Alto CVE-2026-85250 Multiple Vendors

Vulnerabilidad XXE alta en Apache Camel afecta procesamiento de XML en versiones 4.0.0 a 4.22.1

Vulnerabilidad · Publicado 19/10/2026

7.5
CVSS 3.x
04 Medio7 Alto9 Crítico10
Severidad: Alto
Resumen ejecutivo

Apache Camel contiene una vulnerabilidad de Inyección de Entidades Externas XML (XXE) en el componente XPath que permite a atacantes acceder a archivos locales, ejecutar ataques de denegación de servicio o exfiltrar datos sensibles. Afecta versiones desde 4.0.0 anterior a 4.18.5 y desde 4.19.0 anterior a 4.22.1. Empresas en LATAM que usen Camel en integraciones SOA, APIs o procesamiento de datos XML son objetivos prioritarios.

Análisis asistido por IA, contexto LATAM revisado por el equipo 2MCI.

Descripción técnica

Descripción técnica

Improper Restriction of XML External Entity Reference vulnerability in Apache Camel XPath component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. With documentType set to InputSource, XPathBuilder handed the payload straight to javax.xml.xpath, which builds a DocumentBuilder of its own using the JDK defaults. The hardening applied to Camel's default document type was therefore bypassed: a DOCTYPE declaration that is refused on the default type was accepted here, and the external entity it declared was resolved and expanded into the evaluated document. An external sender whose XML reaches such an expression could read files readable by the Camel process and cause the process to issue requests to hosts it names. The two document types disagreeing on parser configuration is what made this reachable, since a deployment choosing InputSource for streaming reasons had no indication it was also choosing a weaker parser. Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The InputSource document type now goes through the same hardened parser as the default type, so a DOCTYPE is refused. Note that it also shares that type's documented escape hatch: the same DocumentBuilderFactory system properties that relax the default type relax this one, so a deployment that has set them remains unprotected by design. For deployments that cannot upgrade immediately, do not use documentType=InputSource on expressions evaluated over untrusted XML; the default document type already refuses a DOCTYPE.

Puntuación CVSS

Score: 7.5/10 — Severidad: HIGH — Estado NIST: Received

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

Debilidades (CWE)

CWE-611

Fuente oficial

Publicado en NIST NVD.

¿Qué hacer?
  • Inventariar sistemas con Apache Camel 4.0.0-4.18.4 y 4.19.0-4.22.0
  • Actualizar a versión 4.18.5 o 4.22.1+ inmediatamente
  • Si actualización no es posible, deshabilitar documentType InputSource en XPathBuilder
  • Implementar WAF para bloquear payloads XXE (patrones de DOCTYPE, ENTITY)
  • Validar y monitorear logs de Camel para intentos de XXE
Esta alerta fue generada automáticamente a partir del NVD del NIST.