CVE-2026-40022

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 58% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.2Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
—
EPSS
46.1%
KEV
Not listed

Published

April 27, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-40022: Apache Camel: Camel-Platform-HTTP-Main: Authentication Bypass on Non-Root Context Paths in camel main runtime

http://www.openwall.com/lists/oss-security/2026/04/26/5
generic

Apache Camel Security Advisory - CVE-2026-40022 - Apache Camel

https://camel.apache.org/security/CVE-2026-40022.html

Vendor Advisories for CVE-2026-40022(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcamel-http-starter2026-05-14redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.camel:camel-platform-http-main4.19.04.20.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 115 total refreshes for this CVE.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-20 13:04 UTCOSV refresh
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-13 22:30 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-08 15:15 UTCEPSS rescore
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 75 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-24 14:05 UTCEPSS rescore
  10. 2026-06-23 21:33 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-22 14:25 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 14:56 UTCEPSS rescore
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-19 19:25 UTCEPSS rescore
  17. 2026-06-18 17:52 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-17 17:53 UTCEPSS rescore
  20. 2026-06-16 17:52 UTCEPSS rescore
  21. 2026-06-15 17:49 UTCEPSS rescore
  22. 2026-06-14 23:00 UTCVendor advisory
  23. 2026-06-14 11:15 UTCVendor advisory
  24. 2026-06-13 23:00 UTCEPSS rescore
  25. 2026-06-12 23:12 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 05:43 UTCVendor advisory
  28. 2026-06-11 17:58 UTCVendor advisory
  29. 2026-06-11 14:00 UTCEPSS rescore
  30. 2026-06-11 06:13 UTCVendor advisory
  31. 2026-06-10 22:18 UTCEPSS rescore
  32. 2026-06-10 13:22 UTCEPSS rescore
  33. 2026-06-10 13:22 UTCEPSS rescore
  34. 2026-06-10 11:49 UTCVendor advisory
  35. 2026-06-10 00:05 UTCVendor advisory
  36. 2026-06-09 12:16 UTCVendor advisory
  37. 2026-06-09 00:13 UTCVendor advisory
  38. 2026-06-08 14:17 UTCEPSS rescore
  39. 2026-06-08 14:17 UTCEPSS rescore
  40. 2026-06-08 09:28 UTCVendor advisory
  41. 2026-06-07 21:44 UTCVendor advisory
  42. 2026-06-07 15:25 UTCEPSS rescore
  43. 2026-06-07 15:25 UTCEPSS rescore
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 10:00 UTCVendor advisory
  46. 2026-06-06 22:12 UTCVendor advisory
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 10:24 UTCVendor advisory
  50. 2026-06-05 22:47 UTCEPSS rescore
  51. 2026-06-05 22:47 UTCEPSS rescore
  52. 2026-06-05 22:10 UTCVendor advisory
  53. 2026-06-05 10:25 UTCVendor advisory
  54. 2026-06-05 06:10 UTCEPSS rescore
  55. 2026-06-05 06:10 UTCEPSS rescore
  56. 2026-06-04 22:15 UTCVendor advisory
  57. 2026-06-04 13:12 UTCEPSS rescore
  58. 2026-06-04 13:12 UTCEPSS rescore
  59. 2026-06-04 10:31 UTCVendor advisory
  60. 2026-06-03 22:35 UTCVendor advisory
  61. 2026-06-03 10:51 UTCVendor advisory
  62. 2026-06-02 23:01 UTCVendor advisory
  63. 2026-06-02 20:13 UTCEPSS rescore
  64. 2026-06-02 11:17 UTCVendor advisory
  65. 2026-06-01 23:30 UTCVendor advisory
  66. 2026-06-01 13:52 UTCEPSS rescore
  67. 2026-06-01 13:52 UTCEPSS rescore
  68. 2026-06-01 13:51 UTCEPSS rescore
  69. 2026-06-01 11:46 UTCVendor advisory
  70. 2026-05-31 22:30 UTCEPSS rescore
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-31 00:16 UTCEPSS rescore
  73. 2026-05-31 00:16 UTCEPSS rescore
  74. 2026-05-31 00:16 UTCEPSS rescore
  75. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-40022?
CVE-2026-40022 is a high vulnerability published on April 27, 2026. 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…
When was CVE-2026-40022 disclosed?
CVE-2026-40022 was first published in the National Vulnerability Database on April 27, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40022 actively exploited?
CVE-2026-40022 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40022?
CVE-2026-40022 has a CVSS v3.1 base score of 8.2 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-40022?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40022, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40022

Explore →

Is Your Infrastructure Affected by CVE-2026-40022?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs