Skip to content
major vulnerability· requires attention

Widely used Apache Camel framework; auth bypass could disrupt deployments by exposing management endpoints.

Web

CVE-2026-40022

8.2
High
EPSS 0.62%Patch availableApr 28, 2026

Auth bypass in Camel embedded HTTP server enables unauthenticated subpath access.

common questions

Is CVE-2026-40022 being exploited?

Not confirmed. CVE-2026-40022 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. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.

How severe is CVE-2026-40022?

CVE-2026-40022 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-40022?

Yes. A fix has been recorded for CVE-2026-40022. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-40022 affect?

CVE-2026-40022 affects Apache Camel (embedded HTTP server) – v4.14.1–4.14.6, v4.18.0–4.18.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-40022?

Upgrade to 4.20.0 ASAP

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Apache Camel (embedded HTTP server) – v4.14.1–4.14.6, v4.18.0–4.18.2
impact

Unauthenticated access to subpaths can reach protected routes and may disclose runtime metadata via /observe/info.

action required

Immediate action required

affected versions
Apache Software Foundation Apache Camel Platform HTTP Main
  • affected>= 4.14.1 and < 4.14.6
  • affected>= 4.18.0 and < 4.18.2

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free