CVE-2026-48206

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-07-06. 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
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, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel JIRA component.

The camel-jira producers read their operation parameters - the issue key, project key, transition id, summary, type, assignee, components, watchers, link type, work-log minutes and others - from Exchange message headers. The header constants defined in JiraConstants (for example ISSUE_KEY = IssueKey, ISSUE_PROJECT_KEY = ProjectKey, ISSUE_TRANSITION_ID = IssueTransitionId, LINK_TYPE = linkType) used plain, non-Camel-prefixed values. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks only the Camel header namespace on the HTTP boundary - let them pass from an inbound HTTP request straight into the Exchange. In a route that bridges an HTTP consumer (for example platform-http) into a jira: producer, any HTTP client could therefore supply these headers and override the values the route intended, driving JIRA operations against the configured JIRA instance with the endpoint's configured service-account credentials - for example deleting or transitioning an arbitrary issue (via IssueKey / IssueTransitionId), creating an issue in a different project (via ProjectKey), modifying issue fields, adding or removing watchers, or logging work. The operations are bounded by what the configured service account is permitted to do. No credentials are required from the attacker when the bridging consumer is unauthenticated. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.

Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, routes that drive JIRA operations via the raw header names must use the CamelJira* names (for example CamelJiraIssueKey) instead of the old values. For deployments that cannot upgrade immediately, strip the camel-jira control headers from any untrusted ingress before the jira: producer (for example removing the IssueKey, ProjectKey, IssueTransitionId and related headers at the start of the route), and set the required JIRA operation parameters from a trusted source.

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.5% × 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
44th
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

July 6, 2026

Last Modified

July 8, 2026

Advisory Details (2)

Auto-updated Jul 8, 2026
Patch available.
Web page

oss-security - CVE-2026-48206: Apache Camel: Camel-JIRA: A set of non-Camel-prefixed Exchange header constants (IssueKey, ProjectKey, IssueTransitionId, ...) bypass the HTTP header filter, allowing an HTTP client to drive arbitrary JIRA issue operations using the endpoint's configured credentials

http://www.openwall.com/lists/oss-security/2026/07/05/20
Web page

Apache Camel Security Advisory - CVE-2026-48206 - Apache Camel

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

Vendor Advisories for CVE-2026-48206(1)

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

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.camel:camel-jira4.19.0, 4.20.0
  • 4.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.21.0: fixed in 4.21.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 28× 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 165 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 65 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

1 shown

Maven:org.apache.camel:camel-jira

Frequently asked(5)

What is CVE-2026-48206?
CVE-2026-48206 is a medium-severity vulnerability; its CVE record was published on July 6, 2026. Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel JIRA component. The camel-jira producers read their operation parameters - the issue key, project key, transition id, summary, type, assignee, components, watchers, link type, work-log minutes…
When was the CVE record for CVE-2026-48206 published?
The CVE record for CVE-2026-48206 was published on July 6, 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 July 8, 2026; the record at its source may have been updated since.
Is CVE-2026-48206 actively exploited?
CVE-2026-48206 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48206?
CVE-2026-48206 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-48206?
A fix for CVE-2026-48206 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48206 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-48206

Explore →

Is Your Infrastructure Affected by CVE-2026-48206?

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

Book a Demo →Browse All CVEs