Bitter Frontier What coding agents just made possible, where the bottleneck moved, and what deserves attention.

Evidence record / claude-code

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-claude-code-four-repository-advisories-in-fifteen-days-disclose-earlier-fixes-plugin4shell-among-them

Four repository advisories in fifteen days disclose earlier fixes, Plugin4Shell among them as CVE-2026-86063. After three months with nothing new, the advisory list gained four entries between 2026-09-25 and 2026-10-09, each disclosing a fix that had already shipped; the three CLI fixes shipped 26 days to five months before their advisories. Plugin4Shell, fixed silently in 2.1.179, now has CVE-2026-86063 and an advisory crediting Air Security; a write-path symlink race fixed silently in 2.1.129 has CVE-2026-103435. GHSA-gfvf records that until 2.1.260, a machine holding a stored API key could run an Enterprise or Team session with no server-managed policy, or a stale one. None has reached the global GitHub advisory database at observation. The three CLI advisories have not reached npm dependency scanners yet; the Desktop advisory is outside their ecosystem. NVD already lists CVE-2026-103012 and CVE-2026-103435.

Channel: docs-only (advisory publication); the fixes are tagged-release in 2.1.129, 2.1.179 and 2.1.260, all before the window, and in Claude Desktop 1.15962.0. Half: defect. Date: 2026-09-25, 2026-09-29, 2026-10-05, 2026-10-09.

Operator consequence: The advisory list is now a delayed record, not an alert: it tells you weeks to months later that a changelog line, or a missing one, was a security fix. Fleets that relied on server-managed settings below 2.1.260 should treat policy as possibly unapplied on machines with a leftover API key and check which policy source /status reports. Watch the repository advisory page directly, because dependency scanners have not raised them yet; NVD lists CVE-2026-103012 and CVE-2026-103435. This is a dated database gap, not a claim that scanners can never report them. The changelog read line by line is still the only timely signal, and it remains incomplete.

Receipt

Finding metadata

Confidence
high

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-claude-code-four-repository-advisories-in-fifteen-days-disclose-earlier-fixes-plugin4shell-among-them

Profile citations

Source links

Primary links, including exact changelog lines when available.

  1. Claude Code
    official docs2026-10-13-claude-code-four-repository-advisories-in-fifteen-days-disclose-earlier-fixes-plugin4shell-among-themgithub.com/anthropics/claude-code/security/advisories/GHSA-pq7j-f95f-qfcvofficial docs2026-10-13-claude-code-four-repository-advisories-in-fifteen-days-disclose-earlier-fixes-plugin4shell-among-themgithub.com/anthropics/claude-code/security/advisories/GHSA-5j29-h97v-84chofficial docs2026-10-13-claude-code-four-repository-advisories-in-fifteen-days-disclose-earlier-fixes-plugin4shell-among-themgithub.com/anthropics/claude-code/security/advisories/GHSA-gfvf-j8jh-jxxwofficial docs2026-10-13-claude-code-four-repository-advisories-in-fifteen-days-disclose-earlier-fixes-plugin4shell-among-themgithub.com/anthropics/claude-code/security/advisories/GHSA-v234-4jrq-mgg6official docs2026-10-13-claude-code-four-repository-advisories-in-fifteen-days-disclose-earlier-fixes-plugin4shell-among-themnvd.nist.gov/vuln/detail/CVE-2026-103012official docs2026-10-13-claude-code-four-repository-advisories-in-fifteen-days-disclose-earlier-fixes-plugin4shell-among-themnvd.nist.gov/vuln/detail/CVE-2026-103435

Versioned source: run artifact