· 07:00 · 7 min + 2 min Explained

AI helped find two serious holes in PHP, and the fix is out

PHP, which runs most websites, patched two severe flaws that AI models helped find. Also: attackers chase AI keys, a new Claude API version, and Europe's compute gap.

Written by AI and checked against our editorial standards. Every claim links to its primary source. Not reviewed by a human editor.

Get it in your inbox at 7am every day ↓

Today in 60 seconds

  1. PHP fixed two severe flaws that let attackers take over servers, and AI models helped find them. Anyone with a WordPress, Drupal or other PHP site.
  2. A poisoned LiteLLM update stole keys, and Railway says customer secrets may have been read. Developers who store AI API keys on servers or platforms.
  3. Claude's API has its first new version since 2023, and the new SDKs use it by default. Developers who build on Claude.
  4. Europe has about 5% of the world's AI compute, and Mistral plans to release Large 4's weights this month. European companies that want AI on their own servers.

1. AI helped find two serious holes in PHP, and the fix is out

Big dealGeneralBuild1½ min

70%of all websites run on PHP, according to Wiz

The short versionPHP, the language behind most websites, fixed two severe security holes on 21 October. AI models helped find them, so update now.

PHP runs WordPress, Drupal and Joomla, and with them a large part of the web. So a hole in PHP itself is a hole in millions of sites at once.

On 21 October, PHP released fixes for two flaws that let an attacker run their own code on a server without logging in. They score up to 9.2 out of 10 for severity. Security firm Wiz says nearly every PHP version back to 5.4 is affected.

AI helped with much of the finding. Calif found one flaw with OpenAI’s GPT-5.6 Sol, as part of OpenAI’s Patch the Planet program. Wiz used Gemini 4 Argon and GPT-5.6 Sol, and showed working attacks on WordPress, Drupal and Joomla.

The release did not go to plan. The flaw IDs leaked online, and Calif published a video of a working attack by mistake. So PHP moved the release forward by a day. The US NSA advised taking sites offline if they cannot be patched, TechCrunch reports. No attacks had been reported when the fixes came out.

Why it matters

Fitting an attack to each PHP version used to be slow, hard work. "With AI this is no longer a barrier," Wiz writes. AI is like a locksmith who works for both sides, so the time between a fix and the first attack is shrinking.

Do this: Update PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35. If a web host runs your site, check that it has done so.

Source: thephp.foundation · Official · wiz.io · Official · techcrunch.com · Reported

2. Attackers go after the keys that pay for AI

Big dealBuild1½ min

The short versionA poisoned update of LiteLLM, a popular AI tool, stole passwords and keys. Hosting platform Railway says attackers may also have read its customers' secrets.

An AI API key works like a company credit card. Whoever holds it can run up a bill or reach your data. Two attacks on 21 October went after exactly those keys.

1 of 2 A poisoned LiteLLM update

LiteLLM sits between apps and AI models, so it often holds the keys to many AI providers. On 21 October, version 1.107.0 appeared on PyPI, Python’s package store, with hidden code. It ran every time Python started, even if LiteLLM was never used. It collected SSH keys, cloud passwords and the AI keys stored in LiteLLM’s database. PyPI pulled the release within two hours.

2 of 2 Railway’s customer secrets may be out

Railway, a platform for hosting apps, says someone may have read the settings where customers keep their secrets. For some secrets, the attacker may have got the decrypted values, such as API keys and database passwords. Railway thinks this is part of “a series of attacks” on platforms like itself, with AI providers as the end target. It has paused all deployments and warned those providers. Railway does not link its breach to LiteLLM.

Why it matters

A stolen AI key pays off at once, because the owner pays for every call. Wiz saw attackers testing stolen credentials about 4.5 hours after the theft. So attackers move within hours, not days.

Do this: If you installed LiteLLM 1.107.0 or use Railway, rotate every key that machine or project could reach. Pin LiteLLM to 1.106.2.

Source: safedep.io · Reported · wiz.io · Reported · blog.railway.com · Official

3. Claude’s first new API version since 2023 drops some old settings

Worth knowingBuild1½ min

The short versionClaude's API has a new version, and the new SDKs use it by default. Upgrading can break code that sets temperature or runs behind a proxy.

Every request to Claude’s API carries a version date. Until now it was 2023-06-01. On 21 October, Anthropic released version 2026-10-21. New major SDK versions, such as Python 2.0.0 and TypeScript 1.0.0, send it automatically.

Two changes can bite. First, sending temperature, top_p or top_k now returns an error, even at the default value. These settings control how random the answers are. On older models such as Claude Sonnet 4.6, code that lowered temperature for steadier answers loses that effect. Second, the SDKs now send your key in the Authorization header instead of X-Api-Key. A proxy that reads the old header will stop working.

Nothing changes until you upgrade, and a request can stay on the old version.

Why it matters

Claude 4.7 and later models already accept only the default values. So the new version is like a car maker removing a dial that was already locked in one position. Old code that still reaches for it now gets a clear error instead.

Do this: Before you upgrade the SDK, search your code for temperature, top_p and top_k, and check any gateway that reads X-Api-Key.

