Skip to content
VulniPulse
Advisory severityMedium6.1Apache Software Foundation

Medium [CVE-2026-84178] Cross-Site Request Forgery (CSRF) vulnerability in Apache Camel OAuth component

This medium-severity Apache Software Foundation advisory covers CVE-2026-84178 affecting Apache Camel OAuth.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-84178 Source published Source updated

VulniPulse record published Record updated

CVE-2026-84178
Affected products & platforms
Apache Software FoundationMessaging
Open source advisory

Get an email when Apache Software Foundation publishes the next one.

VulniPulse checks Apache Software Foundation's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.

Start your free month

Summary

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.

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.

Affected versions
  • 4.11.0 before 4.18.5
  • 4.19.0 before 4.22.1

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Fixed versions
  • 4.18.5
  • 4.22.1

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • 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.
  • 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.

Official advisory · high-confidence parse· fetched 9 days ago·verify at source

All Apache Software Foundation advisories

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.