Skip to content
VulniPulse
High8.2Red Hat Linux

High [CVE-2026-66908] org.apache.camel/camel-platform-http-main: org.apache.camel/camel-main: Apache Camel: Improper authentication allows JWT bypass in Platform HTTP Main component

This high-severity Red Hat Linux advisory covers CVE-2026-66908 affecting OpenShift Serverless, Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Apache Camel for Spring Boot 4.

CVE-2026-66908 Published Aug 24, 2026Updated by vendor Aug 24, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Improper Authentication vulnerability in Apache Camel Platform HTTP Main component. This issue affects Apache Camel: from 4.8.0 before 4.22.0.

The camel-main embedded HTTP server can protect its endpoints with JWT authentication, configured through authenticationEnabled together with the JWT keystore properties.

JWTAuthenticationConfigurer.buildJwtOptions returned null when neither jwtIssuer nor jwtAudience was configured, and the caller then skipped the JWTAuthOptions.setJWTOptions call entirely, so the Vert.x JWTAuth instance was built from the keystore alone.

The result was that inbound tokens were checked only for signature and expiry: the iss and aud claims were not validated at all.

Nothing signalled this - the server started normally and reported no warning - so a deployment configured the documented way silently enforced less than the operator believed it had enabled, and the component documentation itself presented signature and expiry checking as the default with issuer and audience as an optional extra.

Both the application server and the management server were affected, because the omission was in each of the two configureAuthentication paths. Any unexpired token signed by any key the configured keystore trusts was therefore accepted, regardless of which issuer minted it or which audience it was intended for.

Affected versions
  • < 4.8.0
  • < 4.22.0
  • < 4.21.0
  • 4.21

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions
  • 4.22.0
  • 4.14
  • 4.18
  • 4.14.9
  • 4.18.4

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation

Upgrade to a fixed release: 4.22.0, 4.14, 4.18, 4.14.9, 4.18.4. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.