Apache Camel is a widely used enterprise integration framework; fail-open OAuth lets unauthenticated requests reach protected routes, risking unauthorized actions and data exposure across deployments.
CVE-2026-80312
Apache Camel OAuth processors fail-open, allowing unauthenticated access to protected routes.
Is CVE-2026-80312 being exploited?
Not confirmed. CVE-2026-80312 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-80312?
CVE-2026-80312 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-80312?
Yes. A fix has been recorded for CVE-2026-80312. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-80312 affect?
CVE-2026-80312 affects Apache Camel camel-oauth >=4.11.0 <4.18.5, Apache Camel >=4.19.0 <4.22.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-80312?
Upgrade to 4.23.0 (or 4.18.5 / 4.22.1 LTS). If unable, add explicit auth checks after the OAuth processor.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authentication bypass: unauthenticated callers can reach protected endpoints and perform actions allowed by the route.
Immediate action required
- affected>= 4.11.0 and < 4.18.5
- affected>= 4.19.0 and < 4.22.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.