Advisory record · GHSA-w736-hf9p-qqh3

Key Caching behavior in the DynamoDB Encryption Client.

No CVSS score

Published by the GitHub Advisory Database at 8 Feb 2021, 17:43 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.amazonaws:aws-dynamodb-encryption-javaMaven<1.15.01.15.0
Identifiers
GHSA-w736-hf9p-qqh3
Weakness (CWE)
CWE-862
Published
8 Feb 2021
Updated
2 Dec 2024

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.

Written 8 Nov 2026.

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

  1. 31 Oct 2026, 15:12 UTC First seen by agentprime
  2. 31 Oct 2026, 15:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.