CamelApplication · Apache
CVE-2026-48206
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe camel-jira producer accepts operation parameters via Exchange headers using non-prefixed names (IssueKey, ProjectKey, IssueTransitionId, etc.). The HttpHeaderFilterStrategy only blocks Camel-prefixed headers at the HTTP boundary, allowing attackers to inject these headers via HTTP requests and override route-intended values. This enables unauthorized JIRA operations (issue deletion, transitions, creation, field modification) using the endpoint's service account credentials without authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CamelApplication
>= 4.0.0, < 4.14.8>= 4.15.0, < 4.18.3>= 4.19.0, < 4.21.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Camel versionCheck the Camel version in your project dependencies (pom.xml, build.gradle) or the camel-core JAR manifest. Run 'mvn dependency:tree | grep camel' or inspect the classpath for camel-core-*.jarAffected if The installed version is >= 4.0.0 and < 4.14.8, OR >= 4.15.0 and < 4.18.3, OR >= 4.19.0 and < 4.21.0
-
Locate jira: producer endpointsSearch route definitions for 'jira:' URI scheme (such as 'jira:createIssue' or 'jira:transitionIssue'). Inspect your RouteBuilder or XML route configuration files.Affected if Your routes contain a jira: producer endpoint
-
Determine if jira: routes are exposed via HTTPInspect your Camel context configuration to see if HTTP transports (servlet, jetty, undertow, spark-java, rest-dsl) expose routes that include jira: producers. Check if an HTTP ingress path routes to a route containing a jira: endpoint.Affected if Untrusted HTTP requests can reach a route containing a jira: producer endpoint
-
Verify header filtering configurationInspect your HttpHeaderFilterStrategy bean configuration. Look for the 'filterHeaders' or 'restrictedHeaders' settings. Check if JIRA operation headers (IssueKey, ProjectKey, IssueTransitionId, IssueType, Summary, Description, etc.) are explicitly filtered before the jira: producer.Affected if HttpHeaderFilterStrategy does not filter JIRA-specific headers (IssueKey, ProjectKey, etc.) from incoming HTTP requests
-
Check for injected JIRA headers in HTTP trafficReview HTTP access logs or enable debug logging on the camel-http or servlet endpoint to inspect incoming request headers. Look for headers named IssueKey, ProjectKey, IssueTransitionId, or other JIRA operation parameters.Affected if HTTP requests to Camel routes contain unfiltered JIRA operation headers
You are affected if your Apache Camel version is within the vulnerable ranges AND a jira: producer endpoint is exposed to untrusted HTTP traffic without explicit filtering of JIRA operation headers (IssueKey, ProjectKey, IssueTransitionId, etc.).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.14.84.18.34.21.0
Upgrade to Apache Camel 4.21.0 (or 4.14.8/4.18.3 for LTS streams) and update routes to use CamelJira-prefixed headers (CamelJiraIssueKey, etc.). Alternatively, strip JIRA control headers from untrusted ingress before the jira: producer.
4.21.0 (or 4.14.8 LTS, or 4.18.3 depending on release stream)
- Upgrade to Apache Camel 4.21.0 for the latest release, or 4.14.8 for LTS, or 4.18.3 depending on your release stream
- After upgrading, update any routes that use raw header names (IssueKey, ProjectKey, IssueTransitionId, etc.) to use the Camel-prefixed names (CamelJiraIssueKey, CamelJiraProjectKey, CamelJiraIssueTransitionId, etc.)
- Test that JIRA operations function correctly with the new header naming convention
- For deployments that cannot upgrade immediately, add a processor at the start of routes that bridge HTTP to the jira: producer to strip the control headers (IssueKey, ProjectKey, IssueTransitionId, Summary, Type, Assignee, Components, Watchers, LinkType, WorkLogMinutes, etc.) from incoming HTTP requests before they reach the jira: producer
- Alternatively, set JIRA operation parameters from a trusted source (hardcoded values, route configuration, or a trusted internal service) rather than from inbound HTTP headers
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Camel
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48206 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-48206 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data