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.
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.
The Camel-PQC FileBasedKeyLifecycleManager class deserializes the contents of `<keyId>.key` files in the configured key directory using java.io.ObjectInputStream without applying any ObjectInputFilter or class-loading restrictions. The cast to `java.security.KeyPair` is evaluated only after `readObject()` has already returned, so any `readObject()` side effects in the deserialized object run before the type check. An attacker who can write to the key directory used by a Camel application — for example through a path traversal into the directory, misconfigured filesystem permissions on the volume where keys are stored, a compromised key provisioning pipeline, or a symlink attack — can place a crafted serialized Java object that, when deserialized during normal key lifecycle operations, results in arbitrary code execution in the context of the application.
This issue affects Apache Camel: from 4.19.0 before 4.20.0, from 4.18.0 before 4.18.2.
Users are recommended to upgrade to version 4.20.0, which fixes the issue by replacing java.io.ObjectInputStream-based key and metadata storage with standard PKCS#8 (private key) / X.509 SubjectPublicKeyInfo (public key) Base64 JSON encoding. For users on the 4.18.x LTS releases stream, upgrade to 4.18.2.
The camel-mina component's MinaConverter.toObjectInput(IoBuffer) type converter wraps an IoBuffer in a java.io.ObjectInputStream without applying any ObjectInputFilter or class-loading restrictions. When a Camel route uses camel-mina as a TCP or UDP consumer and requests conversion to ObjectInput (for example via getBody(ObjectInput.class) or @Body ObjectInput), an attacker sending a crafted serialized Java object over the network to the MINA consumer port can trigger arbitrary code execution in the context of the application during readObject().
This issue affects Apache Camel: from 3.0.0 before 4.14.6, 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.6. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2.
A flaw has been found in rawchen sims up to 004f783b1db5ecdfad81c8fdc3b34171211112de. Affected by this issue is some unknown functionality of the file sims-master/src/web/servlet/file/DeleteFileServlet.java of the component deleteFileServlet Endpoint. Executing a manipulation of the argument filename can lead to path traversal. The attack can be launched remotely. The exploit has been published and may be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.
A vulnerability was determined in Datavane Datavines up to 13607645e14a4982468cfdbcf75c85cde63bae71. The affected element is an unknown function of the file datavines-core/src/main/java/io/datavines/core/utils/TokenManager.java of the component JWT Token Handler. Executing a manipulation of the argument tokenSecret can lead to use of hard-coded cryptographic key
. The attack can be executed remotely. The attack requires a high level of complexity. The exploitability is described as difficult. The exploit has been publicly disclosed and may be utilized. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. This patch is called e540d6dc04e2e6ad11907fb655f3728a13e7b939. It is advisable to implement a patch to correct this issue. The project was informed of the problem early through a pull request but has not reacted yet.
BridgeHead Software FileStore versions prior to 24A contain a critical vulnerability (CVE-2026-39920) due to insecure default initialization of the Apache Axis2 administration module. This module is exposed on network-accessible endpoints with default credentials, allowing unauthenticated remote attackers to authenticate using these credentials, upload malicious Java archives as web services, and execute arbitrary operating system commands via SOAP requests. The vulnerability has a CVSS 4.0 score of 9.3, indicating critical severity. No official patch or remediation guidance is currently confirmed from the vendor. There are no known exploits in the wild at this time.
The OpenJDK 11 ELS packages provide the OpenJDK 11 Java Runtime Environment and the OpenJDK 11 Java Software Development Kit.
This release of the Red Hat build of OpenJDK 11 (11.0.31) with Extended Lifecycle Support for portable Linux serves as a replacement for the Red Hat build of OpenJDK 11 (11.0.30) and includes security and bug fixes as well as enhancements. For further information, refer to the release notes linked to in the References section.
Security Fix(es):
* JDK: LIBPNG: out-of-bounds read in png_image_read_composite (CVE-2025-66293)
* JDK: LIBPNG: Information disclosure and denial of service via integer
truncation in simplified write API (CVE-2026-22801)
* JDK: LIBPNG: has a heap buffer overflow in png_set_quantize (CVE-2026-25646)
* JDK: GIFLIB: Denial of Service via buffer overflow in EGifGCBToExtension
(CVE-2026-26740)
* JDK: LIBPNG: Arbitrary code execution due to use-after-free vulnerability
(CVE-2026-33416)
* JDK: LIBPNG: Information disclosure and denial of service via out-of-bounds
read/write in Neon palette expansion (CVE-2026-33636)
* JDK: LIBPNG: Denial of service and information disclosure via heap buffer over-read in png_image_finish_read (CVE-2026-22695)
* JDK: (CVE-2026-22007)
* JDK: (CVE-2026-22016)
* JDK: (CVE-2026-22013)
* JDK: (CVE-2026-22018)
* JDK: (CVE-2026-22021)
* JDK: (CVE-2026-34268)
* JDK: (CVE-2026-34282)
* JDK: (CVE-2026-23865)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
CVE-2026-34268 is a low-severity vulnerability in Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition affecting multiple versions including 8u481, 11.0.30, 17.0.18, 21.0.10, 25.0.2, and 26. The vulnerability allows an unauthenticated attacker with local logon access to the infrastructure where these products run to gain unauthorized read access to a subset of accessible data.
CVE-2026-22008 is a low-severity vulnerability in Oracle Java SE version 25.0.1 affecting the Libraries component. It allows an unauthenticated attacker with network access via multiple protocols to potentially perform unauthorized update, insert, or delete operations on some data accessible by Oracle Java SE. This vulnerability primarily impacts Java deployments running sandboxed Java Web Start applications or sandboxed Java applets that execute untrusted code relying on the Java sandbox for security. It does not affect server-side Java deployments running only trusted code. The vulnerability has a CVSS 3.1 base score of 3.7, indicating low severity with integrity impact only. Oracle’s April 2026 Critical Patch Update advisory does not explicitly confirm a patch for this specific vulnerability, and no known exploits are reported in the wild.
CVE-2026-22007 is a low-severity vulnerability in Oracle Java SE, Oracle GraalVM for JDK, and Oracle GraalVM Enterprise Edition affecting multiple versions including 8u481, 11.0.30, 17.0.18, and others. It allows an unauthenticated attacker with local logon access to the infrastructure where these products run to gain unauthorized read access to some accessible data. The vulnerability involves the Security component and can be exploited via APIs, including through web services or sandboxed Java applications that run untrusted code. The CVSS 3.1 base score is 2.9, indicating a low impact on confidentiality with no impact on integrity or availability.
CVE-2026-22003 is a medium severity vulnerability in Oracle Java SE and Oracle GraalVM Enterprise Edition Hotspot component affecting versions 8u481 and 8u481-b50. It allows a low privileged attacker with logon access to the infrastructure to compromise the affected products, but exploitation is difficult and requires human interaction from a person other than the attacker. Successful exploitation can lead to unauthorized creation, deletion, or modification of critical or accessible data and cause a hang or repeated crash resulting in denial of service. This vulnerability primarily affects Java deployments running untrusted code in sandboxed environments such as Java Web Start applications or applets, and does not apply to server deployments running only trusted code. The CVSS 3.1 base score is 6.0, reflecting integrity and availability impacts with attack vector local, high attack complexity, low privileges required, and user interaction required. Oracle has published a Critical Patch Update advisory for April 2026 but does not explicitly confirm a patch for this specific CVE in the provided content.
CVE-2026-32613 is a critical code injection vulnerability in Spinnaker, an open source multi-cloud continuous delivery platform. Prior to versions 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2, the Echo service in Spinnaker used Spring Expression Language (SPeL) without restricting access to trusted classes, allowing full JVM access. This flaw enables attackers to invoke arbitrary Java classes, potentially executing commands and accessing files on the system. The vulnerability has been patched in the specified fixed versions. As a workaround, disabling the Echo service entirely is recommended.
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. When redirect following is enabled (followRedirect(true)), versions of AsyncHttpClient prior to 3.0.9 and 2.14.5 forward Authorization and Proxy-Authorization headers along with Realm credentials to arbitrary redirect targets regardless of domain, scheme, or port changes. This leaks credentials on cross-domain redirects and HTTPS-to-HTTP downgrades. Additionally, even when stripAuthorizationOnRedirect is set to true, the Realm object containing plaintext credentials is still propagated to the redirect request, causing credential re-generation for Basic and Digest authentication schemes via NettyRequestFactory. An attacker who controls a redirect target (via open redirect, DNS rebinding, or MITM on HTTP) can capture Bearer tokens, Basic auth credentials, or any other Authorization header value. The fix in versions 3.0.9 and 2.14.5 automatically strips Authorization and Proxy-Authorization headers and clears Realm credentials whenever a redirect crosses origin boundaries (different scheme, host, or port) or downgrades from HTTPS to HTTP. For users unable to upgrade, set `(stripAuthorizationOnRedirect(true))` in the client config and avoid using Realm-based authentication with redirect following enabled. Note that `(stripAuthorizationOnRedirect(true))` alone is insufficient on versions prior to 3.0.9 and 2.14.5 because the Realm bypass still re-generates credentials. Alternatively, disable redirect following (`followRedirect(false)`) and handle redirects manually with origin validation.
CVE-2026-27674 is a code injection vulnerability in SAP NetWeaver Application Server Java (Web Dynpro Java) version WD-RUNTIME 7.50. An unauthenticated attacker can supply crafted input that is interpreted by the application, causing it to reference attacker-controlled content. If a victim accesses the affected functionality, the attacker-controlled content could execute in the victim's browser, potentially compromising the session and allowing arbitrary client-side code execution. This impacts the confidentiality and integrity of the application but does not affect availability.
OpenIdentityPlatform OpenAM versions prior to 16.0.6 contain a critical deserialization vulnerability (CWE-502) that allows unauthenticated remote code execution. The flaw arises from unsafe Java deserialization of the jato.clientSession HTTP parameter, bypassing previous mitigations applied to a similar parameter. An attacker can exploit this by sending a crafted serialized Java object to specific endpoints using JATO ViewBean JSPs, such as password reset pages. This vulnerability is fixed in version 16.0.6.