How severe is CVE-2026-40022?

CVE-2026-40022 has a CVSS score of 8.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2026-40022?

CVE-2026-40022 affects the following packages: org.apache.camel:camel-platform-http-main (Maven), org.apache.camel:camel-platform-http-main (Maven), org.apache.camel:camel-platform-http-main (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-40022?

Update org.apache.camel:camel-platform-http-main to 4.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40022 is resolved across your whole dependency graph.

How do I detect CVE-2026-40022 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-platform-http-main, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-40022 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-40022 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-40022 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-40022?

CVE-2026-40022 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-40022?

CVE-2026-40022 is classified as CWE-288 (CWE-288), CWE-551 (CWE-551). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-40022 published, and has it been updated?

CVE-2026-40022 was published on April 27, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2026-40022 — camel-platform-http-main

HIGHFix: apache/camel#22474

CVE-2026-40022 is a high-severity (CVSS 8.2) CWE-288 vulnerability in org.apache.camel:camel-platform-http-main. A fix is available for org.apache.camel:camel-platform-http-main — see the affected versions and patch details below.

Apache Camel Platform HTTP Main: Authentication Bypass on Non-Root Context Paths in camel main runtime

Also known asGHSA-27vm-5vpj-rp5g

Published

Apr 27, 2026

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-40022.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.apache.camel:camel-platform-http-main☕org.apache.camel:camel-platform-http-main☕org.apache.camel:camel-platform-http-main

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

When authentication is enabled on the Apache Camel embedded HTTP server or embedded management server (camel-platform-http-main) and a non-root context path such as /api or /admin is configured via camel.server.path or camel.management.path, the BasicAuthenticationConfigurer and JWTAuthenticationConfigurer classes derive the authentication path from properties.getPath() when camel.server.authenticationPath / camel.management.authenticationPath is not explicitly set. Combined with the Vert.x sub-router mounting model - the sub-router is mounted at path* and the authentication handler is registered inside the sub-router at the resolved path - this causes the authentication handler to match only the exact configured context path, not its subpaths. Unauthenticated requests to subpaths such as /api/route or /admin/observe/info therefore reach protected business routes and management endpoints without being challenged for credentials. The /observe/info endpoint can disclose runtime metadata such as the user, working directory, home directory, process ID, JVM and operating system information.

This issue affects Apache Camel: from 4.14.1 before 4.14.6, from 4.18.0 before 4.18.2.

Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, they are suggested to upgrade to 4.14.6. If users are on the 4.18.x LTS releases stream, they are suggested to upgrade to 4.18.2.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.camel:camel-platform-http-main`	≥ 4.14.1&&< 4.14.6	4.14.6`org.apache.camel:camel-platform-http-main:4.14.6`
☕Maven	`org.apache.camel:camel-platform-http-main`	≥ 4.18.0&&< 4.18.2	4.18.2`org.apache.camel:camel-platform-http-main:4.18.2`
☕Maven	`org.apache.camel:camel-platform-http-main`	≥ 4.19.0&&< 4.20.0	4.20.0`org.apache.camel:camel-platform-http-main:4.20.0`

Affected Products

1 product · 2 configurations

Application

camelapache

≥ 4.15.0 && < 4.18.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-platform-http-main, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-platform-http-main to 4.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40022 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14	`camel-http`	RHSA-2026:17668

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-40022 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works