CVE-2025-30177

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 44% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Bypass/Injection vulnerability in Apache Camel in Camel-Undertow component under particular conditions.

This issue affects Apache Camel: from 4.10.0 before 4.10.3, from 4.8.0 before 4.8.6.

Users are recommended to upgrade to version 4.10.3 for 4.10.x LTS and 4.8.6 for 4.8.x LTS.

Camel undertow component is vulnerable to Camel message header injection, in particular the custom header filter strategy used by the component only filter the "out" direction, while it doesn't filter the "in" direction.

This allows an attacker to include Camel specific headers that for some Camel components can alter the behaviour such as the camel-bean component, or the camel-exec component.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
59.0%
KEV
Not listed

Published

April 1, 2025

Last Modified

April 15, 2025

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.camel:camel-undertow4.8.0 ... 4.8.5 (6 versions)4.8.6

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 22:29 UTCEPSS rescore
  2. 2026-07-13 06:12 UTCEPSS rescore
  3. 2026-07-13 06:12 UTCEPSS rescore
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:09 UTCEPSS rescore
  9. 2026-07-08 15:14 UTCEPSS rescore
  10. 2026-07-07 13:45 UTCEPSS rescore
  11. 2026-07-07 05:51 UTCOSV refresh
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 16:26 UTCEPSS rescore
  14. 2026-07-06 02:22 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 06:30 UTCEPSS rescore
  17. 2026-07-02 17:01 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 23:21 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 14:07 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-28 04:55 UTCEPSS rescore
Show 51 more
  1. 2026-06-27 03:08 UTCEPSS rescore
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-25 13:49 UTCEPSS rescore
  4. 2026-06-24 14:04 UTCEPSS rescore
  5. 2026-06-24 14:04 UTCEPSS rescore
  6. 2026-06-23 21:32 UTCEPSS rescore
  7. 2026-06-23 21:32 UTCEPSS rescore
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-19 19:25 UTCEPSS rescore
  15. 2026-06-19 19:25 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-18 17:05 UTCOSV refresh
  19. 2026-06-17 17:52 UTCEPSS rescore
  20. 2026-06-16 17:52 UTCEPSS rescore
  21. 2026-06-16 17:52 UTCEPSS rescore
  22. 2026-06-15 17:48 UTCEPSS rescore
  23. 2026-06-14 23:17 UTCEPSS rescore
  24. 2026-06-13 23:00 UTCEPSS rescore
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-12 23:11 UTCEPSS rescore
  27. 2026-06-11 13:59 UTCEPSS rescore
  28. 2026-06-10 22:18 UTCEPSS rescore
  29. 2026-06-10 13:22 UTCEPSS rescore
  30. 2026-06-08 14:16 UTCEPSS rescore
  31. 2026-06-08 14:16 UTCEPSS rescore
  32. 2026-06-07 15:24 UTCEPSS rescore
  33. 2026-06-07 15:24 UTCEPSS rescore
  34. 2026-06-06 13:47 UTCEPSS rescore
  35. 2026-06-06 13:47 UTCEPSS rescore
  36. 2026-06-05 22:46 UTCEPSS rescore
  37. 2026-06-05 22:46 UTCEPSS rescore
  38. 2026-06-05 06:10 UTCEPSS rescore
  39. 2026-06-05 06:10 UTCEPSS rescore
  40. 2026-06-04 13:12 UTCEPSS rescore
  41. 2026-06-04 13:11 UTCEPSS rescore
  42. 2026-06-02 20:12 UTCEPSS rescore
  43. 2026-06-01 13:51 UTCEPSS rescore
  44. 2026-06-01 13:51 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-30 08:29 UTCEG score recompute
  50. 2026-05-30 03:53 UTCOSV refresh
  51. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-30177?
CVE-2025-30177 is a medium vulnerability published on April 1, 2025. Bypass/Injection vulnerability in Apache Camel in Camel-Undertow component under particular conditions. This issue affects Apache Camel: from 4.10.0 before 4.10.3, from 4.8.0 before 4.8.6. Users are recommended to upgrade to version 4.10.3 for 4.10.x LTS and 4.8.6 for 4.8.x LTS. Camel undertow…
When was CVE-2025-30177 disclosed?
CVE-2025-30177 was first published in the National Vulnerability Database on April 1, 2025, with the most recent update on April 15, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-30177 actively exploited?
CVE-2025-30177 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 59.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-30177?
CVE-2025-30177 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2025-30177?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-30177, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-30177

Explore →

Is Your Infrastructure Affected by CVE-2025-30177?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.