Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-27vm-5vpj-rp5g

Apache Camel Vulnerable to Authentication Bypass Using an Alternate Path or Channel

CVSS 8.2 HighEPSS 0.0094 · 60th percentile

Published by the GitHub Advisory Database at 27 Apr 2026, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.camel:camel-platform-http-mainMaven>=4.14.1, <4.14.6 || >=4.18.0, <4.18.2 || >=4.19.0, <4.20.04.14.6, 4.18.2, 4.20.0
Identifiers
GHSA-27vm-5vpj-rp5g · CVE-2026-40022
Weakness (CWE)
CWE-288 · CWE-551
Tags
Published
27 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Camel's camel-platform-http-main module is vulnerable to an authentication bypass in versions 4.14.1 to before 4.14.6, 4.18.0 to before 4.18.2, and 4.19.0 to before 4.20.0. When authentication is enabled and a non-root context path is configured, requests to subpaths of that path are not challenged for credentials, so an unauthenticated remote attacker can reach protected routes and management endpoints. Upgrade to 4.14.6, 4.18.2, or 4.20.0 depending on your release line.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0094, the 60th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:17 UTC First seen by agentprime
  2. 31 Oct 2026, 14:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.