CVE-2026-80312
Camel-OAuth processors fail open, letting requests that failed authentication through
Apache disclosed CVE-2026-80312 on 15 October 2026. The camel-oauth processors handed control back to the route when authentication could not be completed, so an unauthenticated request reached the protected route. Apache CVSS 3.1 8.2. Fixed in 4.18.5, 4.22.1 and 4.23.0. Public reproducer by a Camel PMC member. Not in KEV.
By ThreatWire Desk · Published 19 Oct 2026 · Updated 26 Oct 2026
- CVSS
- 8.2
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- Class
- Auth bypass
- Status
- PoC Available
- KEV
- Not in CISA KEV
- 0-day
- No
- Vendor
- Apache
- Products
- Apache Camel, camel-oauth
- Affected
- Apache Camel (org.apache.camel:camel-oauth) from 4.11.0 before 4.18.5, and from 4.19.0 before 4.22.1. The 4.14.x line is end of life and gets no fix.
- Fixed
- Apache Camel 4.18.5 (4.18.x LTS), 4.22.1 (4.22.x) and 4.23.0.
- CWE
- CWE-287
- Published
- 19 Oct 2026
- Updated
- 26 Oct 2026
The status above is the claim. Links do not upgrade it.
CVE-2026-80312 is an authentication bypass in camel-oauth, the Apache Camel component that guards routes with OAuth. Apache published the advisory on 15 October 2026. The CVE record and NVD entry followed on 19 October.
When authentication could not be completed, the processors did not stop the exchange. They returned control to the route. The request then went on as if it had been authenticated.
Apache calls it a fail-open guard. An unauthenticated caller reached whatever the route did next. The advisory says it needs no special configuration and no prior access.
It only matters for routes that use camel-oauth to protect them. What an attacker can reach depends on what the protected route does.
Apache scores it CVSS 3.1 8.2 (High). NVD shows the Apache score and has not added its own.
Affected: 4.11.0 before 4.18.5, and 4.19.0 before 4.22.1. Fixed: 4.18.5, 4.22.1 and 4.23.0. The 4.14.x line is end of life; Apache says to move to 4.18.5 or later.
Before you can upgrade, Apache suggests an explicit authorization check after the OAuth processor. Then verify that the route stops when authentication fails.
The advisory credits the Claude Security Scan Tool. A public reproducer repository is published by Andrea Cosentino (oscerd), the Camel PMC member who wrote the fix. ThreatWire did not run it.
The CVE is not in the CISA KEV catalog (catalog 2026.10.23). CISA's SSVC entry sets exploitation to none.
Read the full explainer on the eight Camel and Camel K flaws.
Sources
Related on ThreatWire
- NewsApache Camel and Camel K: eight high and critical flaws, from OAuth bypass to deserialization RCE
- VendorAll Apache CVEs in the ThreatWire tracker
- CVE recordCVE-2026-88900: Camel-JGroups consumer deserializes cluster messages without a filter, leading to code execution
- CVE recordCVE-2026-78164: Camel HTTP producers resolve property placeholders in message-supplied URI headers, exposing secrets
- CVE recordCVE-2026-78165: Camel-Spring-Redis default serializer deserializes Redis payloads without a filter, enabling code execution
- CVE recordCVE-2026-85251: Camel-HTTP re-sends credentials to whatever host a redirect names
- CVE recordCVE-2026-88901: Camel-Smooks resolves external XML entities by default, allowing local file reads
- CVE recordCVE-2026-88789: Camel Quarkus Xalan TransformerFactory drops XXE hardening