# CVE-2026-132607: GCM authentication tag length downgrade in Amazon S3 Encryption Client for PHP


- **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
- **Fix available:** Yes
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-9c62-hqw2-gj46

## What is CVE-2026-132607?

CVE-2026-132607 is a medium-severity vulnerability in aws-sdk-php, published on 19 Nov 2026. 

### Official description

Insufficient verification of data authenticity in the decryption component of Amazon S3 Encryption Client for PHP in AWS SDK for PHP before 3.383.1 might allow an authenticated remote user to forge ciphertext that decrypts to arbitrary plaintext via manipulation of the GCM authentication tag length metadata.

To remediate this issue, users should upgrade to AWS SDK for PHP version 3.383.1 or later.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-132607?


## How do I fix CVE-2026-132607?

Upgrade aws-sdk-php to 3.383.1 or later. The advisory says that version fixes it.

## Is CVE-2026-132607 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-132607 and fix it if it is affected.

What it is: CVE-2026-132607 is a medium-severity vulnerability in aws-sdk-php, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-132607 in the wild and no public exploit code.

Affected product: aws-sdk-php. 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-2026-132607/ (Markdown: https://insights.sbomify.com/CVE-2026-132607/index.md)
```

## Sources

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

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