4.8

CVE-2025-29891: apache software foundation apache camel

CVSS: 4.8v3.1MediumAnalyzed
AliasesGHSA-96v5-c2h5-56hm
Published 12-03-2025Last modified 19-03-2025

Vulnerability summary

CVE-2025-29891 is a medium (CVSS 4.8) vulnerability in apache software foundation apache camel. EPSS estimates a 76.09% chance of exploitation in the next 30 days, higher than 99.5% of scored vulnerabilities. 1 public exploit is recorded.

Overall risk
44/100
0100
Medium · default modelHow is this calculated?
CVSS score
4.8/10
010
Medium · v3.1 (CVE.org)
EPSS score
76.09%
0%100%
Critical · +2.64 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits1github

Timeline

  1. 12-03-2025
    PublishedVulnerability first disclosed.
  2. 19-03-2025
    Last modifiedVulnerability information updated.

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.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

76.09%

Chance of exploitation in the next 30 days

Percentile

100%

Versus all other CVEs

30-day change

+2.64 pp

From 73.45% on 18-09-2026

18-09-202618-10-2026
EPSS score
76.09%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

1 found
  • githubUnverified

    Cve 2025 27636 Apache Camel Poc

    Maturity: poc

Weaknesses

CWE · root cause

Affected systems

Apache1 product
  • camel≥ 3.10.0, < 3.22.4 | ≥ 4.8.0, < 4.8.5 | ≥ 4.10.0, < 4.10.2
Apache software foundation1 product
  • apache camel≥ 4.10.0, < 4.10.2 | ≥ 4.8.0, < 4.8.5 | ≥ 3.10.0, < 3.22.4
Org.apache.camel1 product
  • camel-support≥ 3.10.0, < 3.22.4 | ≥ 4.9.0, < 4.10.2 | ≥ 4.0.0-M1, < 4.8.5

3 vendors · 3 products

References

8 links