deardaniel/secdata-raw huggingface dataset:
GitHub Security Advisory: GHSA-mqvw-jfmh-93qq
Package: org.springframework.boot:spring-boot-cassandra (MAVEN)
Severity: MODERATE (CVSS 5.0)
CWE: CWE-295: Improper Certificate Validation
Vulnerable versions: >= 3.4.0, <= 3.4.15
Patched in: unpatched

Summary: Spring Boot's Cassandra SSL auto-configuration disables TLS hostname verification

Details:
Spring Boot's Cassandra auto-configuration does not perform hostname verification when establishing an SSL connection to Cassandra.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); Cassandra SSL auto-configuration. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-mqvw-jfmh-93qq
Package: org.springframework.boot:spring-boot-cassandra (MAVEN)
Severity: MODERATE (CVSS 5.0)
CWE: CWE-295: Improper Certificate Validation
Vulnerable versions: >= 3.5.0, < 3.5.14
Patched in: 3.5.14

Summary: Spring Boot's Cassandra SSL auto-configuration disables TLS hostname verification

Details:
Spring Boot's Cassandra auto-configuration does not perform hostname verification when establishing an SSL connection to Cassandra.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); Cassandra SSL auto-configuration. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-mqvw-jfmh-93qq
Package: org.springframework.boot:spring-boot-cassandra (MAVEN)
Severity: MODERATE (CVSS 5.0)
CWE: CWE-295: Improper Certificate Validation
Vulnerable versions: >= 4.0.0, < 4.0.6
Patched in: 4.0.6

Summary: Spring Boot's Cassandra SSL auto-configuration disables TLS hostname verification

Details:
Spring Boot's Cassandra auto-configuration does not perform hostname verification when establishing an SSL connection to Cassandra.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); Cassandra SSL auto-configuration. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-wwpq-f5c3-7hvx
Package: org.springframework.boot:spring-boot (MAVEN)
Severity: HIGH (CVSS 7.0)
CWE: CWE-377: Insecure Temporary File
Vulnerable versions: <= 2.7.32
Patched in: unpatched

Summary: Spring Boot accepts predictable temp directory without ownership verification

Details:
A local attacker on the same host as the application may be able to take control of the directory used by `ApplicationTemp`. When `server.servlet.session.persistent` is set to `true` and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); predictable temp directory / `ApplicationTemp` ownership verification. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-wwpq-f5c3-7hvx
Package: org.springframework.boot:spring-boot (MAVEN)
Severity: HIGH (CVSS 7.0)
CWE: CWE-377: Insecure Temporary File
Vulnerable versions: >= 3.3.0, <= 3.3.18
Patched in: unpatched

Summary: Spring Boot accepts predictable temp directory without ownership verification

Details:
A local attacker on the same host as the application may be able to take control of the directory used by `ApplicationTemp`. When `server.servlet.session.persistent` is set to `true` and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); predictable temp directory / `ApplicationTemp` ownership verification. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-wwpq-f5c3-7hvx
Package: org.springframework.boot:spring-boot (MAVEN)
Severity: HIGH (CVSS 7.0)
CWE: CWE-377: Insecure Temporary File
Vulnerable versions: >= 3.4.0, <= 3.4.15
Patched in: unpatched

Summary: Spring Boot accepts predictable temp directory without ownership verification

Details:
A local attacker on the same host as the application may be able to take control of the directory used by `ApplicationTemp`. When `server.servlet.session.persistent` is set to `true` and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); predictable temp directory / `ApplicationTemp` ownership verification. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-wwpq-f5c3-7hvx
Package: org.springframework.boot:spring-boot (MAVEN)
Severity: HIGH (CVSS 7.0)
CWE: CWE-377: Insecure Temporary File
Vulnerable versions: >= 3.5.0, < 3.5.14
Patched in: 3.5.14

Summary: Spring Boot accepts predictable temp directory without ownership verification

Details:
A local attacker on the same host as the application may be able to take control of the directory used by `ApplicationTemp`. When `server.servlet.session.persistent` is set to `true` and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); predictable temp directory / `ApplicationTemp` ownership verification. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-wwpq-f5c3-7hvx
Package: org.springframework.boot:spring-boot (MAVEN)
Severity: HIGH (CVSS 7.0)
CWE: CWE-377: Insecure Temporary File
Vulnerable versions: >= 4.0.0, < 4.0.6
Patched in: 4.0.6

Summary: Spring Boot accepts predictable temp directory without ownership verification

