Skip to main content
VulnerabilityPublished

CVE-2026-48206: Apache Camel JIRA · Improper Input Validation

Affects Apache Camel JIRASource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium · fixed in 4.21.0 : update Apache Camel JIRA when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.21.0, 4.18.3, 4.14.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Apache Camel JIRA and org.apache.camel/camel-jira to 4.21.0, 4.18.3 or 4.14.8.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Camel JIRAAffected
  • >=4.19.0 <4.21.0
Fixed in
  • 4.21.0
Apache Software FoundationApache Camel JIRAAffected
  • >=4.15.0 <4.18.3
Fixed in
  • 4.18.3
Apache Software FoundationApache Camel JIRAAffected
  • >=4.0.0 <4.14.8
Fixed in
  • 4.14.8
Mavenorg.apache.camel/camel-jirapkg:maven/org.apache.camel/camel-jiraOther threatsAffected
  • =4.0.0
  • >=4.0.0 <4.14.8
  • =4.15.0
  • >=4.15.0 <4.18.3
  • =4.19.0
  • >=4.19.0 <4.21.0
Fixed in
  • 4.14.8
  • 4.18.3
  • 4.21.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Apache Camel versions 4.14.8, 4.18.3, and 4.21.0. Users should upgrade to one of these versions according to their release stream. After upgrading, routes must use Camel-prefixed header names (e.g., CamelJiraIssueKey) instead of the old plain header names. For deployments unable to upgrade immediately, it is recommended to strip camel-jira control headers (such as IssueKey, ProjectKey, IssueTransitionId) from any untrusted ingress before the jira: producer and set required parameters from trusted sources.

Description

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.

References

Community reviews

Loading reviews…