Deserialization of Untrusted Data Affecting software.amazon.jdbc:aws-advanced-jdbc-wrapper package, versions [3.3.0,4.0.1)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.42% (34th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-JAVA-SOFTWAREAMAZONJDBC-17796067
  • published2 Jul 2026
  • disclosed1 Jul 2026
  • creditUnknown

Introduced: 1 Jul 2026

CVE-2026-14265  (opens in a new tab)
CWE-502  (opens in a new tab)

How to fix?

Upgrade software.amazon.jdbc:aws-advanced-jdbc-wrapper to version 4.0.1 or higher.

Overview

software.amazon.jdbc:aws-advanced-jdbc-wrapper is an Amazon Web Services (AWS) Advanced JDBC Wrapper

Affected versions of this package are vulnerable to Deserialization of Untrusted Data via the CachedResultSet deserialization path in the RemoteQueryCachePlugin. An attacker can execute arbitrary code on the application server by poisoning the shared Redis/Valkey cache with crafted serialized query results that are later read and deserialized by the driver. When the plugin reconstructs cached rows or result sets, it unmarshals untrusted cache data with ObjectInputStream and accepts attacker-controlled object graphs without class filtering. This impacts applications that enable the remote query cache and allow an untrusted or compromised principal to write to the shared cache, leading to server-side code execution when a victim application reads the poisoned entry.

Notes

  • The plugin is not enabled by default; the vulnerable path is only reachable in deployments that turn on RemoteQueryCachePlugin and use the shared cache for query-result reuse.
  • The cache lookup path accepts third-party application types when they are registered through Driver.skipWrappingForType() or Driver.skipWrappingForPackage(), so affected deployments may intentionally allow extra classes to deserialize from cache beyond the built-in JDBC types.

Workarounds

  • Disable RemoteQueryCachePlugin on systems that cannot be upgraded yet, to stop the driver from reading and deserializing cached query results from the shared cache.
  • Restrict write access to the Redis/Valkey cache infrastructure to trusted principals only, to prevent an attacker from poisoning cache entries with crafted serialized objects.

Details

Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.

Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.

CVSS Base Scores

version 4.0
version 3.1