Source: platform.claude.com · Official · platform.claude.com · Official

4. Europe has little AI compute, and Mistral’s largest model is about to open

Worth knowingEurope1½ min

The short versionEurope has about 5% of the world's AI computing power, AP reports. Mistral plans to release the weights of its huge Large 4 model at the end of October.

To train and run AI you need computing power, and most of it sits in the US. That set the tone at Nvidia’s conference in Berlin on 21 October.

1 of 2 Nvidia in Berlin

Europe has about 5% of the world’s AI computing capacity, against 75% in the US, AP reports. Nvidia’s CEO Jensen Huang said the company invested $10 billion in European startups and partners in the past year.

2 of 2 Mistral Large 4 trained in Europe

French lab Mistral says it trained Mistral Large 4 on 3,800 Nvidia chips in its own European data centers. The model has about 1 trillion parameters, and 49 billion of them work on each word. It is in public preview now, and Mistral plans to release the weights at the end of October. Mistral’s post does not name a license.

Why it matters

Downloadable weights are like owning the recipe instead of ordering takeaway. A European company can run the model on its own servers, so its data never has to leave for a US cloud.

Source: abcnews.com (AP) · Reported · mistral.ai · Official

Open source & local AI

Flint is a free coding model built to run on your own computer

Worth knowingBuildEurope1 min

The short versionAI lab Recursive released Flint, an open coding model for agents. It is a 23 GB download in Ollama, and only a small part of it works on each word.

Coding agents read and write a lot, so running them through a paid API adds up. A model on your own machine costs nothing per task, and your code stays private.

Flint has about 40 billion parameters, but only about 2.5 billion work on each word, so it is fast for its size. It comes under the Apache 2.0 license, and Ollama can start it inside Claude Code with one command.

Recursive reports 74.2% on SWE-bench Verified, a common coding test. Those are its own numbers, and nobody else has checked them yet.

Why it matters

Think of a large firm where only the right specialists join each meeting. You get the knowledge of a big model at the running cost of a small one. That is why a model this size can run fast on your own machine.

Try it: Run ollama launch claude --model flint to use Flint in Claude Code.

Source: huggingface.co · Official · ollama.com · Official · blogs.nvidia.com · Official

Paper of the day

Agents get cheaper when they trim their memory instead of rewriting it

Worth knowingBuild1 min

The short versionResearchers let AI agents delete old tool output straight from the model's working memory. That cut costs by 27.7% and scored slightly higher than summarizing.

A model keeps a cache of what it has already read, so it does not have to read it again. But when an agent rewrites its history to make it shorter, the cache no longer matches. Then the model must read everything again, and you pay for it.

Tianyu Fu and colleagues tried another way. They let the agent drop parts of the cache directly, such as old tool responses, and keep the rest as it is. A matching serving engine, AKV, handles this behind a normal API.

Compared with summarizing once the history gets long, dropping old tool responses cut the average cost by 27.7%. Benchmark scores rose by 1.7 points. It needs their own serving engine, so it is research for now.

Why it matters

It is like clearing old papers off your desk instead of copying all of them into a short summary. You keep your place, and you only lose what you no longer need.

Source: arxiv.org · Official


Explained: if you have a little more time

3 terms from today's news · 2 min

What is coordinated disclosure?

From story #12 min
Coordinated disclosure is the process for handling a newly found security hole. The finder reports it to the maker in private, the maker builds a fix, and everyone announces it together. The steps are simple. A researcher finds a flaw and reports it to the maker, or to a body such as the US agency CISA. The maker checks the report and builds a fix. The flaw gets an ID, called a CVE number, so everyone can refer to the same problem. Then the fix and a public warning are published at the same time. > **Think of it like this:** you notice that a shop's back door does not lock. You tell the owner quietly, not the whole street. Once the lock is changed, the owner can tell customers what happened. Where the comparison fails: with software, millions of "shops" share the same door, so they all need the new lock on the same day. The quiet period is the hard part. If the maker does nothing, the warning can still go out after a while. CISA, for example, may publish as early as 45 days after it first tried to reach an unresponsive maker. If details leak early, attackers get a head start while users still have no fix. AI is putting pressure on this system. AI models now help researchers find flaws faster, so makers receive more reports. The same models can also help attackers turn a short warning into a working attack quickly. **Why it matters to you:** when a security update arrives with a warning, the clock has already started. The details are public, so install the fix soon.

Two more from today

What is a mixture-of-experts (MoE) model?Why huge models only use a slice of themselves for each word.

A mixture-of-experts model is split into many smaller specialist parts, called experts. For each word it writes, a small router picks only a few of them to do the work.

So a model can have hundreds of billions of weights in total but use only a fraction per word. That makes it much faster and cheaper to run than a dense model of the same size.

What does "open-weight" mean?What you get when a model's weights are public, and what you don't.

An AI model is a huge file of numbers called weights. “Open-weight” means anyone can download that file and run the model on their own machines, instead of renting access through an API.

It is not the same as open source: the training data and code usually stay secret, and the license can set limits.

How sure are we?Official: from the company, regulator or authorsReported: from a named outletUnconfirmed: rumor or leak