Nicholas Carlini and coauthors argue in Anthropic’s post for faster vulnerability defence

Nicholas Carlini and coauthors argue in Anthropic’s post for faster vulnerability defence

Nicholas Carlini and coauthors published this post on February fifth, twenty twenty-six, arguing that Claude Opus 4.6 can find high-severity vulnerabilities in well-tested open-source code without specialised setup. Unlike fuzzers, which test code with many inputs, Claude can inspect code and past fixes to look for similar bugs that remain. The authors report that it found vulnerabilities in projects tested for years, and say they validated findings before reporting them. Human researchers validated the vulnerabilities and wrote initial patches; external researchers helped as the work grew. The authors conclude that language models can add value alongside existing discovery tools, while creating a dual-use risk: they can aid defence or misuse. Anthropic describes new detection and enforcement measures, including possible real-time blocking of traffic it detects as malicious, while acknowledging this could hinder legitimate research and defensive work. The authors warn that industry-standard 90-day disclosure windows may not keep pace with the speed and volume of findings. They also forecast that models may soon exceed expert human researchers in speed and scale. How disclosure practices and misuse controls can keep pace without obstructing legitimate security work remains unresolved.

Publication: c7a76c40-8fae-feb6-95c2-59fcb9be0248

attribution — pass: The reading attributes the post to Nicholas Carlini and coauthors at Anthropic, matching the byline, and frames claims as the authors' or Anthropic's statements. The page notes a February 6 edit that updated the author list. Naming the first listed author with coauthors stays consistent with that list.

Nicholas Carlini*, Keane Lucas*, Evyatar Ben Asher*, Newton Cheng, Hasnain Lakhani, David Forsythe, and Kyla Guru

summary — pass: The summary leads with the authors' central argument and explains fuzzers and dual-use risk in plain terms. It covers validation, safeguards and their admitted friction, the disclosure-window warning and the attributed forecast. The question follows from the source's own concerns. The 500-vulnerability figure is omitted, but its absence does not distort the reading's meaning.

Our view is this is a moment to move quickly—to empower defenders and secure as much code as possible while the window exists.

date — pass: February 5, 2026 matches originalPublished at day precision. The kind is publisher-page, so no archive disclosure is needed. The forecast about exceeding human researchers is reported as the authors' forecast. The reading does not rely on any passage from the later page modification (dateModified October 2026). The only in-text edit note concerns the author list.

Edited February 6, 2026: Updated the author list

support — pass: Each claim is supported by passages from the main article body. These cover out-of-the-box discovery, human validation and patching, admitted friction from real-time intervention, and the 90-day disclosure warning. The memory-corruption limitation is also source-supported. The cited body text appears to be original article content rather than a later edit. Source-grounding here does not independently verify the real-world claims.

Claude Opus 4.6 can find meaningful 0-day vulnerabilities in well-tested codebases, even without specialized scaffolding.

media — pass: No media is selected, and no verified media candidates were supplied, so nothing is misidentified or irrelevant.