# AWS SDK for PHP's S3 Encryption Client has a Key Commitment Issue

Advisory record · `GHSA-x8cp-jf6f-r4xh`

- **Identifiers:** `GHSA-x8cp-jf6f-r4xh` · `CVE-2025-14761` · `PKSA-dxyf-6n16-t87m`
- **State:** Confirmed
- **Severity:** CVSS 6.0 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-327](https://cwe.mitre.org/data/definitions/327.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 18 Dec 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Dec 2025, 18:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `aws/aws-sdk-php` (Packagist): affected `<3.368.0`; fixed in `3.368.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The AWS SDK for PHP's S3 Encryption Client, in aws/aws-sdk-php versions before 3.368.0, is vulnerable to a key commitment weakness when encrypted data keys are stored in an Instruction File. An attacker who can upload a new Instruction File to the same S3 bucket, and who can create a rogue encrypted data key, could cause the client to decrypt the object with that key and return attacker-chosen plaintext. Upgrade to aws/aws-sdk-php 3.368.0 or later, as the source states there are no workarounds.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.0 Medium, CVSS 4.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`, from CNA (AMZN)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 11th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:02 UTC: First seen by agentprime
- 31 Oct 2026, 14:02 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x8cp-jf6f-r4xh)

## Sources

- [GitHub Advisory Database: GHSA-x8cp-jf6f-r4xh](https://github.com/advisories/GHSA-x8cp-jf6f-r4xh)
- [OSV: GHSA-x8cp-jf6f-r4xh](https://osv.dev/vulnerability/GHSA-x8cp-jf6f-r4xh)
- <https://github.com/aws/aws-sdk-php/security/advisories/GHSA-x8cp-jf6f-r4xh>
- <https://nvd.nist.gov/vuln/detail/CVE-2025-14761>
- <https://github.com/aws/aws-sdk-php/commit/6827cac70397dca07e6e86f7cf630954ec2bc6bf>
- <https://aws.amazon.com/security/security-bulletins/AWS-2025-032>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/aws/aws-sdk-php/CVE-2025-14761.yaml>
- <https://github.com/aws/aws-sdk-php>
- <https://github.com/aws/aws-sdk-php/releases/tag/3.368.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x8cp-jf6f-r4xh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x8cp-jf6f-r4xh/>. Everything for agents: <https://agentprime.io/llms.txt>.