Vulnerabilidades explotables hoy
406,233en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,766
Nuevos KEV · 24H0
Exploit Today ≥ 701,698
Distribución · última ventana
- Crítico5,579
- Alto21,699
- Medio20,217
- Bajo2,100
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2024-38666—97.4%
——29——CVE-2017-11769—97.4%
——29——CVE-2015-6076—97.4%
——29——CVE-2016-4372—97.4%
——29——CVE-2012-2557—97.4%
——29——CVE-2022-26187—97.4%
——29——CVE-2004-1331—97.4%
——29——CVE-2018-12031—97.4%
——29——CVE-2010-2748—97.4%
——29——CVE-2018-16060—97.4%
——29——CVE-2026-473239.8 CRÍ97.4%
——29Camel-CXF and Camel-Knative Message Header Injection via Missing Inbound Filtering
The CXF and Knative HeaderFilterStrategy implementations (CxfRsHeaderFilterStrategy in camel-cxf-rest, CxfHeaderFilterStrategy in camel-cxf-transport, and KnativeHttpHeaderFilterStrategy in camel-knative-http) only filter outbound Camel-internal headers via setOutFilterStartsWith, while not configuring inbound filtering via setInFilterStartsWith. As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelExecCommandExecutable, CamelFileName) via HTTP requests to CXF-RS or CXF-SOAP endpoints. When a route forwards messages from these endpoints to header-driven components such as camel-exec or camel-file, the injected headers override configured values, enabling remote code execution or arbitrary file writes. This is the same pattern that was previously addressed in camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and non-HTTP strategies (CVE-2026-40453).
This issue affects Apache Camel: from 3.18.0 before 4.14.6, from 4.15.0 before 4.18.2.
Users are recommended to upgrade to version 4.19.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.2. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6.6dCVE-2013-3190—97.4%
——29——CVE-1999-1578—97.4%
——29——CVE-2007-4286—97.4%
——29——CVE-2020-16137—97.4%
——29——CVE-2009-2529—97.4%
——29——CVE-2011-0364—97.4%
——29——CVE-2018-5093—97.4%
——29——CVE-2021-33813—97.4%
——29——CVE-2004-1306—97.4%
——29——CVE-2020-14947—97.4%
——29——CVE-2015-0030—97.4%
——29——CVE-2015-6148—97.4%
——29——CVE-2023-46370—97.4%
——29——CVE-2010-1903—97.4%
——29——CVE-2018-16287—97.4%
——29——CVE-2019-15683—97.4%
——29——CVE-2026-33497—97.4%
——29——CVE-2021-31800—97.4%
——29——CVE-1999-0945—97.4%
——29——CVE-2015-6081—97.4%
——29——CVE-2022-32449—97.4%
——29——CVE-2015-6077—97.4%
——29——CVE-2025-7769—97.4%
——29——CVE-2006-4018—97.4%
——29——CVE-2017-14094—97.4%
——29——CVE-2021-42561—97.4%
——29——CVE-2017-8507—97.4%
——29——CVE-2020-8845—97.4%
——29——CVE-2009-4073—97.4%
——29——