Details:
A local attacker on the same host as the application may be able to take control of the directory used by `ApplicationTemp`. When `server.servlet.session.persistent` is set to `true` and the attack persists across application restarts, this may allow the attacker to read session information and hijack authenticated users or deploy a gadget chain and execute code as the application's user.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); predictable temp directory / `ApplicationTemp` ownership verification. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-m4x9-hx6x-2c43
Package: org.springframework.boot:spring-boot-cassandra (MAVEN)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-330: Use of Insufficiently Random Values
Vulnerable versions: <= 2.7.32
Patched in: unpatched

Summary: Spring Boot's random value property source uses a weak PRNG unsuitable for secrets

Details:
Values produced by ${random.value} are not suitable for use as secrets. ${random.uuid} is not affected. ${random.int} and ${random.long} should never be used for secrets as they are numeric values with a predictable range.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); random value property source / weak PRNG for secrets. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-m4x9-hx6x-2c43
Package: org.springframework.boot:spring-boot-cassandra (MAVEN)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-330: Use of Insufficiently Random Values
Vulnerable versions: >= 3.3.0, <= 3.3.18
Patched in: unpatched

Summary: Spring Boot's random value property source uses a weak PRNG unsuitable for secrets

Details:
Values produced by ${random.value} are not suitable for use as secrets. ${random.uuid} is not affected. ${random.int} and ${random.long} should never be used for secrets as they are numeric values with a predictable range.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); random value property source / weak PRNG for secrets. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-m4x9-hx6x-2c43
Package: org.springframework.boot:spring-boot-cassandra (MAVEN)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-330: Use of Insufficiently Random Values
Vulnerable versions: >= 3.4.0, <= 3.4.15
Patched in: unpatched

Summary: Spring Boot's random value property source uses a weak PRNG unsuitable for secrets

Details:
Values produced by ${random.value} are not suitable for use as secrets. ${random.uuid} is not affected. ${random.int} and ${random.long} should never be used for secrets as they are numeric values with a predictable range.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); random value property source / weak PRNG for secrets. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-m4x9-hx6x-2c43
Package: org.springframework.boot:spring-boot-cassandra (MAVEN)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-330: Use of Insufficiently Random Values
Vulnerable versions: >= 3.5.0, < 3.5.14
Patched in: 3.5.14

Summary: Spring Boot's random value property source uses a weak PRNG unsuitable for secrets

Details:
Values produced by ${random.value} are not suitable for use as secrets. ${random.uuid} is not affected. ${random.int} and ${random.long} should never be used for secrets as they are numeric values with a predictable range.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); random value property source / weak PRNG for secrets. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-m4x9-hx6x-2c43
Package: org.springframework.boot:spring-boot-cassandra (MAVEN)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-330: Use of Insufficiently Random Values
Vulnerable versions: >= 4.0.0, < 4.0.6
Patched in: 4.0.6

Summary: Spring Boot's random value property source uses a weak PRNG unsuitable for secrets

Details:
Values produced by ${random.value} are not suitable for use as secrets. ${random.uuid} is not affected. ${random.int} and ${random.long} should never be used for secrets as they are numeric values with a predictable range.

Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); random value property source / weak PRNG for secrets. Versions that are no longer supported are also affected per vendor advisory.
GitHub Security Advisory: GHSA-8v8j-3hxp-93wr
Package: org.springframework.boot:spring-boot (MAVEN)
Severity: CRITICAL (CVSS 9.1)
CWE: CWE-862: Missing Authorization
Vulnerable versions: >= 4.0.0, < 4.0.6
Patched in: 4.0.6

Summary: Spring Boot's default security filter chain has no authorization rule with Actuator but without Health

Details:
In certain circumstances, Spring Boot's default web security is ineffective allowing unauthorized access to all endpoints. For an application to be vulnerable, it must: be a servlet-based web application; have no Spring Security configuration of its own and rely on the default web security filter chain; depend on spring-boot-actuator-autoconfigure; not depend on spring-boot-health. If any of the above does not apply, the application is not vulnerable.

Affected: Spring Boot 4.0.0–4.0.5; upgrade to 4.0.6 or later per vendor advisory.
GitHub Security Advisory: GHSA-c96x-rpm4-349p
Package: org.springframework.boot:spring-boot-elasticsearch (MAVEN)
Severity: MODERATE (CVSS 5.0)
CWE: CWE-295: Improper Certificate Validation
Vulnerable versions: >= 4.0.0, < 4.0.6
Patched in: 4.0.6

Summary: Spring Boot's Elasticsearch auto-configuration doesn't perform hostname verification when connecting to the Elasticsearch server.

Details:
When configured to use an SSL bundle, Spring Boot's Elasticsearch auto-configuration does not perform hostname verification when connecting to the Elasticsearch server.

Affected: Spring Boot 4.0.0–4.0.5; upgrade to 4.0.6 or later per vendor advisory.
GitHub Security Advisory: GHSA-fxc7-fm93-6q77
Package: com.arcadedb:arcadedb-server (MAVEN)
Severity: CRITICAL (CVSS 9.0)
CWE: CWE-863: Incorrect Authorization
Vulnerable versions: < 26.4.2
Patched in: 26.4.2

