CVE-2025-14759
Missing cryptographic key commitment in the Amazon S3 Encryption …
Missing cryptographic key commitment in the Amazon S3 Encryption Client for .NET 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 .NET to version 3.2.0 or later.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/aws/amazon-s3-encryption-client-dotnet/security/advisories/GHSA-4v42-65r3-3gjx
- nvd.nist.gov/vuln/detail/CVE-2025-14759
- github.com/aws/amazon-s3-encryption-client-dotnet/commit/6a0272c79347b2672eea599f73ee1a94d
- aws.amazon.com/security/security-bulletins/AWS-2025-032
- github.com/aws/amazon-s3-encryption-client-dotnet/releases/tag/release_2025-12-17
- github.com/advisories/GHSA-4v42-65r3-3gjx
- aws.amazon.com/security/security-bulletins/AWS-2025-032/
- nvd.nist.gov/vuln/detail/CVE-2025-14759
- cve.org/CVERecord?id=CVE-2025-14759
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.