CVE-2026-48206: CWE-20 Improper Input Validation in Apache Software Foundation Apache Camel JIRA
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.
AI Analysis
Technical Summary
The Apache Camel JIRA component reads operation parameters from Exchange message headers using plain, non-Camel-prefixed header names (e.g., IssueKey, ProjectKey). These headers are not blocked by the HttpHeaderFilterStrategy on the HTTP boundary, allowing an attacker to supply these headers via an unauthenticated HTTP consumer route. This enables the attacker to override intended JIRA operation parameters and perform actions with the service account's permissions without needing credentials. The issue affects Apache Camel versions from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, and from 4.19.0 before 4.21.0. The vulnerability is fixed in versions 4.14.8, 4.18.3, and 4.21.0 respectively. Mitigation includes upgrading to these versions and changing routes to use Camel-prefixed header names or stripping untrusted headers before the jira: producer.
Potential Impact
An attacker can perform unauthorized JIRA operations such as deleting or transitioning issues, creating issues in arbitrary projects, modifying issue fields, adding or removing watchers, or logging work. These actions are performed with the permissions of the configured service account and do not require attacker credentials if the HTTP consumer route is unauthenticated. The impact is limited by the permissions of the service account configured in the Camel JIRA endpoint.
Mitigation Recommendations
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.
CVE-2026-48206: CWE-20 Improper Input Validation in Apache Software Foundation Apache Camel JIRA
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.
CVSS v3.1
Score 5.3medium
Affected software
pkg:maven/org.apache.camel/camel-jiraRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Apache Camel JIRA component reads operation parameters from Exchange message headers using plain, non-Camel-prefixed header names (e.g., IssueKey, ProjectKey). These headers are not blocked by the HttpHeaderFilterStrategy on the HTTP boundary, allowing an attacker to supply these headers via an unauthenticated HTTP consumer route. This enables the attacker to override intended JIRA operation parameters and perform actions with the service account's permissions without needing credentials. The issue affects Apache Camel versions from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, and from 4.19.0 before 4.21.0. The vulnerability is fixed in versions 4.14.8, 4.18.3, and 4.21.0 respectively. Mitigation includes upgrading to these versions and changing routes to use Camel-prefixed header names or stripping untrusted headers before the jira: producer.
Potential Impact
An attacker can perform unauthorized JIRA operations such as deleting or transitioning issues, creating issues in arbitrary projects, modifying issue fields, adding or removing watchers, or logging work. These actions are performed with the permissions of the configured service account and do not require attacker credentials if the HTTP consumer route is unauthenticated. The impact is limited by the permissions of the service account configured in the Camel JIRA endpoint.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-21T09:02:10.464Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4b6cae27e9c7971925237c
Added to database: 07/06/2026, 08:51:58 UTC
Last enriched: 07/06/2026, 09:07:48 UTC
Last updated: 07/06/2026, 23:08:03 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.