Summary: ArcadeDB vulnerable to cross-database authorization bypass and unsecured newly-created databases

Details:
### Impact
Authenticated users and API tokens scoped to a specific database could read, write, and mutate schema on any other database on the same server. Two distinct defects contributed: (1) ServerSecurityUser.getDatabaseUser() returned a DB user with an uninitialized fileAccessMap, which requestAccessOnFile treated as allow-all; (2) ArcadeDBServer.createDatabase() omitted factory.setSecurity(...) so any database created via POST /api/v1/server {"command":"create database X"} had its entire record-level authorization system silently disabled. In combination, record-level and database-level authorization could be bypassed by any authenticated principal.

### Patches
Upgrade to version 26.4.2

### Resources

https://github.com/ArcadeData/arcadedb/commit/04110c06315da55604ac107f71fe7182f3a3deb8
GitHub Security Advisory: GHSA-j2q8-xx3q-8fqh
Package: org.apache.storm:storm-client (MAVEN)
Severity: MODERATE (CVSS 6.5)
CWE: CWE-287: Improper Authentication
Vulnerable versions: < 2.8.7
Patched in: 2.8.7

Summary: Apache Storm's Improper Handling of TLS Client Authentication Failure Leads to Anonymous Principal Assignment

Details:
Improper Handling of TLS Client Authentication Failure Leading to Anonymous Principal Assignment in Apache Storm

Versions Affected: up to 2.8.7

Description: When TLS transport is enabled in Apache Storm without requiring client certificate authentication (the default configuration), the TlsTransportPlugin assigns a fallback principal (CN=ANONYMOUS) if no client certificate is presented or if certificate verification fails. The underlying SSLPeerUnverifiedException is caught and suppressed rather than rejecting the connection.

This fail-open behavior means an unauthenticated client can establish a TLS connection and receive a valid principal identity. If the configured authorizer (e.g., SimpleACLAuthorizer) does not explicitly deny access to CN=ANONYMOUS, this may result in unauthorized access to Storm services. The condition is logged at debug level only, reducing visibility in production.

Impact: Unauthenticated clients may be assigned a principal identity, potentially bypassing authorization in permissive or misconfigured environments.

Mitigation: Users should upgrade to 2.8.7 in which TLS authentication failures are handled in a fail-closed manner.

Users who cannot upgrade immediately should:
- Enable mandatory client certificate authentication (nimbus.thrift.tls.client.auth.required: true)
- Ensure authorization rules explicitly deny access to CN=ANONYMOUS
- Review all ACL configurations for implicit default-allow behavior
GitHub Security Advisory: GHSA-82fm-wpc2-5pmp
Package: org.apache.storm:storm-metrics-prometheus (MAVEN)
Severity: MODERATE (CVSS 4.8)
CWE: CWE-295: Improper Certificate Validation
Vulnerable versions: >= 2.6.3, < 2.8.7
Patched in: 2.8.7

Summary: Apache Storm Prometheus Reporter vulnerable to Improper Certificate Validation via Global SSL Context Downgrade

Details:
Improper Certificate Validation via Global SSL Context Downgrade in Apache Storm Prometheus Reporter


Versions Affected: from 2.6.3 to 2.8.6


Description: 

In production deployments where an administrator enables storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation (by default it is disabled) intending to affect only the Prometheus reporter, the undocumented global side effect creates an attack surface across every TLS-protected communication channel in the Storm daemon.


The PrometheusPreparableReporter class implements an INSECURE_TRUST_MANAGER that accepts all SSL certificates without validation, with empty checkClientTrusted and checkServerTrusted methods. Most critically, when the storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation configuration option is enabled (default = disabled) for HTTPS Prometheus PushGateway connections, the INSECURE_CONNECTION_FACTORY calls SSLContext.setDefault(sslContext), which globally replaces the JVM's default SSL context rather than applying the insecure context only to the Prometheus connection. This payload flows through storm.yaml configuration → PrometheusPreparableReporter.prepare() → INSECURE_CONNECTION_FACTORY → SSLContext.setDefault(), resulting in a JVM-wide TLS security downgrade. All subsequent HTTPS connections in the process - including ZooKeeper, Thrift, Netty, and UI connections - silently trust all certificates, including self-signed, expired, and attacker-generated ones, enabling man-in-the-middle interception of cluster state, topology submissions, tuple data, and administrative credentials.




