Amazon S3 Encryption Client for Java v<4.0 Key Commitment Vulnerability
CVE-2025-14763 Published on December 17, 2025
Missing cryptographic key commitment in the Amazon S3 Encryption Client for Java may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an "instruction file" instead of S3's metadata record. To mitigate this issue, upgrade Amazon S3 Encryption Client for Java to version 4.0.0 or later.
Vulnerability Analysis
CVE-2025-14763 can be exploited with network access, and requires small amount of user privileges. This vulnerability is consided to have a high level of attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality, a high impact on integrity, and no impact on availability.
Weakness Type
Use of a Broken or Risky Cryptographic Algorithm
The use of a broken or risky cryptographic algorithm is an unnecessary risk that may result in the exposure of sensitive information. The use of a non-standard algorithm is dangerous because a determined attacker may be able to break the algorithm and compromise whatever data has been protected. Well-known techniques may exist to break the algorithm.
Products Associated with CVE-2025-14763
Want to know whenever a new CVE is published for Amazon Aws? stack.watch will email you.
Affected Versions
AWS S3 Encryption Client for Java Version 4.0.0 is unaffected by CVE-2025-14763Vulnerable Packages
The following package name and versions may be associated with CVE-2025-14763
| Package Manager | Vulnerable Package | Versions | Fixed In |
|---|---|---|---|
| maven | software.amazon.encryption.s3:amazon-s3-encryption-client-java | < 4.0.0 | 4.0.0 |
Exploit Probability
EPSS (Exploit Prediction Scoring System) scores estimate the probability that a vulnerability will be exploited in the wild within the next 30 days. The percentile shows you how this score compares to all other vulnerabilities.