CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NMedium (5.3) in apache camel. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-jira 4.14.8, 4.18.3, 4.21.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:Norg.apache.camel:camel-jira (Maven): fixed in 4.14.8, 4.18.3, 4.21.0Explain CVE-2026-48206 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-48206?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-48206?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-48206 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel JIRA | from 4.0.0 before 4.14.8 |
| Apache Software Foundation Apache Camel JIRA | from 4.15.0 before 4.18.3 |
| Apache Software Foundation Apache Camel JIRA | from 4.19.0 before 4.21.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-64gv-6cq2-45jr | Maven | org.apache.camel:camel-jira | >=4.0.0 <4.14.8 | 4.14.8 |
| GHSA-64gv-6cq2-45jr | Maven | org.apache.camel:camel-jira | >=4.15.0 <4.18.3 | 4.18.3 |
| GHSA-64gv-6cq2-45jr | Maven | org.apache.camel:camel-jira | >=4.19.0 <4.21.0 | 4.21.0 |
Red Hat rates this Moderate.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-jira | Fix deferred | |
| Red Hat build of Apache Camel for Spring Boot 4 | camel-jira | Fix deferred | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | camel-jira | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-48206.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).