Mitigation: 2.x users should upgrade to 2.8.7 if the Prometheus Metrics Reporter is used. Prometheus Metrics Reporter Users who cannot upgrade immediately should remove the storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation: true setting from their storm.yaml configuration and instead configure a proper truststore containing the PushGateway's certificate.
GitHub Security Advisory: GHSA-4xwx-hvv7-7prj
Package: org.apache.camel:camel-infinispan (MAVEN)
Severity: HIGH (CVSS 8.8)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: >= 4.19.0, < 4.20.0
Patched in: 4.20.0

Summary: Apache Camel-Infinispan Component Vulnerable to Deserialization of Untrusted Data

Details:
The camel-infinispan component's ProtoStream-based remote aggregation repository deserializes data read from a remote Infinispan cache using java.io.ObjectInputStream without applying any ObjectInputFilter. An attacker who can write to the Infinispan cache used by a Camel application can inject a crafted serialized Java object that, when read during normal aggregation repository operations such as get or recover, results in arbitrary code execution in the context of the application.

This issue affects Apache Camel: from 4.0.0 before 4.14.7, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0.

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, then they are suggested to upgrade to 4.14.7. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2.

The JIRA ticket:  https://issues.apache.org/jira/browse/CAMEL-23322  refers to the various commits that resolved the issue, and have more details. This issue follows the same class of vulnerability previously addressed in CVE-2024-22369, CVE-2024-23114 and CVE-2026-25747.
GitHub Security Advisory: GHSA-4xwx-hvv7-7prj
Package: org.apache.camel:camel-infinispan (MAVEN)
Severity: HIGH (CVSS 8.8)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: >= 4.15.0, < 4.18.2
Patched in: 4.18.2

Summary: Apache Camel-Infinispan Component Vulnerable to Deserialization of Untrusted Data

Details:
The camel-infinispan component's ProtoStream-based remote aggregation repository deserializes data read from a remote Infinispan cache using java.io.ObjectInputStream without applying any ObjectInputFilter. An attacker who can write to the Infinispan cache used by a Camel application can inject a crafted serialized Java object that, when read during normal aggregation repository operations such as get or recover, results in arbitrary code execution in the context of the application.

This issue affects Apache Camel: from 4.0.0 before 4.14.7, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0.

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, then they are suggested to upgrade to 4.14.7. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2.

The JIRA ticket:  https://issues.apache.org/jira/browse/CAMEL-23322  refers to the various commits that resolved the issue, and have more details. This issue follows the same class of vulnerability previously addressed in CVE-2024-22369, CVE-2024-23114 and CVE-2026-25747.
GitHub Security Advisory: GHSA-4xwx-hvv7-7prj
Package: org.apache.camel:camel-infinispan (MAVEN)
Severity: HIGH (CVSS 8.8)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: >= 4.0.0, < 4.14.7
Patched in: 4.14.7

Summary: Apache Camel-Infinispan Component Vulnerable to Deserialization of Untrusted Data

Details:
The camel-infinispan component's ProtoStream-based remote aggregation repository deserializes data read from a remote Infinispan cache using java.io.ObjectInputStream without applying any ObjectInputFilter. An attacker who can write to the Infinispan cache used by a Camel application can inject a crafted serialized Java object that, when read during normal aggregation repository operations such as get or recover, results in arbitrary code execution in the context of the application.

This issue affects Apache Camel: from 4.0.0 before 4.14.7, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0.

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, then they are suggested to upgrade to 4.14.7. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2.

The JIRA ticket:  https://issues.apache.org/jira/browse/CAMEL-23322  refers to the various commits that resolved the issue, and have more details. This issue follows the same class of vulnerability previously addressed in CVE-2024-22369, CVE-2024-23114 and CVE-2026-25747.
GitHub Security Advisory: GHSA-5rc6-9qfp-8vwg
Package: org.apache.camel:camel-consul (MAVEN)
Severity: MODERATE (CVSS 6.3)
CWE: CWE-502: Deserialization of Untrusted Data
Vulnerable versions: >= 4.15.0, < 4.18.1
Patched in: 4.18.1

Summary: Apache Camel-Consul component vulnerable to Deserialization of Untrusted Data

Details:
The ConsulRegistry in the camel-consul component (class org.apache.camel.component.consul.ConsulRegistry and its inner ConsulRegistryUtils.deserialize method) read Java-serialized values from the Consul KV store and passed them to ObjectInputStream.readObject() without configuring an ObjectInputFilter. An attacker who can write to the Consul KV store backing a Camel ConsulRegistry instance could inject a malicious serialized Java object that is deserialized the next time Camel performs a lookup against that registry, leading to arbitrary code execution in the Camel process. The issue mirrors the class of vulnerability already addressed for other Camel components in CVE-2024-22369, CVE-2024-23114 and CVE-2026-25747, and was overlooked during the original remediation of those CVEs.

This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.1.

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