Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The aws-dynamodb-encryption-java package, versions before 1.15.0, has a key caching issue in MostRecentProvider. After key usage permissions were revoked at a key provider such as AWS Key Management Service, cached keys could still be used for encryption in the DynamoDB Encryption Client. Upgrade to 1.15.0 or later, and switch to CachingMostRecentProvider; if you cannot upgrade, call clear() on the cache to force revalidation with the key provider.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
No source has published a CVSS score for this record yet.
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 15:12 UTC First seen by agentprime
- 31 Oct 2026, 15:12 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-w736-hf9p-qqh3
- OSV: GHSA-w736-hf9p-qqh3
- github.com/aws/aws-dynamodb-encryption-java/security/advisories/GHSA-w736-hf9p-qqh3
- github.com/aws/aws-dynamodb-encryption-java/commit/7de5f5a5929271ab25bce685089eb7ec564dac4b
- github.com/aws/aws-dynamodb-encryption-java/blob/master/CHANGELOG.md#1150----2021-02-04