# CVE-2026-48206: Apache Camel-JIRA: A set of non-Camel-prefixed Exchange header constants bypass the HTTP header filter > Attackers can bypass HTTP header filters to manipulate JIRA operations via unauthenticated HTTP requests in Apache Camel routes. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jul 2026 - **Updated:** 6 Jul 2026 - **Also known as:** GHSA-64gv-6cq2-45jr ## What is CVE-2026-48206? CVE-2026-48206 is a medium-severity missing authorization vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2026-48206? 6 open source packages ship an affected version, including org.apache.camel:camel-jira. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-jira` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-jira` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-jira` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-jira` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-jira` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-jira` | Maven | From 4.19.0 | 4.21.0 | Products: Apache Camel. ## How do I fix CVE-2026-48206? Upgrade org.apache.camel:camel-jira to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0. ## Is CVE-2026-48206 being exploited? There is no known exploitation of CVE-2026-48206 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-48206: Apache Camel camel-jira IssueKey (and other non-Camel-prefixed) header injection driving arbitrary JIRA issue operations with the endpoint's service-account credentials (fixed in 4.14.8/4.18.3/4.21.0) (github_poc): https://github.com/oscerd/CVE-2026-48206 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-48206 and fix it if it is affected. What it is: CVE-2026-48206 is a medium-severity missing authorization vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-48206 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-jira (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-jira (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-jira (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-jira (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-jira (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-jira (Maven): affected from 4.19.0; fixed in 4.21.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-48206/ (Markdown: https://insights.sbomify.com/CVE-2026-48206/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48206 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48206 - OSV: https://osv.dev/vulnerability/CVE-2026-48206 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-48206/ Summaries are generated and may contain mistakes; the official description above is the record.