Threat reportVulnerabilityTL-2026-4449
Apache Camel Vulnerabilities Allow Remote Code Execution, Authentication Bypass, and Data Theft (CVE-2026-80352, CVE-2026-80351 and 6 others)
Apache Camel Vulnerabilities Allow Remote Code Execution (TL-2026-4449) is a critical-severity software vulnerability scored CVSS 9.8, first published 2026-10-26. It has no confirmed attribution, affects Apache Software Foundation Apache Camel K, references 8 CVEs (CVE-2026-80352, CVE-2026-80351, CVE-2026-88900), maps to 6 MITRE ATT&CK techniques (T1005, T1059, T1190), and is covered by 9 detection rules and 6 indicators of compromise.
- CVSS
- 9.8/10Critical
- CVEs
- 8Referenced vulnerabilities
- Techniques
- 6MITRE ATT&CK
- Actors
- 0Not attributed
- Detection rules
- 9SPL · KQL · Sigma
- IOCs
- 6Indicators of compromise
Key facts for TL-2026-4449
- Threat ID
- TL-2026-4449
- Severity
- CRITICAL
- CVSS
- 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
- Status
- PATCHED
- Category
- VULNERABILITY
- First published
- Last reviewed
- Attribution confidence
- LOW
- Motivation
- UNKNOWN
- Target sectors
- technology, finance, government administration, health, telecoms
- Target regions
- Global
- Detection rules
- 9
- Indicators of compromise
- 6
How Apache Camel Vulnerabilities Allow Remote Code Execution works
Apache Camel disclosed eight vulnerabilities: two Critical in Camel K (Kubernetes YAML injection and tenant-controlled Maven execution in the operator pod) and six High in Camel components (JGroups and Spring Redis unsafe deserialization, OAuth fail-open authentication, HTTP placeholder injection, HTTP redirect credential leak, Smooks XXE). Fixes are available in Camel 4.18.5, 4.22.1, 4.23.0 and Camel K 2.9.3, 2.10.2, 2.11.0; no in-the-wild exploitation or public PoC was found in the sources reviewed.
On 2026-10-15 the Apache Camel project published a batch of security advisories (reported as 38 in total) fixed in Camel 4.18.5, 4.22.1 and 4.23.0. Eight of them are tracked here, together with two Critical Camel K issues published in September 2026.
Camel K (CVE-2026-80352, CVE-2026-80351; Critical; affects 2.0.0 before 2.9.3 and 2.10.0 before 2.10.2; fixed in 2.9.3, 2.10.2, 2.11.0). CVE-2026-80352 is a YAML injection through the Master trait serviceAccountName field (CWE-94) that lets an author of a Camel K custom resource cause arbitrary Kubernetes objects to be applied with the operator's privileges; NVD lists CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). CVE-2026-80351 is an eval-injection style flaw (improper neutralization of directives in dynamically evaluated Maven configuration) in which tenant-supplied repositories reach Maven execution inside the operator pod, potentially giving the tenant code execution with operator privileges.
Camel-JGroups (CVE-2026-88900): the JGroups consumer deserializes cluster messages without an ObjectInputFilter, so any serializable class on the classpath can be instantiated and its deserialization callbacks run. Exploitation needs network access to the cluster multicast group or UDP bind port plus a usable gadget chain on the classpath. Affects 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1. Mitigations: jdk.serialFilter JVM filter, JGroups AUTH plus SYM_ENCRYPT/ASYM_ENCRYPT via channelProperties, and keeping the cluster off untrusted networks. 4.23.0 requires at least one pre-deserialization control on consumers.
Camel-Spring-Redis (CVE-2026-78165; CWE-502): the default JdkSerializationRedisSerializer reads Redis payloads with no ObjectInputFilter, so anyone able to PUBLISH to a subscribed channel can reach remote code execution before route validation. Affects 2.11.0 before 4.18.5 and 4.19.0 before 4.22.1. Workarounds: -Djdk.serialFilter, a non-Java serializer such as StringRedisSerializer, and Redis authentication with restricted publish rights. The fix adds a deserializationFilter endpoint option that blocks java.net classes.
Camel-OAuth (CVE-2026-80312; CWE-287): the OAuth processors returned control to the route when authentication could not be completed, so failed-authentication requests were processed as successful (fail-open). Affects 4.11.0 before 4.18.5 and 4.19.0 before 4.22.1 (the advisory index lists 4.0.0 as the lower bound). Workaround: add an explicit authorization check after the OAuth processor.
Camel HTTP producers (CVE-2026-78164): property placeholders are resolved in the message-supplied CamelHttpUri and CamelRestHttpUri headers, so an unauthenticated sender can expand environment variables, system properties, cloud vault secrets (AWS, Azure, GCP) and invoke bean methods. Affects camel-http, camel-http-common, camel-vertx-http, camel-undertow and camel-netty-http. Workarounds: removeHeader on both headers at trust boundaries; skipControlHeaders=true (camel-http only); bridgeEndpoint=true is not a full mitigation. Sources disagree on the lower affected bound (4.0.0 vs 4.15.0); fixed in 4.18.5, 4.22.1, 4.23.0.
Camel-HTTP (CVE-2026-85251; CWE-200): with followRedirects=true the Authorization header (OAuth2 bearer tokens, basic and digest credentials) is re-attached to whatever host the Location header names, so a malicious or compromised remote endpoint can harvest credentials with a redirect. Affects 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1. Workaround: followRedirects=false.
Camel-Smooks (CVE-2026-88901; CWE-611): the Smooks data format and component parse the XML body with Smooks' default reader, which resolves external general and parameter entities and loads external DTDs, enabling local file reads and requests to internal hosts. Affects 4.7.0 before 4.18.5 and 4.19.0 before 4.22.1. The fix uses a hardened DocumentBuilder.
The sources reviewed (Apache Camel advisories, NVD for CVE-2026-80352, Openwall postings) do not report in-the-wild exploitation, public PoC code, threat actor activity or network IOCs. A partial read of the CISA KEV feed (first 100,000 characters) did not show any of these CVEs; the full feed was not checked. CVSS scores other than the NVD 9.8 for CVE-2026-80352 were not found; Apache rates the Camel K issues Critical and the rest High.
MITRE ATT&CK techniques used in TL-2026-4449
Collection
Execution
T1059 Command and Scripting Interpreter; T1610 Deploy Container
Initial Access
T1190 Exploit Public-Facing Application
Credential Access
T1528 Steal Application Access Token; T1552 Unsecured Credentials
Affected products and versions in Apache Camel Vulnerabilities Allow Remote Code Execution
- Apache Software Foundation — Apache Camel K
Vulnerable versions: 2.0.0 before 2.9.3; 2.10.0 before 2.10.2
Fixed in: 2.9.3; 2.10.2; 2.11.0 - Apache Software Foundation — Apache Camel (camel-jgroups, camel-spring-redis, camel-oauth, camel-http and HTTP-based components, camel-smooks)
Vulnerable versions: 4.0.0 before 4.18.5; 4.19.0 before 4.22.1; camel-spring-redis from 2.11.0; camel-oauth from 4.11.0; camel-smooks from 4.7.0
Fixed in: 4.18.5; 4.22.1; 4.23.0
Remediation for Apache Camel Vulnerabilities Allow Remote Code Execution
Patches
- Camel 4.18.5, 4.22.1, 4.23.0
- Camel K 2.9.3, 2.10.2, 2.11.0
Immediate actions
- Upgrade Apache Camel to 4.18.5, 4.22.1 or 4.23.0 and Camel K to 2.9.3, 2.10.2 or 2.11.0
- Restrict who can create Camel K custom resources and tenant Maven repositories until patched
- Strip CamelHttpUri and CamelRestHttpUri headers at trust boundaries
- Set followRedirects=false on camel-http endpoints that send credentials
Workarounds
- Use a non-Java serializer such as StringRedisSerializer for camel-spring-redis
- Set skipControlHeaders=true on camel-http (not available in other HTTP components)
- Add an explicit authentication check after the OAuth processor
Longer-term hardening
- Apply a JVM-wide deserialization filter (-Djdk.serialFilter) for Camel applications
- Secure JGroups channels with AUTH plus SYM_ENCRYPT or ASYM_ENCRYPT and keep clusters off untrusted networks
- Require authentication and restrict PUBLISH rights on Redis instances used by camel-spring-redis
- Avoid feeding untrusted XML to camel-smooks
- Add explicit authorization checks after OAuth processors in routes
CVEs associated with Apache Camel Vulnerabilities Allow Remote Code Execution
CVE-2026-80352, CVE-2026-80351, CVE-2026-88900, CVE-2026-78165, CVE-2026-80312, CVE-2026-78164, CVE-2026-85251, CVE-2026-88901
Weaknesses (CWE) in Apache Camel Vulnerabilities Allow Remote Code Execution
CWE-94, CWE-95, CWE-502, CWE-287, CWE-200, CWE-611, CWE-1336
Timeline of Apache Camel Vulnerabilities Allow Remote Code Execution
- Apache Camel publishes advisory CVE-2026-80352 (Camel K Master trait serviceAccountName YAML injection, CWE-94), credited to internal analysis; same fixed Camel K versions
- Apache Camel publishes advisory CVE-2026-80351 (Camel K tenant repositories reach Maven execution in the operator pod, CWE-95); fixed in Camel K 2.9.3, 2.10.2, 2.11.0
- CVE-2026-80352 (Camel K Master trait YAML injection, CVSS 9.8) published to NVD and announced on oss-security
- Apache Camel announces a batch of 38 security advisories fixed in Camel 4.18.5, 4.22.1 and 4.23.0, including the six High CVEs tracked here
- Advisories for CVE-2026-78165 (spring-redis deserialization), CVE-2026-80312 (OAuth fail-open), CVE-2026-78164 (HTTP placeholder injection), CVE-2026-85251 (redirect credential leak) and CVE-2026-88901 (Smooks XXE) published; three are credited to researchers and two to the Claude Security Scan Tool
- Camel advisory batch posted to the oss-security mailing list
- Advisory for CVE-2026-88900 (camel-jgroups unsafe deserialization leading to RCE, credited to h1ei1) published; Camel 4.23.0 consumers refuse to start without a pre-deserialization control
- GBHackers reports the eight Apache Camel vulnerabilities (RCE, authentication bypass, data theft)
Sources cited for Apache Camel Vulnerabilities Allow Remote Code Execution
- Apache Camel Vulnerabilities Allow Remote Code Execution, Authentication Bypass, and Data Theft
- Apache Camel Security Advisories
- CVE-2026-80352 Apache Camel K Master trait YAML injection
- CVE-2026-80351 Apache Camel K tenant repositories reach Maven execution
- CVE-2026-88900 Camel-JGroups unsafe deserialization
- CVE-2026-78165 Camel-Spring-Redis unsafe deserialization
- CVE-2026-80312 Camel-OAuth authentication bypass
- CVE-2026-78164 Camel HTTP producers property placeholder injection
- CVE-2026-85251 Camel-HTTP credential disclosure on redirect
- CVE-2026-88901 Camel-Smooks XXE
- NVD CVE-2026-80352
- oss-security: Apache Camel CVE-2026-80352
- oss-security: Apache Camel advisories batch
Detection coverage for TL-2026-4449
As of 2026-10-26, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-4449 across Splunk SPL, Microsoft KQL and Sigma, covering 6 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.