CVE-2026-85247: Improper Certificate Validation vulnerability in Apache Camel Knative component
CVE-2026-85247 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- Medium
- CVSS base score
- 5.9 (Apache), 5.9 (Red Hat)
- Weakness
- CWE-295
- Fixed releases
- Apache: 4.18.5, 4.22.1
- Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-85247; each belongs to its advisory, not to every product listed. How records are collected and checked.
How do I fix CVE-2026-85247?
Upgrade to a fixed release named by the vendor:
- Apache: 4.18.5, 4.22.1
- Red Hat: 4.23.0, 4.18, 4.18.5, 4.22, 4.22.1
- Upgrade to Apache Camel 4.23.0, which fixes the issue. (Apache)
- Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. (Apache)
Vendor advisories for CVE-2026-85247
Apache
1 advisory- Advisory severityMedium5.9
Medium [CVE-2026-85247] Improper Certificate Validation vulnerability in Apache Camel Knative component
CVE-2026-85247Source published Source updated
Improper Certificate Validation vulnerability in Apache Camel Knative component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. When SSL was enabled on the Knative HTTP client but no truststore was configured, the client options fell back to trusting every presented certificate rather than to the JVM's default trust anchors. A deployment that switched TLS on without also configuring a truststore therefore obtained an encrypted connection with no peer authentication, which an attacker positioned on the network path can terminate and read. The dangerous state is reached by omission rather than by an explicit opt-in, which is what makes it a framework defect: turning TLS on should not be the thing that turns certificate validation off. Upgrade to…
- Affected products in this advisory
- Apache Camel Knative
- Source-reported affected versions
- 4.0.0 before 4.18.5
- 4.19.0 before 4.22.1
- Source-reported fixed versions
- 4.18.5
- 4.22.1
- Mitigation guidance
- Upgrade to Apache Camel 4.23.0, which fixes the issue.
- Users on the 4.18.x LTS releases stream should upgrade to 4.18.5.
- Users on the 4.22.x LTS releases stream should upgrade to 4.22.1.
- With no truststore configured the trust options are now left unset so the JVM default trust anchors apply, the same fallback SSLContextParameters and the rest of Camel use.
2 more entries in the full advisory.
Red Hat
1 advisory- Advisory severityMedium5.9
Medium [CVE-2026-85247] Information disclosure via improper certificate validation
CVE-2026-85247Source published Source updated
Information disclosure via improper certificate validation. Red Hat rates this moderate (CVSS 5.9). Weakness: CWE-295. Affected products named by the advisory: OpenShift Serverless; Red Hat build of Apache Camel for Spring Boot 4.
- Related products — impact not confirmed
- OpenShift Serverless
- Red Hat build of Apache Camel for Spring Boot 4
- Source-reported affected versions
- < 4.0.0
- < 4.18.5
- < 4.19.0
- < 4.22.1
- Source-reported fixed versions
- 4.23.0
- 4.18
- 4.18.5
- 4.22
1 more entries in the full advisory.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
References
More Apache advisories
CVE-2026-84180Oct 19, 2026Generation of Error Message Containing Sensitive Information vulnerability in Apache CamelCVE-2026-86336Nov 10, 2026Apache TomEE running on JDK 21 or later skips EJB method authorization checksCVE-2026-86531Nov 10, 2026The embedded OpenEJB HTTP server does not limit the size of incoming request bodiesCVE-2026-87758Nov 10, 2026The remote EJB client does not verifyCVE-2026-97849Nov 10, 2026The embedded Derby network service ignores its configured bind address and listens on allCVE-2026-97867Nov 10, 2026The EJBd remote protocol returns datasource connection details, including database
Get an email when Apache publishes the next one.
See Apache's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
iPhone and Android apps · New on the App Store
Get alerts for new CVEs on your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
