On this page
CVE Details
- Protection status: Protected by Atomicorp rules · About protection statuses
- CVE: CVE-2026-84178
- Name: Apache Camel: Camel-OAuth Login Cross-Site Request Forgery via Missing State Binding in the Authorization Code Flow
- Severity: Medium
- CVSS: 6.1 (v3.1) (Medium)
- CVSS version: 3.1
- CVSS source: apache CNA
- CVSS vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: Required
- Scope: Changed
- Confidentiality impact: Low
- Integrity impact: Low
- Availability impact: None
- CWE: CWE-352 — Cross-Site Request Forgery
- Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-111 (opens in a new tab) , CAPEC-462 (opens in a new tab) , CAPEC-467 (opens in a new tab) , CAPEC-62 (opens in a new tab)
- Vendor: Apache Software Foundation
- Vulnerable product: Apache Camel
- CVE published: 2026-10-19
- CVE last modified: 2026-10-19
- EPSS: 0.0018; 7.9th percentile as of 2026-11-20 (FIRST (opens in a new tab) )
- Latest Update: 2026-11-10
- Selected Rule IDs observed: 344365
- Matching rules: 1; rules with blocking actions: 1
- Would-block Rule IDs: 344365
- Request surfaces inspected: JSON request data, Request URI, Request argument names, Request arguments, Request headers, SOAP request data
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data
CVSS assessments
CVSS v3.1 · security@apache.org
- Base score: 6.1
- Base severity: MEDIUM
- Exploitability subscore: 2.8
- Impact subscore: 2.7
- Assessment type: Secondary
- Source identifier: security@apache.org
- Full vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Attack vector: Network
- Attack complexity: Low
- Privileges required: None
- User interaction: Required
- Scope: Changed
- Confidentiality impact: Low
- Integrity impact: Low
- Availability impact: None
- Exploit maturity: Not scored
Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.
Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)
CISA SSVC assessments
These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.
- Provider: CISA ADP
- Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC version: 2.0.3
- Role: CISA Coordinator
- Assessment timestamp: 2026-10-19T18:39:52.682056Z
- Exploitation: none
- Automatable: no
- Technical Impact: partial
- Source: CISA ADP in the CVE record (opens in a new tab)
Vulnerable CPE configurations
No vulnerable CPE configurations are supplied in the current NVD record. See the affected-product information and vendor guidance on this page.
Vulnerability Description
Cross-Site Request Forgery (CSRF) vulnerability in Apache Camel OAuth component.
This issue affects Apache Camel: from 4.11.0 before 4.18.5, from 4.19.0 before 4.22.1.
The authorization code callback did not carry a state parameter binding it to the authorization request that started the flow, and the callback did not verify one. An authorization code obtained in any browser could therefore be redeemed at the callback and associated with whichever session presented it, which is login cross-site request forgery: a victim can be silently signed in as an identity the attacker controls, so that actions the victim then performs, and data they then submit, land in the attacker’s account. The same unvalidated callback handling also allowed the post-authentication redirect target to be influenced, giving an open redirect from a trusted origin. The state check runs before the authorization code is redeemed, so these paths are reachable without any interaction with the identity provider.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The authorization request now issues a state value bound to the session, and the callback rejects a request whose state is absent or does not match, stopping the route with a 400 response. For deployments that cannot upgrade immediately, terminate the authorization code flow in a component that performs its own state binding rather than relying on the Camel callback. Note that after upgrading, a deployment behind a proxy that drops or rewrites the callback query string will begin to see 400 responses, because the state parameter must survive the round trip.
Recommended Actions
Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (344365 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.
Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.
- Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.18.5.
- Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.22.1.
- Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.18.5 or later.
- Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.22.1 or later.
- CNA guidance source: apache (opens in a new tab)
- Vendor recommendation: Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The authorization request now issues a state value bound to the session, and the callback rejects a request whose state is absent or does not match, stopping the route with a 400 response.
- Vendor workaround: For deployments that cannot upgrade immediately, terminate the authorization code flow in a component that performs its own state binding rather than relying on the Camel callback. Note that after upgrading, a deployment behind a proxy that drops or rewrites the callback query string will begin to see 400 responses, because the state parameter must survive the round trip.
Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.
Research Notes
Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.
Public Vulnerability References
- NVD (opens in a new tab)
- CVE Record (opens in a new tab)
- CVE authority reference: https://camel.apache.org/security/CVE-2026-84178.html (opens in a new tab)
- CVE authority reference: https://github.com/apache/camel/pull/25821 (opens in a new tab)
- CVE authority reference: https://github.com/apache/camel/pull/25944 (opens in a new tab)
- CVE authority reference: https://github.com/apache/camel/pull/25946 (opens in a new tab)
- CVE authority reference: https://issues.apache.org/jira/browse/CAMEL-24437 (opens in a new tab)
Test or Research Source
- Source: Atomicorp AI Research Framework
- Tags: cve, derived, redirect, waf-probe
Research Note Context
This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.
Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.
Learn More
Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.
Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:
- Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
- Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
- Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
- Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
- Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.
For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .