Update dependency software.amazon.encryption.s3:amazon-s3-encryption-client-java to v4 [SECURITY]

[jamietanna]

This PR contains the following updates:

Package	Type	Update	Change
software.amazon.encryption.s3:amazon-s3-encryption-client-java	compile	major	3.4.0 → 4.0.0

---

Amazon S3 Encryption Client for Java has a Key Commitment Issue

CVE-2025-14763 / GHSA-x44p-gvrj-pj2r

More information

Details

Summary

S3 Encryption Client for Java is an open-source client-side encryption library used to facilitate writing and reading encrypted records to S3.

When the encrypted data key (EDK) is stored in an "Instruction File" instead of S3's metadata record, the EDK is exposed to an "Invisible Salamanders" attack (https://eprint.iacr.org/2019/016), which could allow the EDK to be replaced with a new key.

Impact

Background - Key Commitment

There is a cryptographic property whereby under certain conditions, a single ciphertext could be decrypted into 2 different plaintexts by using different encryption keys. To address this issue, strong encryption schemes use what is known as "key commitment", a process by which an encrypted message can only be decrypted by one key; the key used to originally encrypt the message.

In older versions of S3EC, when customers are also using a feature called "Instruction File" to store EDKs, key commitment is not implemented because multiple EDKs could be associated to an underlying encrypted message object. For such customers an attack that leverages the lack of key commitment is possible. A bad actor would need two things to leverage this issue: (i) the ability to create a separate, rogue, EDK that will also decrypt the underlying object to produce desired plaintext, and (ii) permission to upload a new instruction file to the S3 bucket to replace the existing instruction file placed there by the user using the S3C. Any future attempt to decrypt the underlying encrypted message with the S3EC will unwittingly use the rogue EDK to produce a valid plaintext message.

Impacted versions: <= v3.5

Patches

S3 Encryption Client is introducing the concept of "key commitment" to S3EC where the EDK is cryptographically bound to the ciphertext in order to address this issue. In order to maintain compatibility for in-flight messages we are releasing the fix in two versions. A code-compatible minor version that can read messages with key-commitment but not write them, and a new major version that can both read and write messages with key-commitment. For maximum safety customers are asked to upgrade to the latest major version: 4.0.0 or later

Workarounds

There are no workarounds, please upgrade to the suggested version of S3EC.

References

If users have any questions or comments about this advisory, S3 Encryption Client asks that they contact AWS Security via our issue reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

Severity

• CVSS Score: 6.0 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/aws/amazon-s3-encryption-client-java/security/advisories/GHSA-x44p-gvrj-pj2r
• https://nvd.nist.gov/vuln/detail/CVE-2025-14763
• https://github.com/aws/amazon-s3-encryption-client-java/commit/9d4523edbbc249781b3b3b3f8868fad39c5673d5
• https://aws.amazon.com/security/security-bulletins/AWS-2025-032
• https://github.com/aws/amazon-s3-encryption-client-java
• https://github.com/aws/amazon-s3-encryption-client-java/releases/tag/v4.0.0

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

aws/amazon-s3-encryption-client-java (software.amazon.encryption.s3:amazon-s3-encryption-client-java)

v4.0.0

Compare Source

⚠ BREAKING CHANGES

• The S3 Encryption Client now requires key committing algorithm suites by default.
  See migration guide from 3.x to 4.x: link

• builder() method has been removed; use builderV4() instead

• builderV4() now defaults to commitmentPolicy (REQUIRE_ENCRYPT_REQUIRE_DECRYPT) and encryptionAlgorithm (ALG_AES_256_GCM_HKDF_SHA512_COMMIT_KEY)

• Updated expectations for custom implementations of the CryptographicMaterialsManager interface.

  • Custom implementations of the interface's getEncryptionMaterials method MUST set the AlgorithmSuite field on the returned EncryptionMaterials.
    • The provided DefaultCryptoMaterialsManager's getEncryptionMaterials method sets this field from the AlgorithmSuite provided in the EncryptionMaterialsRequest.
    • If the custom implementation wraps the provided DefaultCryptoMaterialsManager.getEncryptionMaterials method, it's likely that no code updates are required. The provided logic has been updated with this change.
  • Custom implementations of the interface's decryptMaterials method MUST set the KeyCommitment field on the returned DecryptionMaterials.
    • The provided DefaultCryptoMaterialsManager's decryptMaterials method sets this field from the KeyCommitment provided in the DecryptMaterialsRequest.
    • If the custom implementation wraps the provided DefaultCryptoMaterialsManager.decryptMaterials method, it's likely that no code updates are required. The provided logic has been updated with this change.

• Updated expectations for custom implementations of the Keyring interface.

  • Custom implementations of the interface's onDecrypt method MUST preserve the KeyCommitment field on the returned DecryptionMaterials.
    • The provided S3Keyring's onDecrypt method (base class for all keyrings including KmsKeyring) preserves this field through the builder pattern when returning updated materials.
    • If the custom implementation wraps the provided S3Keyring.onDecrypt method or uses the builder pattern to return materials, it's likely that no code updates are required. The provided logic has been updated with this change.

Features

• Updates to the S3 Encryption Client (#​491) (9d4523e)

Maintenance

• update releaserc (#​492) (d423d8d)

v3.6.1: Amazon S3 Encryption Client 3.6.1 Release -- 2026-02-06

Compare Source

Changelog

3.6.1 (2026-02-06)

Fixes

• set instruction file content length (#​501) (e32cd09)

Maintenance

• release: release from main-3.x and remove javadocs (#​503) (e3bb32d)
• release: Update .releaserc (#​502) (80971da)

v3.6.0

Compare Source

Features

• Updates to the S3 Encryption Client (#​489) (2b13cf2)

Maintenance

• Add 's3:HeadObject' action to S3 bucket policies (#​488) (c24b358)
• update releaserc (#​490) (51d4635)

v3.5.0

Compare Source

Features

• allow raw keyrings to decrypt with multiple wrapping keys (#​485) (a78cb52)

Maintenance

• add client specification and Duvet annotations (#​481) (1bd8b7a)
• move spec submodule to master, update annotations (#​482) (cc9eafc)
• release: skip openjdk11 during release validation (#​487) (a210653)
• spec: add spec and Duvet annotations for KmsKeyring (#​483) (ab41a57)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.