# CVE-2025-14760: Weak cryptography in AWS SDK for C++

> Missing key commitment in AWS SDK for C++ allows attackers with write access to manipulate encrypted data keys, potentially exposing plaintext data.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Dec 2025
- **Updated:** 17 Dec 2025
- **Also known as:** GHSA-792f-r46x-r7gm

## What is CVE-2025-14760?

CVE-2025-14760 is a medium-severity vulnerability in AWS SDK for C++, published on 17 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing cryptographic key commitment in the AWS SDK for C++ 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 AWS SDK for C++ to version 1.11.712 or later

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2025-14760?


## How do I fix CVE-2025-14760?

Upgrade to a fixed version.

## Is CVE-2025-14760 being exploited?

There is no known exploitation of CVE-2025-14760 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14760 and fix it if it is affected.

What it is: CVE-2025-14760 is a medium-severity vulnerability in AWS SDK for C++, published on 17 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14760 in the wild and no public exploit code.

Affected product: AWS SDK for C++. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14760/ (Markdown: https://insights.sbomify.com/CVE-2025-14760/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14760
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14760
- OSV: https://osv.dev/vulnerability/CVE-2025-14760

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14760/
Summaries are generated and may contain mistakes; the official description above is the record.