Login CSRF via missing callback state binding
Published Oct 19, 2026 · Updated Oct 19, 2026
Login CSRF in Apache Camel's OAuth callback allows remote attackers to sign victims into attacker-controlled accounts via crafted callbacks. OAuthCodeFlowCallback redeems codes without checking session-bound state, associating an unrelated authorization flow with the presenting session. Deployments using this flow expose victims who follow a crafted callback to submitting data into the attacker's account; the callback also permits open redirects.
Summary
What happened
Login CSRF in Apache Camel's OAuth callback allows remote attackers to sign victims into attacker-controlled accounts via crafted callbacks. OAuthCodeFlowCallback redeems codes without checking session-bound state, associating an unrelated authorization flow with the presenting session. Deployments using this flow expose victims who follow a crafted callback to submitting data into the attacker's account; the callback also permits open redirects.
The record
- CVE
- CVE-2026-84178
- Published
- Oct 19, 2026
- Updated
- Oct 19, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Camel
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 2026CVE publishedPublication date reported by the CVE source.
- Oct 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.11.0 <4.18.5
- Affected versionversion=4.19.0 <4.22.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started