CVE-2026-84178
Received Received - Intake

Cross-Site Request Forgery in Apache Camel OAuth Component

Vulnerability report for CVE-2026-84178, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-19

Last updated on: 2026-10-19

Assigner: Apache Software Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-19
Last Modified
2026-10-19
Generated
2026-10-19
AI Q&A
2026-10-19
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
Apache Software Foundation Apache Camel 4.11.0
Apache Software Foundation Apache Camel 4.19.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Cross-Site Request Forgery (CSRF) vulnerability in Apache Camel's OAuth component. It affects versions from 4.11.0 before 4.18.5 and from 4.19.0 before 4.22.1. The issue occurs because the authorization callback does not verify a state parameter, allowing an attacker to silently sign in a victim as an identity they control. This can lead to actions and data submitted by the victim being redirected to the attacker's account.

Detection Guidance

Detecting this CSRF vulnerability requires checking Apache Camel OAuth component versions and verifying if the state parameter is properly handled in authorization callbacks. Inspect server logs for unusual login patterns or unauthorized redirects. No specific commands are provided in the context.

Impact Analysis

An attacker could exploit this to log in as you without your knowledge, perform actions on your behalf, or steal sensitive data you submit. It also allows open redirects from trusted origins, potentially leading to phishing attacks or further exploitation.

Compliance Impact

This vulnerability could lead to unauthorized access to user data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. It may result in non-compliance due to potential data breaches and unauthorized data exposure.

Mitigation Strategies

Upgrade Apache Camel to version 4.23.0 or apply the latest patches for your LTS stream (4.18.5 for 4.18.x or 4.22.1 for 4.22.x). If immediate upgrade is not possible, terminate the authorization code flow in a component that performs its own state binding.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-84178. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart