Anthropic says it proved no crashes across 239 entry points in 123 libraries
Anthropic said it proved there were no crashes for 239 entry points across 123 OSS-Fuzz libraries, in work with software verification company Theorem. The publication is dated October 22, 2026.

Key takeaways · 4
- 01
The claimed scope is 239 entry points across 123 OSS-Fuzz libraries—not a claim that the libraries are entirely bug-free.
- 02
The proofs concern compiled RISC-V instructions, with assumptions including a single-threaded static binary, fixed memory budget, and RISC-V/Linux environment.
- 03
The specified property covers every input under 64 MB and every modeled Linux response and memory layout.
- 04
Anthropic says it will publish a subset of proofs and relevant semantics; Theorem offers the verification pipeline to other open-source projects.
What the proofs establish
Anthropic says the proofs establish that covered programs exit normally without memory-safety errors or failed assertions.[1] The property is stated to cover every input under 64 MB and every modeled Linux response and memory layout.[1] These are proofs about compiled RISC-V instructions, rather than direct proofs over source code.[1] Anthropic describes the work as, to its knowledge, the first large-scale AI formal-verification effort on production software at the assembly-code level.[1]
The scope and assumptions
The project covered 239 entry points across 123 OSS-Fuzz libraries, and Anthropic says it carried out the work for hundreds of projects in Google's OSS-Fuzz initiative.[1] The proofs assume each program is a single-threaded static binary with a fixed memory budget, running on RISC-V and Linux.[1] Anthropic reports about 180 million lines of Rocq across the project, with a typical proof containing about 600,000 lines; binaries covered by a typical proof had a median length of 18,000 RISC-V instructions.[1]
Bugs found—and what remains unproven
Anthropic says the proof attempts surfaced hundreds of bugs, including logic bugs that do not cause crashes.[1] Reported examples include a decompressor counter underflow leading to an out-of-bounds write on inputs around 20 MB with a rare layout, and an image-decoder out-of-bounds read requiring a 64 MB input and more than 2 GB of memory.[1] Claude also rediscovered CVE-2026-56132 in libexpat, which required deeply nested input.[1] Anthropic cautions that the libraries are not necessarily bug-free.[1]
Verification and next steps
Anthropic says the Rocq checker verifies each completed proof against its specification, and that developers need to trust only certain artifacts.[1] The company says it is publishing a subset of the proofs and the RISC-V and operating-system semantics, along with complete proofs for fuzz tests that needed no patching and specifications for tests it could not prove.[1] Theorem offers to run the same pipeline for other open-source projects.[1] Unite.AI reports that Anthropic penalized patches and logged and audited them to reduce reward-hacking risk.[2]
Anthropic says the proofs establish defined properties for covered binaries under stated assumptions. Teams should treat the results as evidence about those binaries and conditions—not as a blanket security guarantee.
Why it matters
Bring this to your team — one session a day, built for your industry.
kju.ai is built for teams: daily sessions, team analytics, and rollout support for your organization.
For teamsHow this developed
23 October 2026
Anthropic says it proved no crashes across 239 entry points in 123 libraries