---
id: "CVE-2026-80312"
kind: "vulnerability"
aliases: ["CVE-2026-80312"]
title: "Apache Camel: OAuth guard fails open, letting unauthenticated requests reach routes"
severity: "high"
cvss: 8.2
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["apache-camel", "camel-oauth", "java", "package", "self-hosted"]
not_affected_if: ["no-camel-oauth", "patched-version"]
published_at: "2026-10-19T11:17:21+00:00"
first_seen_at: "2026-10-23T21:57:17+00:00"
updated_at: "2026-10-25T03:04:26+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80312", "first_seen_at": "2026-10-23T21:57:17+00:00"}]
---

# Apache Camel: OAuth guard fails open, letting unauthenticated requests reach routes

The camel-oauth processors did not stop a request when authentication could not complete, so routing continued to the protected endpoint. An unauthenticated caller can reach whatever the guarded route does next.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Camel version in use, for example with `mvn dependency:tree | grep camel-oauth` or by reading the camel-oauth version in the build file.
- Look for routes that use the OAuth processor to guard an endpoint, and confirm they depend on it to halt the exchange.

## Fix

- Upgrade Apache Camel to `4.23.0`.
- If on the 4.18.x LTS stream, upgrade to `4.18.5`.
- If on the 4.22.x LTS stream, upgrade to `4.22.1`.
- Until upgraded, add an explicit authorization check after the OAuth processor and verify the route stops on failure.

## Timeline

- 2026-10-23T21:57:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-80312

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_