CVE-2026-63621

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.3 from GitHub Security Advisory published 2026-08-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component

The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode the HTTP-header path filters Camel-internal headers through KnativeHttpHeaderFilterStrategy, but in structured content mode (Content-Type application/cloudevents+json) the CloudEvent extension fields are read directly from the JSON body and every extension key is copied into the Exchange headers without applying any HeaderFilterStrategy (CloudEventProcessors, spec versions 1.0, 1.0.1 and 1.0.2). As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelHttpUri, CamelHttpPath, CamelFileName) via a structured-mode CloudEvent request, matched case-insensitively against Camel's header map. When a route forwards messages from a Knative consumer to a header-driven component such as camel-http or camel-file, the injected headers override configured values, enabling server-side request forgery (SSRF), path traversal or message-dispatch redirection depending on the route. This is an incomplete fix of the inbound header filtering previously added for the binary content-mode path, and is the same pattern addressed in camel-cxf/camel-knative (CVE-2026-47323), camel-undertow (CVE-2025-30177), the broader incoming-header filter (CVE-2025-27636 and CVE-2025-29891), and the non-HTTP strategies (CVE-2026-40453).

This issue affects Apache Camel: from 3.15.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.21.0.

Users are recommended to upgrade to version 4.22.0, which fixes the issue. If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.4. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.9. The non-LTS releases 4.15.0 through 4.17.0 and 4.19.0 through 4.21.0 are affected but do not receive a maintenance fix; users on those versions should upgrade to 4.18.4 or 4.22.0.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
46th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (1)

Auto-updated Aug 25, 2026
Patch available.
Web page

Apache Camel Security Advisory - CVE-2026-63621 - Apache Camel

https://camel.apache.org/security/CVE-2026-63621.html

Vendor Advisories for CVE-2026-63621(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcamel-knative2026-09-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.camel:camel-knative4.19.0, 4.20.0, 4.21.0
  • 3.15.0 up to 4.14.9: fixed in 4.14.9
  • 4.15.0 up to 4.18.4: fixed in 4.18.4
  • 4.19.0 up to 4.22.0: fixed in 4.22.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 60× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 102 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 2 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-12 15:29 UTCEG score recompute
  4. 2026-10-12 15:29 UTCVendor advisory
  5. 2026-10-11 19:33 UTCEG score recompute
  6. 2026-10-11 16:48 UTCEG score recompute
  7. 2026-10-11 14:10 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-10 12:38 UTCEG score recompute
  11. 2026-10-10 12:38 UTCVendor advisory
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-08 06:52 UTCEG score recompute
  15. 2026-10-08 06:52 UTCVendor advisory
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-10-07 04:51 UTCEG score recompute
  18. 2026-10-07 04:51 UTCVendor advisory
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-10-06 02:50 UTCEG score recompute
  21. 2026-10-06 02:50 UTCVendor advisory
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-10-04 20:42 UTCVendor advisory
  25. 2026-10-03 16:32 UTCEG score recompute
Show 75 more
  1. 2026-10-03 16:32 UTCVendor advisory
  2. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  4. 2026-10-02 11:13 UTCEG score recompute
  5. 2026-10-02 11:13 UTCVendor advisory
  6. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  7. 2026-10-01 09:11 UTCEG score recompute
  8. 2026-10-01 09:11 UTCVendor advisory
  9. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-09-30 07:11 UTCEG score recompute
  11. 2026-09-30 07:11 UTCVendor advisory
  12. 2026-09-29 04:38 UTCEG score recompute
  13. 2026-09-29 04:38 UTCVendor advisory
  14. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-09-28 02:37 UTCEG score recompute
  16. 2026-09-28 02:37 UTCVendor advisory
  17. 2026-09-27 00:37 UTCEG score recompute
  18. 2026-09-27 00:37 UTCVendor advisory
  19. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-09-25 11:47 UTCEG score recompute
  21. 2026-09-24 09:17 UTCEG score recompute
  22. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  23. 2026-09-23 07:17 UTCEG score recompute
  24. 2026-09-22 05:17 UTCEG score recompute
  25. 2026-09-21 03:16 UTCEG score recompute
  26. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  27. 2026-09-20 01:13 UTCEG score recompute
  28. 2026-09-18 23:12 UTCEG score recompute
  29. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  30. 2026-09-17 21:12 UTCEG score recompute
  31. 2026-09-16 15:42 UTCEG score recompute
  32. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  33. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  34. 2026-09-15 13:37 UTCEG score recompute
  35. 2026-09-14 11:37 UTCEG score recompute
  36. 2026-09-13 09:37 UTCEG score recompute
  37. 2026-09-12 07:36 UTCEG score recompute
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  39. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  40. 2026-09-11 05:33 UTCEG score recompute
  41. 2026-09-09 01:30 UTCEG score recompute
  42. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  43. 2026-09-07 18:39 UTCEG score recompute
  44. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  45. 2026-09-06 16:39 UTCEG score recompute
  46. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  47. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  48. 2026-09-05 14:38 UTCEG score recompute
  49. 2026-09-04 12:38 UTCEG score recompute
  50. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  51. 2026-09-03 10:38 UTCEG score recompute
  52. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  53. 2026-09-02 08:34 UTCEG score recompute
  54. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  55. 2026-09-01 06:30 UTCEG score recompute
  56. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  57. 2026-08-31 04:27 UTCEG score recompute
  58. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  59. 2026-08-30 02:26 UTCEG score recompute
  60. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  61. 2026-08-29 00:26 UTCEG score recompute
  62. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  63. 2026-08-27 20:20 UTCGHSA enrichmentGHSA-vvwm-3j43-7pfm · GitHub CVSS 5.3
  64. 2026-08-27 19:05 UTCEG score recompute
  65. 2026-08-27 19:04 UTCGHSA enrichmentGHSA-vvwm-3j43-7pfm · GitHub CVSS 5.3
  66. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  67. 2026-08-26 16:59 UTCEG score recompute
  68. 2026-08-26 16:59 UTCGHSA enrichmentGHSA-vvwm-3j43-7pfm · GitHub CVSS 5.3
  69. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  70. 2026-08-25 20:35 UTCGHSA enrichmentGHSA-vvwm-3j43-7pfm
  71. 2026-08-25 19:50 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  72. 2026-08-25 19:50 UTCGHSA enrichmentGHSA-vvwm-3j43-7pfm
  73. 2026-08-25 19:49 UTCMITRE cvelistV5CVSS v3 → 5.3 · severity → MEDIUM
  74. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  75. 2026-08-24 17:18 UTCNVD update

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-63621?
CVE-2026-63621 is a medium-severity vulnerability; its CVE record was published on August 24, 2026. Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode…
When was the CVE record for CVE-2026-63621 published?
The CVE record for CVE-2026-63621 was published on August 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-63621 actively exploited?
CVE-2026-63621 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63621?
CVE-2026-63621 has a CVSS v3.1 base score of 5.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-63621?
A fix for CVE-2026-63621 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63621 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63621

Explore →

Is Your Infrastructure Affected by CVE-2026-63621?

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

Book a Demo →Browse All CVEs