CVE-2026-48206
Description
A flaw was found in the Apache Camel JIRA component. Due to improper input validation, non-Camel-prefixed Exchange header constants can bypass the HTTP header filter. This allows a remote attacker, potentially unauthenticated, to supply specific headers and override intended values. Consequently, the attacker can perform unauthorized JIRA operations, such as deleting or transitioning issues, creating issues in different projects, or modifying issue fields, limited by the configured service account's permissions.
Statement
When an Apache Camel route bridges an HTTP consumer to a JIRA producer, an unauthenticated client can bypass header filtering. This allows the client to manipulate JIRA issue operations by supplying specific non-Camel-prefixed headers, potentially leading to unauthorized actions within the bounds of the configured JIRA service account's permissions.
Mitigation
To mitigate this issue, configure routes that bridge an HTTP consumer to a JIRA producer to strip all non-Camel-prefixed JIRA control headers (e.g., IssueKey, ProjectKey, IssueTransitionId) from untrusted ingress before they reach the JIRA producer. Ensure that required JIRA operation parameters are set from a trusted source within the route.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | None | N/A | None |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism
Access control checks for specific user data or functionality can be bypassed.
Access Control
Technical Impact: Gain Privileges or Assume Identity
Horizontal escalation of privilege is possible (one user can view/modify information of another user).
Access Control
Technical Impact: Gain Privileges or Assume Identity
Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
