Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2025-29891: Apache Camel: Camel Message Header Injection through request parameters

MediumCVSS 4.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 42/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 76% (FIRST EPSS); higher than 99.5% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Apache Software Foundation Apache Camel 3.22.4, 4.10.2, 4.8.5.

Add it to your regular patch cycle. Upgrade to Apache Software Foundation Apache Camel 3.22.4, 4.10.2, 4.8.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Mar 12, 2025
Updated
Jun 17, 2026
EPSS
76.0% · 99th percentile

Report tools

JSON

Action score

42

Plan

Add it to your regular patch cycle.

CVSS
19 / 40 · 4.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
23 / 30 · 76.0%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-29891

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachecamel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Camel

    • 4.10.0 and later · before 4.10.2affected · semver
    • 4.8.0 and later · before 4.8.5affected · semver
    • 3.10.0 and later · before 3.22.4affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache camel3.10.0 and later · before 3.22.4
  • apache camel4.8.0 and later · before 4.8.5
  • apache camel4.10.0 and later · before 4.10.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.apache.camel:camel-supportfrom 3.10.0 · before 3.22.43.22.4
Mavenorg.apache.camel:camel-supportfrom 4.0.0-M1 · before 4.8.54.8.5
Mavenorg.apache.camel:camel-supportfrom 4.9.0 · before 4.10.24.10.2

Other highest-scoring records for the same primary product.

  • CVE-2025-27636Apache Camel: Camel Message Header Injection via Improper Filtering
    51Plan
  • CVE-2026-47323Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering
    45Plan
  • CVE-2026-33453Apache Camel: CoAP URI Query Parameter to Exchange Header Injection in camel-coap Allows Single-Packet Pre-Auth Remote Code Execution
    43Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-23114Feb 20, 2024 · Apache Camel: Camel-CassandraQL: Unsafe Deserialization from CassandraAggregationRepository
    39Monitor
  • ← EarlierCVE-2024-22371Feb 26, 2024 · Apache Camel issue on ExchangeCreatedEvent
    30Monitor
  • Later →CVE-2025-30177Apr 1, 2025 · Apache Camel: Camel-Undertow Message Header Injection via Improper Filtering
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Apache Software Foundation Apache Camel3.22.4Vendor (CNA)
Apache Software Foundation Apache Camel4.10.2Vendor (CNA)
Apache Software Foundation Apache Camel4.8.5Vendor (CNA)
Maven:org.apache.camel:camel-support3.22.4Package registry (OSV)
Maven:org.apache.camel:camel-support4.10.2Package registry (OSV)
Maven:org.apache.camel:camel-support4.8.5Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-3017720 days apartApache Camel: Camel-Undertow Message Header Injection via Improper Filtering
    26Monitor

Not on record for this CVE: patch commit or PR link · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
Low
Availability impact
Low

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records