CVE-2025-14764 json
Amazon S3 Encryption Client has a Key Commitment Issue
published 10mo ago modified last mo. also GHSA-3g75-q268-r9r6 , GO-2025-4250 , EUVD-2025-203945
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
Missing cryptographic key commitment in the Amazon S3 Encryption Client for Go 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 Go to version 4.0 or later.
Patch / fix
- go github.com/aws/amazon-s3-encryption-client-go/v3 4.0.0
- go github.com/aws/amazon-s3-encryption-client-go/v4 4.0.0
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20251230T014957-150000.1.134.1
suse advisories SUSE-SU-2026:0037-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2025-14764 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 10mo ago
Exploit prediction
0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N |
| CNA | 4.0 | 6.0 | 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 |
| CNA | 4.0 | 6.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/aws/amazon-s3-encryption-client-go/v3 | <4.0.0 all versions |
4.0.0 |
| go | github.com/aws/amazon-s3-encryption-client-go | all versions |
no fix listed |
| go | github.com/aws/amazon-s3-encryption-client-go/v4 | <4.0.0 |
4.0.0 |
Affected products
- AWS S3 Encryption Client for Go
Classification
- Weakness
-
- CWE-327 Use of a Broken or Risky Cryptographic Algorithm
References
-
github.com
/aws/amazon-s3-encryption-client-go/releases/tag/v4.0.0
patch, web
-
github.com
/aws/amazon-s3-encryption-client-go/commit/3e1740ec014e234e6d454291615011122e642b5d
web, patch
-
aws.amazon.com
/security/security-bulletins/AWS-2025-032/
vendor-advisory
-
github.com
/aws/amazon-s3-encryption-client-go/security/advisories/GHSA-3g75-q268-r9r6
third-party-advisory, web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-14764
advisory
-
aws.amazon.com
/security/security-bulletins/AWS-2025-032
web
-
github.com
/aws/amazon-s3-encryption-client-go
package
Sources
- CVE List CVE-2025-14764
- GitHub Advisory GHSA-3g75-q268-r9r6
- NVD CVE-2025-14764
- OSV GO-2025-4250
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.