cve.bz

CVE-2026-48206 apache camel: Improper Input Validation

5.3 mediumEPSS 0.6%Fix available

Medium (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.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Badge for a README or a site

CVE-2026-48206

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-48206](https://cve.bz/cve/badge/CVE-2026-48206.svg)](https://cve.bz/cve/CVE-2026-48206)

HTML:

<a href="https://cve.bz/cve/CVE-2026-48206"><img src="https://cve.bz/cve/badge/CVE-2026-48206.svg" alt="CVE-2026-48206"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camel JIRAfrom 4.0.0 before 4.14.8
Apache Software Foundation Apache Camel JIRAfrom 4.15.0 before 4.18.3
Apache Software Foundation Apache Camel JIRAfrom 4.19.0 before 4.21.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-64gv-6cq2-45jrMavenorg.apache.camel:camel-jira>=4.0.0 <4.14.84.14.8
GHSA-64gv-6cq2-45jrMavenorg.apache.camel:camel-jira>=4.15.0 <4.18.34.18.3
GHSA-64gv-6cq2-45jrMavenorg.apache.camel:camel-jira>=4.19.0 <4.21.04.21.0

Red Hat

Red Hat rates this Moderate.

Red Hat's 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.

Red Hat's 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.

ProductPackageStateAdvisory
Red Hat build of Apache Camel 4 for Quarkus 3camel-jiraFix deferred
Red Hat build of Apache Camel for Spring Boot 4camel-jiraFix deferred
Red Hat JBoss Enterprise Application Platform Expansion Packcamel-jiraFix 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.

GitHub PoC

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.

  • oscerd/CVE-2026-48206 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-48206: Apache Camel camel-jira IssueKey (and other non-Camel-prefixed) header injection driving arbitrary JIRA issu…

Attack patterns (CAPEC)

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).

References

Check your stackJSON