PHP web runtimes (CVE-2026-109618 and CVE-2026-109619)

114 pointsposted 11 hours ago
by hayd
(aws.amazon.com)

26 Comments

hayd

11 hours ago

Update: After posting this Amazon security released a bulletin to say we should see the updates _some time tomorrow_. https://aws.amazon.com/security/security-bulletins/2026-143-...

Scant messaging throughout the day. I don't understand why AWS, seemingly, didn't have prior knowledge of this/have it ready very soon after the CVE announcement.

otterley

11 hours ago

> Scant messaging throughout the day. I don't understand why AWS, seemingly, didn't have prior knowledge of this/have it ready very soon after the CVE announcement.

Posts elsewhere have suggested that the embargo was broken early. Even the PHP release team itself didn't have sufficient time to update their public Docker images before it was published.

hayd

11 hours ago

My understanding is the embargo was scheduled to end 14:00 UTC today, broken 07:41 UTC by Chainguard... It's now 22:00 UTC and AWS are talking about (some time) tomorrow.

bunderbunder

10 hours ago

The official story is that it was originally scheduled for 14:00 UTC tomorrow. Then yesterday they decided to move the date forward by 24 hours in response to information about the vulnerability leaking.

edaemon

10 hours ago

Even assuming they didn't have prior knowledge, I don't understand why AWS is going to take 24+ hours to incorporate an upstream fix.

mikeweiss

11 hours ago

Amazon has a bad track record for delivering critical updates quickly. During the Copy Fail - CVE-2026-31431 event they were behind every major Linux distro in updating Bottlerocket OS

jamesfinlayson

9 hours ago

Yes I was hit by waiting for Elastic Beanstalk to update nginx for the succession of fixes. Wasn't fun being pestered by my security team.

otterley

11 hours ago

Patch releases are currently scheduled for tomorrow (October 22): https://aws.amazon.com/security/security-bulletins/2026-143-...

hayd

11 hours ago

We didn't get much information throughout the day, besides these comments by an AWS employee/Amazon Linux maintainer on this thread: https://github.com/amazonlinux/amazon-linux-2023/issues/1148...

He referenced an nginx Important CVE taking 20 days to be patched - after it was noted that these PHP CVEs were also labelled by AWS as Important (not Critical). This employee took issue to another user's comment describing 20 days as "nearly a month".

Amazon Linux users/AWS customers barely got any tangible information from the CVE publication at 14:00UTC until this bulletin was posted at 21:30UTC. Very disappointing.

Twirrim

11 hours ago

Where, exactly, does Amazon classify the PHP RCE as Important?

I'm not sure anything says what your editorialised title, and comment link says.

They were calling out that an NGINX CVE that was Important took 20 days. They're saying nothing about what classification Amazon has set on PHP,.

> So, from the CVE publication to an available fixed package it took 20 days, not a month.

They specifically call out that it's not the same as the Nginx case:

> In contrast to the PHP's case, that CVE wasn't Critical, but only Important, that doesn't have the same urgency.

trgfdffd

11 hours ago

It seems to me that this comment is just regarding an earlier vulnerability and doesn't comment on PHP2Shell?

80fj0348i

11 hours ago

Honest question: Does anyone actually use Amazon Linux in production? Everywhere I've every worked used a mainstream distro for cloud servers, like Debian, Ubuntu, Red Hat or SUSE.

otterley

11 hours ago

I do. It works fine, particularly if you're using EKS- or ECS-optimized images.

jamesfinlayson

9 hours ago

Yes. I had a project that was built with Elastic Beanstalk and was trying to move off it, but never got there. Amazon Linux and its package management was not great and I missed Debian/CentOS/Ubuntu.

iririririr

10 hours ago

aren't everyone using lambda functions? and aws infra itself? they migth only consider the urgency of internal teams, so anything !java will be pushed.

pier25

10 hours ago

sounds like they are trying to get rid of users of Amazon Linux honestly