Skip to content
Vulnerability Intelligence

CVE-2025-29891

MediumExploitedPublic exploit

Apache Camel Message Header Injection through request parameters

Published Mar 12, 2025 · Updated Oct 8, 2026 · Also known as GHSA-96v5-c2h5-56hm

Key Facts

Patch immediately
  • CVE-2025-29891 is a medium-severity vulnerability (CVSS 4.8 v3.1) affecting Camel (Apache), org.apache.camel:camel-support (maven), org.apache.camel:camel.
  • It is exploited in the wild, listed in Industry KEV feed since Jul 3, 2025. Public exploit code is available.
  • EPSS estimates a 76% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Camel 3.22.4, org.apache.camel:camel 3.22.4, org.apache.camel:camel 4.10.2.
  • Brandefense priority: patch immediately, because it is listed as exploited in the wild.

CVSS v3.1

4.8

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

EPSS (30-day exploit likelihood)

76%

Higher than 99.5% of all scored CVEs

Exploited in the wild

Yes

1 catalog listing

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2025-29891 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

Bypass/Injection vulnerability in Apache Camel.

This issue affects Apache Camel: from 4.10.0 before 4.10.2, from 4.8.0 before 4.8.5, from 3.10.0 before 3.22.4.

Users are recommended to upgrade to version 4.10.2 for 4.10.x LTS, 4.8.5 for 4.8.x LTS and 3.22.4 for 3.x releases.

This vulnerability is present in Camel's default incoming header filter, that allows an attacker to include Camel specific headers that for some Camel components can alter the behaviours such as the camel-bean component, or the camel-exec component.

If you have Camel applications that are directly connected to the internet via HTTP, then an attacker could include parameters in the HTTP requests that are sent to the Camel application that get translated into headers.

The headers could be both provided as request parameters for an HTTP methods invocation or as part of the payload of the HTTP methods invocation.

All the known Camel HTTP component such as camel-servlet, camel-jetty, camel-undertow, camel-platform-http, and camel-netty-http would be vulnerable out of the box.

This CVE is related to the CVE-2025-27636: while they have the same root cause and are fixed with the same fix, CVE-2025-27636 was assumed to only be exploitable if an attacker could add malicious HTTP headers, while we have now determined that it is also exploitable via HTTP parameters. Like in CVE-2025-27636, exploitation is only possible if the Camel route uses particular vulnerable components.

Known-Exploited Catalog Listings

CatalogAddedRemediation dueRansomware use
Industry KEV feedJul 3, 2025n/aNot reported

Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Affected Products

3 affected entries in total
ProductAffected versionsFixed in
CamelApacheSee advisory3.22.4
org.apache.camel:camel-supportmaven>= 3.10.04.8.5
org.apache.camel:camel>= 4.10.04.10.2

Patched Releases

Camel

3.22.4

org.apache.camel:camel

3.22.4, 4.10.2, 4.8.5

org.apache.camel:camel-support

3.22.4, 4.10.2, 4.8.5

Timeline

  1. Publicly disclosed

    Mar 12, 2025

  2. Added to Industry KEV feed

    Jul 3, 2025

  3. Last updated

    Oct 8, 2026

Weakness Type

  • CWE-164 Improper Neutralization of Internal Special Elements

References

7 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2025-29891 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.

Request A Demo