Security / News explained
The S3 PHP encryption advisory is about trusting altered ciphertext
CVE-2026-132607 weakens ciphertext authenticity checks in the S3 Encryption Client for PHP. It requires object read/write access and repeated changes; AWS identifies SDK 3.383.1 as fixed.
AWS published an S3 Encryption Client for PHP advisory on November 19, 2026 for CVE-2026-132607. It identifies AWS SDK for PHP versions 3.148.0 through 3.383.0 as affected, with 3.383.1 correcting the issue. The flaw concerns verification during client-side decryption. [1]
The security announcement and the fixed package have different dates. The project’s release record dates SDK 3.383.1 to May 29, 2026. This is a November explanation of a vulnerability and an already available correction, rather than a newly released November SDK version. [4]
Authenticity is a separate promise
The project advisory describes acceptance of an AES-GCM authentication tag of any length from an encrypted object’s metadata. Failing to enforce the expected tag length weakens the check that the ciphertext has not been forged. That is the particular verification boundary addressed here. [2]
The stated attack requires someone who can both read and write the encrypted object, knows or can guess its plaintext, and can make repeated writes. A successful forgery produces chosen plaintext of the same length as the original. Those requirements are narrower than anonymous access to a bucket. [2]
AWS explicitly says the issue does not disclose the plaintext or encryption key. The failure is about accepting altered encrypted data as authentic, with a different security consequence from exposing the secret used to encrypt it. [1]
That distinction matters to an application owner. Confidentiality asks whether someone can learn protected information. Integrity asks whether a consumer can trust the information it receives. A system can retain secrecy while still making a bad decision based on altered data. Saying only that “the key stayed secret” would leave that second question unanswered.
The encryption happens in the application
The PHP SDK guide describes client-side encryption as encryption and decryption performed in the application’s environment, before transfer to S3 and after retrieval. Its implementation uses envelope encryption and OpenSSL. That places this advisory’s affected verification code in the PHP software using the client. [5]
AWS documents server-side encryption as a separate layer performed at the storage destination. The two approaches can be used together. An encrypted object sent by a client remains an ordinary object from S3’s perspective; storage encryption does not perform the client library’s authenticity decision for the application. [6]
Consider a hypothetical export consumer that decrypts a stored document before acting on its contents. An account permitted to replace that object has a different role from an account permitted only to read it. If a permitted writer can also satisfy the advisory’s other conditions, the consumer’s authenticity check becomes important even though nobody has obtained its encryption key.
This scenario illustrates the trust decision, not a reported customer incident or a claim that every object writer can perform the forgery. The advisory’s plaintext-knowledge, length and repeated-write conditions still apply. Nor does the announcement establish that another SDK language or a server-side S3 encryption mode shares this particular flaw. [2]
For a business workflow, the question is what happens after decryption succeeds. An import could be reviewed by a person, or another process could act on it automatically. Those are hypothetical surrounding choices. Understanding that consequence helps explain why authenticity verification matters without expanding the vendor’s stated attack into an invented outcome.
Use the package boundary in the maintenance decision
Amazon’s CNA record also names the PHP decryption component and gives 3.383.1 as the corrective SDK version. AWS’s bulletin states there is no workaround and calls for that version or later. Restrictions on who can replace an object should not be reported as a substitute patch. [1] [3]
The PHP guide separately distinguishes several generations of encryption-client APIs and provides migration guidance. Those client names and the Composer package’s release number answer different questions. An implementation review should preserve that distinction rather than assuming that a newer-sounding class name proves which SDK build an application loads. [5]
The same care applies to maintenance language. Updating the PHP interpreter and updating the AWS SDK dependency are separate changes. A report that identifies the deployed SDK package and its consumer makes this advisory actionable; a broad statement that “PHP is current” does not tell the application owner whether this component received its correction.
In the hypothetical export service, useful release evidence would connect the reviewed dependency update to the artifact running the consumer and its normal decryption workflow. Any compatibility failure would deserve investigation on its own terms. An authenticity check rejecting unexpected input should not be casually weakened merely to make a failing workflow appear healthy again.
This advisory gives a precise reason to examine that consumer: altered ciphertext could cross a boundary that the application expected the encryption client to enforce. Keeping object permissions, SDK versions and downstream decisions visible turns an abstract cryptography headline into a maintenance question a team can actually answer.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- AWS S3 Encryption Client for PHP bulletin 2026-191AWS · Checked Nov 20, 2026
- AWS SDK for PHP project security advisoryAWS SDK for PHP · Checked Nov 20, 2026
- CVE-2026-132607 Amazon CNA recordAmazon · Checked Nov 20, 2026
- AWS SDK for PHP 3.383.1 release record and publication dateAWS SDK for PHP · Checked Nov 20, 2026
- Amazon S3 client-side encryption in the PHP SDKAWS · Checked Nov 20, 2026
- Client-side and server-side encryptionAWS · Checked Nov 20, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.