PHP's patch, Muse's reopened links and an agent score each leave a job with you

This week’s three stories share one scene: someone declares the job done, and the cleanup falls to the user. PHP has patches for two severe vulnerabilities, yet on October 23 the PHP team added one more configuration line worth turning off. Meta paused Muse link sharing, then turned it back on October 22 with new addresses, while the conversation title you chose, according to Claroc, still sits in a public store of domain names. And a research preprint promises an agent (AI software that calls tools across many steps) that learns from its mistakes, with figures the authors reported themselves on three public test sets.

PHP: you have updated, but one more feature is worth turning off

On October 21, the PHP team published an advisory on two vulnerabilities that allow remote code execution without logging in, along with patches 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The simplest version check: ask whoever looks after your website which PHP version is running, then compare it with those four numbers.

On October 23, on the same php.net page, the PHP team posted a supplementary notice. They recommend setting session.upload_progress.enabled=0 (turning off the feature that reports file-upload progress within a session) until the next regular bugfix release, to block a remote-code-execution path they describe as unlikely. According to them, the bug appears only when an application sets session.serialize_handler to php_binary or php_serialize in its configuration, then switches to php at runtime with ini_set() before calling session_start(), and the progress feature is still on. An application that does not change this handler at runtime can be left as it is. The PHP team will publish the full advisory for CVE-2026-115560 with the next release. If you already applied this switch-off from the October 21 advisory, keep it as it is; nothing more is needed.

This week’s task: if someone else runs your website, ask them two questions. One, have you moved to one of the four patched versions? Two, does the application code anywhere call ini_set to change session.serialize_handler? If so, turn off session.upload_progress until the next release. If you manage the server yourself, searching the source and configuration for serialize_handler is enough to tell whether you are in this rare group.

Muse: sharing is back on, but the conversation title is not gone

Claroc, a cybersecurity company, published research on Muse, Meta’s AI assistant launched on September 8, 2026. Muse built the address of a share page from the conversation title, and that address ended up in passive DNS data (a store of the domain names that computers have looked up). Claroc says it found more than 6,800 such addresses. In its October 20 update, it said Meta told Ars Technica it would pause the feature, and that 40 links it rechecked no longer opened. Also according to Claroc, the domain names containing titles remain in passive DNS history.

Two days later, on October 22, Meta’s David Singleton wrote on X: “The underlying issue is now fixed, and sharing is back on”. Each old share link now has a new address; anyone who opens an old link sees a message asking the sender for a new one. The Verge reported it the same day, and recorded Meta saying the problem lay in the addresses of artifacts (documents and images created in Muse), not in conversation sharing.

This changes one concrete thing: for links you sent earlier, do not treat “the old link no longer opens” as the end of it. If you ever shared a Muse conversation whose title carried something like a client’s name or a salary figure, treat that title as exposed and handle it under your company’s policy. The review steps are already in Five steps to recheck every AI assistant share link you have sent, after Muse put chat titles in DNS (October 23), which also covers the 6,800 figure; what is new since then is that Muse has turned sharing back on, so anyone who needs to resend a link must get the new address. For every AI assistant you use, set a neutral title before you click share from now on. Claroc notes that many AI assistants also share by public link, and that putting the title in the address is specific to Muse. The source for this piece does not say whether Muse is available in Vietnam.

Self-Direction: an agent that “remembers its lessons”, but the scores are the authors’ own

On October 22, a group of authors posted a preprint on arXiv (a repository of research manuscripts, not yet peer reviewed) about Self-Direction. When an agent gets a task wrong, it reviews its own process, draws a lesson and writes that lesson into an adapter, a small added layer of parameters amounting to about 0.02% of the base model’s parameters. The base model’s weights are left unchanged. The adapters are stored as a library the agent can pick from and reuse for similar tasks.

The authors measured agents built on open Qwen models across three test sets: GAIA (open-ended research), Claw-Eval (tool use) and Terminal-Bench 2.1 (command-line work). They report success rates up by 8.9 to 17.0 percentage points, on par with frontier systems, and say agents repeat old mistakes less often and that the reliability of their self-repairs nearly doubled. These are results the authors reported themselves; nobody has rechecked them independently.

For people at work, there is nothing to install yet. The abstract does not say whether a product or code is available to use now. What you can use is a question: when a vendor says its agent “learns from mistakes”, ask where the lesson is stored, for how long, and whether you can inspect or delete it. If you build agents yourself, copy its repeated mistakes into a list; that is your own test set for comparing before and after any way of “teaching” it.

Three tasks for this week

1. Ask whoever runs your website: is the patched PHP version installed, and does session.upload_progress need to be turned off?

2. If you ever shared a Muse link, treat the conversation title as already public; from now on, set a neutral title on every link you share.

3. Read Self-Direction as a new idea; change how you work only when you have a test on your own tasks.

Sources

1. PHP.net, “Informational advisory: Session upload progress” (October 23, 2026) — the PHP team’s notice about the configuration line to turn off and CVE-2026-115560.

2. php-src, advisory GHSA-6wmf-4rv5-p3rp for CVE-2026-109619 — the PHP team’s October 21 advisory on the remote-code-execution vulnerability and the patched versions.

3. Claroc Research Team, “GhostShares: Muse passive DNS” (updated October 20, 2026) — research from a cybersecurity company; Meta’s statement to Ars Technica is relayed by Claroc.

4. Kansal et al., “Don’t Forget What You Just Learned: Self-Directed Repair Turns Agent Mistakes Into Lasting Lessons”, arXiv:2610.31846 (October 22, 2026) — a preprint that has not been peer reviewed.

5. David Singleton (Meta), “An update on @Muse shared artifacts” (October 22, 2026) — Meta’s statement on turning sharing back on and the new addresses.

6. The Verge, “Meta turns Muse sharing back on” (October 22, 2026) — report on Muse turning sharing back on.