CVE-2026-80312

LOWCVSS 8.2 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

Improper Authentication 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 camel-oauth processors that guard a route did not stop the exchange when authentication could not be completed. Where a failure to establish an authenticated session should have terminated routing and returned an error to the caller, the processors fell through and returned control to the route, so the request continued to the protected endpoint as though authentication had succeeded. The effect is a fail-open authentication guard: an unauthenticated caller reached whatever the route did next. The condition is reached on the ordinary request path of a route configured to require OAuth, and needs no special configuration or prior access on the caller's part. 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 processors now stop the exchange and set the appropriate error status whenever an authenticated session cannot be established, so a failed authentication no longer reaches the protected part of the route. For deployments that cannot upgrade immediately, place an explicit authorization check after the OAuth processor rather than relying on it to halt the exchange, and verify that the route stops on failure.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-287

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-10-26: 110-26
Referenced assets9 URLs
Full discourse1 post
  • ThreatWire@ThreatWire_

    🚨 A failed OAuth check in Apache Camel could still let the request through (CVE-2026-80312). One of 8 Camel/Camel K flaws, incl. unsafe deserialization. Fix: Camel 4.18.5/4.22.1/4.23.0, Camel K 2.9.3/2.10.2/2.11.0. Disclosed 8 Sep–19 Oct 2026. Breakdown: https://www.threatwire.tech/news/apache-camel-and-camel-k-fix-eight-high-and-critical-flaws-oauth-bypass-deserialization-rce CVE-2026-80352 https://www.threatwire.tech/cve/cve-2026-80352 CVE-2026-80351 https://www.threatwire.tech/cve/cve-2026-80351 CVE-2026-88900 https://www.threatwire.tech/cve/cve-2026-88900 [CVE-2026-78165 https://www.threatwire.tech/cve/cve-2026-78165 [CVE-2026-80312 https://www.threatwire.tech/cve/cve-2026-80312 CVE-2026-78164 https://www.threatwire.tech/cve/cve-2026-78164 CVE-2026-85251 https://www.threatwire.tech/cve/cve-2026-85251 CVE-2026-88901 https://www.threatwire.tech/cve/cve-2026-88901

    00023247
    2.0K followersView on X

Explore more