← Übersicht Nicht im beobachteten Stack

Apache Camel: Camel-Knative Improper Certificate Validation When SSL Is Enabled Without a Truststore

CVE-2026-85247

Mittel · CVSS 5.9 Red Hat: Moderate Netzwerk · ohne Login Kein Fix bekannt

Veröffentlicht
19.10.2026
Zuletzt geändert
04.11.2026
EPSS (30 Tage)
0.5 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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 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. Trusting every certificate is now reached only by asking for it explicitly through the trust.all property, which remains available for development against a cluster with a self-signed certificate. For deployments that cannot upgrade immediately, configure a truststore explicitly wherever SSL is enabled. After upgrading, a deployment that was relying on the implicit trust-all behaviour must either configure a truststore or set the trust.all property deliberately.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 2 betroffen.

OpenShift Serverless BetroffenFix zurückgestellt openshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9, openshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9, openshift-serverless-1/kn-eventing-integrations-log-sink-rhel9, openshift-serverless-1/kn-eventing-integrations-timer-source-rhel9
Red Hat build of Apache Camel for Spring Boot 4 BetroffenFix zurückgestellt camel-knative, camel-knative-http
Weitere betroffene Pakete (2)
CVEApache Software Foundation/Apache Camel4.0.0 → 4.18.5, 4.19.0 → 4.22.1CVE-2026-85247
NVDapache:camel4.0.0 → 4.18.5, 4.19.0 → 4.22.1CVE-2026-85247

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.