Skip to content
VulniPulse
Sign in
Medium 2 vendors · 2 advisories

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

CVE-2026-84178 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Medium
CVSS base score
6.1 (Apache), 6.1 (Red Hat)
Weakness
CWE-358
Fixed releases
  • Apache: 4.18.5, 4.22.1
  • Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
Vendor advisories
2 from Apache, Red Hat
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-84178; each belongs to its advisory, not to every product listed. How records are collected and checked.

How do I fix CVE-2026-84178?

Upgrade to a fixed release named by the vendor:

  • Apache: 4.18.5, 4.22.1
  • Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
  • Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
  • Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. (Apache)

Vendor advisories for CVE-2026-84178

Apache

1 advisory
  • Advisory severityMedium6.1

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

    CVE-2026-84178Source published Source updated

    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…

    Affected products in this advisory
    • Apache Camel OAuth
    Source-reported affected versions
    • 4.11.0 before 4.18.5
    • 4.19.0 before 4.22.1
    Source-reported fixed versions
    • 4.18.5
    • 4.22.1
    Mitigation guidance
    • 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.
    Full advisory and evidenceOpen source bulletin

Red Hat

1 advisory

References

More Apache advisories

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Apache

iPhone and Android apps · New on the App Store

Get alerts for new CVEs on 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.

Matching phone alertsOptional email delivery
Download on the App StoreGet CVE alerts on AndroidSee app features