Liz Fong-Jones (方禮真)

@lizthegrey.com

Technical Fellow, @honeycomb.io American by birth, Chinese by heritage, Australian by choice living on occupied and unceded Gadigal and Musqueam/Squamish/Tsleil-Waututh land she/it

if you, like me, spent two days patching and wondering whether you missed something: same. the checks are boring. which workloads run fixed vs vulnerable PHP or Go builds, and where repeat 500s hit while exposed (a good sign of compromise). if events carry runtime version, it’s a query, not a grep.

An embargoed security issue in PHP leaked and it is extremely serious: all versions >5.4 are affected. No patches are available yet. I highly recommend shutting down any PHP services until the patch is available—that's how severe this issue is.

new reference PDS container has been published! if you do the classic self-hosting auto-update setup, you can force a faster refresh with: sudo pdsadmin update and while you are in there why not: sudo apt update sudo apt upgrade

BTW knowledge of the existence of this vulnerability enables a well financed malware group to use AI to find it, if you run PHP anything you should be taking the service down NOW until a patch is available. And then patch before bringing the service back up.

nightshade →home, for now@nightshade.technology · yesterday

details leaked. this vulnerability is a full unauthenticated unconditional remote code execution exploit against any service running on a PHP version from 5.4 until latest yeah if anything deserves CVSS 11, this is it. this is CATACLYSMICALLY bad.

`session.upload_progress.enabled = Off` is a stopgap, so at least it isn't as demonic as like, heartbleed remediation was, but enjoy figuring out whether your router has been weaseled or whatever I want to say that only the PHP team could cause a heap UAF, but someone else will live down to that

Only for the curious...

jackalsyn.com

We should start requiring root certs to support name constraint validation. It was never adopted due to browser bugs. But it is time.

No, people really are not getting this. The login needs to be through your SSO so that your IT team can cut you off. An SSO that uses passkeys is a good SSO. A random app using SSO has absolutely no use for passkeys, they add nothing. For consumer accounts, just use passkeys, yes, they're the best.

After the firefighting is done (and a nap) we'll need to have a long, serious conversation about the state of non-browser non-platform X.509 verifiers. The Linux status quo is "a pile of PEM files behind a dumpster" and that's not an acceptable excuse for a root store in 2026.

me going to work this morning: 😀🎶🎶🎶 me seeing a go patch release for security: eh, probably not a big deal me opening up the patch release email: crypto/x509, eh, probably not a feature we use, no rush me opening up bsky morning digest from LLM: 😡😡😡😡😡 current state: 🙀🙀🙀🙀🙀🙀