As one of the original co-authors of PHP, I’m used to seeing PHP take its share of heat whenever a high-profile vulnerability makes headlines—most recently with PHP2Shell (CVE-2026-109618 / CVE-2026-109619).
Critique is healthy, and runtime security always needs to improve. However, treating this as a "PHP problem" misses a much bigger shift happening across the entire software industry right now.
We are entering an era where autonomous AI agents are fundamentally changing vulnerability discovery and exploitation. Researchers and adversaries alike are using agents to audit millions of lines of complex, low-level C, C++, and JIT runtime code—uncovering deep-seated memory corruption bugs that sat hidden for years, and compressing the time from discovery to working RCE exploit from weeks to hours.
Look at just the past few weeks across other major ecosystems:
- Node.js & .NET (Node2Shell / CVE-2026-111497): A critical out-of-bounds write in the native Brotli compression decoder bundled in Node.js (and also requiring out-of-band patches in .NET 8, 9, and 10), enabling unauthenticated RCE simply by sending a malformed compressed HTTP payload.
- Java (Java2Shell / Java4Shell / CVE-2026-114938): A critical heap buffer overflow in OpenJDK’s HotSpot JVM hardware-accelerated Base64 decoder (java.util.Base64), exposing default enterprise Java stacks to unauthenticated RCE via crafted Base64 strings.
- Python (CVE-2026-112900): A critical 9.2 CVSS unauthenticated RCE in the ubiquitous Pillow library triggered by crafted image uploads.
None of these are flaws in developer application code—they live deep in the foundational runtimes, standard libraries, and native dependencies that every modern stack relies on.
The takeaway: every mature runtime carries legacy C/C++ or JIT attack surface that AI agents can now probe at unprecedented scale. The real lesson for all of us—regardless of stack—is that we have to use these same agentic capabilities defensively: to audit core runtimes continuously, harden memory-unsafe boundaries, and shrink patch-deployment windows to match machine-speed exploitation.
New in macOS 27.3 beta 2: You can now migrate existing Exchange accounts using EWS over to Graph!
for key in GraphAuth GraphContacts GraphExchangeSync GraphMail GraphMigration; do
defaults write -g "$key" -bool true
done
Known Issues from Apple:
• Notes folder structure modifications will be preserved on Mac computers but not on iOS devices.
• It is not recommended to test consumer Outlook or Hotmail accounts. Local Notes data may be lost due to a server-side error.
Notes from Apple:
• Before testing, your Exchange admin must grant admin consent for “Apple Internet Accounts” in your organization. ID: f8d98a96-0999-43f5-8af3-69971c7bb423
• If the new Graph defaults are removed, accounts will no longer be able to sync until the testing profile is reinstalled. To continue using Exchange Web Services (EWS), the account will need to be removed and added again.
• Accounts added in macOS 27.3 beta without the defaults added will continue to use EWS.
To restore to default:
for key in GraphAuth GraphContacts GraphExchangeSync GraphMail GraphMigration; do
defaults delete -g "$key"
done
What if Jensen Huang manufactured the entire scandal himself so he could get the Board to fire him and he can play GTA VI in peace after a 13 year wait?
People are going to die because of this. It’s impossible to know what critical systems Quad9 or any other resolver are built into. Some are about to stop working. France’s copyright cops and the courts that enable them are about to have blood on their hands.
Samsung has been gradually losing smartphone market share against the iPhone for years. Samsung has no legitimate response to iPhone. Instead, they run these ineffective ads that only raise awareness for iPhone.
I CANNOT believe the report: it proves that eMudhra is a clown show, and was never fit to be a CA:
The point of a HSM (hardware security module) is that the private key NEVER leaves it. Guess what eMudhra did: it turned off FIPS mode (WTF?!) and copied out the private key 😱
“Hint of Lime” is an astonishingly dishonest name for a tortilla chip that tastes like it was manufactured during an industrial accident at a lime processing facility
Why would anyone trust Nvidia's "independent investigation" into Jensen Huang following news that the company apparently intervened to intimidate Commerce Dept. officials who were conducting their own inquiry? https://t.co/uuIjvixKLE