Skip to main content

CVE-2026-132607AWS aws-sdk-php insufficient verification of data authenticity

Low priorityMedium6.0EPSS not scored yet

CVE-2026-132607 is a insufficient verification of data authenticity in AWS aws-sdk-php, rated medium (6.0 on CVSS 4.0).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

Data is accepted without proof it came from where it claims.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can change data or behaviour. In practice, this kind of flaw lets an attacker read or tamper with traffic, or pass a forged message as genuine.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade AWS aws-sdk-php to 3.383.1 or later.
  2. Until it is patched, review who holds accounts that can reach it.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • TLS termination and service-to-service channels. The flaw sits on the network path between clients and services.
  • Signature checks. The flaw sits on the network path between clients and services.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • On the network path between clients and services. An attacker who crosses it can read or tamper with traffic, or pass a forged message as genuine.

Questions to answer about your own systems

  • Where does AWS aws-sdk-php run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.