Vulnerabilities in pkg:maven/org.apache.camel/camel-jira

PACKAGE
Advisory Identifier: GHSA-64gv-6cq2-45jr
Advisory Summary

CVE-2026-48206 is a MODERATE (CVSS 5.3) a set of non-camel-prefixed exchange vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Apache Camel-JIRA libraries in the Maven ecosystem. The issue involves a set of non-camel-prefixed exchange header constants bypass the http header filter. Remediation is available by upgrading affected packages to version 4.14.8, 4.18.3, 4.21.0.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:maven/org.apache.camel/camel-jira

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:maven/org.apache.camel/camel-jira. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-64gv-6cq2-45jr CVE-2026-48206 MODERATE Apache Camel-JIRA: A set of non-Camel-prefixed Exchange header constants bypass the HTTP header filter
GHSA-6g2w-257v-3c9f CVE-2023-34442 LOW Apache Camel information exposure vulnerability

CVE-2026-48206 at a Glance

CVE Identifier CVE-2026-48206
GHSA Identifier GHSA-64gv-6cq2-45jr
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Apache Camel-JIRA
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-48206

To remediate this vulnerability, upgrade all affected Apache Camel-JIRA dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.apache.camel:camel-jira fixed: 4.14.8
<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-jira</artifactId>
    <version>4.14.8</version>
</dependency>
org.apache.camel:camel-jira fixed: 4.18.3
<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-jira</artifactId>
    <version>4.18.3</version>
</dependency>
org.apache.camel:camel-jira fixed: 4.21.0
<dependency>
    <groupId>org.apache.camel</groupId>
    <artifactId>camel-jira</artifactId>
    <version>4.21.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.apache.camel

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-48206, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.apache.camel

Analyze the terminal output to locate any version of Apache Camel-JIRA in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.14.8), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.apache.camel command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. In Apache Camel-JIRA, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2026-48206 Affected Apache Camel-JIRA Versions

3 component(s)
Fixed Versions:
4.14.84.18.34.21.0
Product / Package Ecosystem Affected Versions Fixed Version
org.apache.camel:camel-jira
Maven
≥ 4.0.0
< 4.14.8
4.14.8
org.apache.camel:camel-jira
Maven
≥ 4.15.0
< 4.18.3
4.18.3
org.apache.camel:camel-jira
Maven
≥ 4.19.0
< 4.21.0
4.21.0

References

Frequently Asked Questions

What is CVE-2026-48206?
CVE-2026-48206 is a security vulnerability in Apache Camel-JIRA involving A set of non-Camel-prefixed Exchange header constants bypass the HTTP header filter under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Apache Camel-JIRA versions are affected?
Affected versions include releases prior to 4.14.8, 4.18.3, 4.21.0 across affected packages: org.apache.camel:camel-jira.
What version fixes CVE-2026-48206?
Upgrading to 4.14.8, 4.18.3, 4.21.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is camel-jira affected?
Yes, org.apache.camel:camel-jira is affected in releases prior to 4.14.8, 4.18.3, 4.21.0. Upgrade your dependency to 4.14.8, 4.18.3, 4.21.0 or later.
What is the CVSS score of CVE-2026-48206?
CVE-2026-48206 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2026-48206?
CVE-2026-48206 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Maven dependencies for CVE-2026-48206?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.apache.camel'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-64gv-6cq2-45jr",
  "modified" : "2026-08-28T19:33:21Z",
  "published" : "2026-07-06T09:30:30Z",
  "aliases" : [ "CVE-2026-48206" ],
  "summary" : "Apache Camel-JIRA: A set of non-Camel-prefixed Exchange header constants bypass the HTTP header filter",
  "details" : "Improper Input Validation, Authorization Bypass Through User-Controlled Key vulnerability in Apache Camel JIRA component.\n\nThe 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.\nThis 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.\n\nUsers 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.camel:camel-jira"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.14.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.camel:camel-jira"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.15.0"
      }, {
        "fixed" : "4.18.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.apache.camel:camel-jira"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.19.0"
      }, {
        "fixed" : "4.21.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48206"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/23417"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/23460"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/pull/23472"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/commit/024704f95f16d1260304054088fa0b34acb57ebf"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/commit/3240a174a3707ba2b1d893c4ac0880829e0c9233"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/commit/6863ea624605ab3fa8827c43a4c5df333f767dc4"
  }, {
    "type" : "WEB",
    "url" : "https://camel.apache.org/security/CVE-2026-48206.html"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/apache/camel"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/releases/tag/camel-4.14.8"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/releases/tag/camel-4.18.3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/camel/releases/tag/camel-4.21.0"
  }, {
    "type" : "WEB",
    "url" : "https://issues.apache.org/jira/browse/CAMEL-23576"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2026/07/05/20"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20", "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-28T19:33:21Z",
    "nvd_published_at" : "2026-07-06T09:16:38Z"
  }
}