Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.7

CVE-2026-14265: AWS Advanced JDBC Wrapper allows code execution through cache

CVE-2026-14265 · published 2 days ago
Summary

The AWS Advanced JDBC Wrapper driver can read cached query results from a shared Redis/Valkey store without checking their content. If someone can write to that cache, they could place specially crafted data that makes the application run unwanted code on its server. To protect yourself, keep the RemoteQueryCachePlugin turned off and limit write access to the cache to trusted users only.

What to do
  • Update software.amazon.jdbc:aws-advanced-jdbc-wrapper to version 4.0.1.
  • Update amazon advanced_jdbc_wrapper to version 4.0.1 or later.
Affected software
Ecosystem VendorProductAffected versions
– aws aws advanced jdbc wrapper <= 4.0.0
– amazon advanced_jdbc_wrapper >= 3.3.0, < 4.0.1
cpe:2.3:a:amazon:advanced_jdbc_wrapper:*:*:*:*:*:*:*:*
maven – software.amazon.jdbc:aws-advanced-jdbc-wrapper >= 3.3.0, < 4.0.1
Fix: upgrade to 4.0.1
Original advisory text
AWS-advanced-jdbc-wrapper: Java Deserialization RCE via Cache Poisoning
### Impact
The AWS Advanced JDBC Wrapper is an open-source JDBC driver wrapper that extends a JDBC driver to enable Amazon Aurora and AWS Cloud features such as failover handling and caching. We identified CVE-2026-14265, an issue in the RemoteQueryCachePlugin of the AWS Advanced JDBC Wrapper. When this plugin is enabled, query results read from the shared Redis/Valkey cache are deserialized without class filtering. An actor with write access to the shared cache infrastructure could insert a crafted serialized Java object that, when read by an application, results in execution of arbitrary code on the application server.

### Workarounds
The RemoteQueryCachePlugin is not enabled by default. Customers who cannot immediately upgrade can mitigate this issue by disabling the RemoteQueryCachePlugin, and by restricting write access to the Redis/Valkey cache infrastructure to trusted principals.
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
7.7 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-502Deserialization of Untrusted Data
Timeline
Published17 Nov 2026
Updated19 Nov 2026
First seen1 Jul 2026
Track software like this
Free during beta