
A good reminder that even in a memory-safe language, a single misused CPU instruction (VMOVDQU8) is all it takes to turn Base64 decoding into an OOB write.
Java4Shell: write once, RCE everywhere calif.io/java4shell

Security REsearch @Anthropicai · Breaking & Fixing AI Failure Modes | Founder @binarly_io · @SBOM_Tools · @REhints | Author “Rootkits & Bootkits" (bootkits.io)

A good reminder that even in a memory-safe language, a single misused CPU instruction (VMOVDQU8) is all it takes to turn Base64 decoding into an OOB write.
Java4Shell: write once, RCE everywhere calif.io/java4shell

Phrack 73 just dropped. Tell your SOC you'll be busy phrack.org/issues/73/1

Anthropic is making some important changes to our Coordinated Vulnerability Disclosure policy in order to keep pace with the rapid improvement of AI driven vulnerability discovery capabilities. Starting in January we are moving to a 30-day timeline for Critical and High vulnerabilities, and 45 days for everything else. See the post linked below for more details. We know that this change may put more pressure on OSS maintainers and vendors. Given this change some important aspects of our policy are worth calling out here: * We will continue to agree to a sustainable pace with maintainers and vendors before sending a large volume of findings. * We will always include a patch or mitigation with each finding where possible. * We will work with vendors and OSS maintainers on a timeline for issues that can’t be fixed quickly. * A reminder that issues reported with no human triage, such as those from OSS-Scanner are not subject to this policy. See our FAQ for more details. We know that we cannot just patch our way to better security. Securing all of the code in the world requires a combination of language modernization, redesign, rewriting, hardening, reducing attack surface, and yes, finding and fixing vulnerabilities. But we must move at a faster pace together in order to make progress. anthropic.com/research/coord…

1/ AI is finding bugs faster than we can patch them, we hear "formally verify everything" more and more. So let’s look at the most verified kernel in existence, seL4, and what its latest release (Oct 30) fixed. 🧵

In the age of AI, 90 days isn’t fast enough. Today, Project Zero updated our disclosure policy to reflect the changes needed to protect users in this new world. projectzero.google/2026/11/d…


30 years ago today, Phrack 49 published Aleph One’s “Smashing the Stack for Fun and Profit”. A legendary paper that inspired generations of hackers and helped shape modern exploit development. Still an essential reading. phrack.org/issues/49/smashin… Phrack 73 is coming soon!

Slides from the talk @mlippautz and I gave at the recent @offensive_con in Tokyo: saelo.github.io/presentation… Blog post for the Fuzzing vs. AI part: projectzero.google/2026/10/f…

if you're interested in building next-gen sandboxing for agents, have a ton of passion/ambition for low-level systems software (OS/hypervisor), and are itching to rewrite their internals for security/performance/whatever, don't miss this: job-boards.greenhouse.io/ant…

Anthropic is releasing an open source library, FlashProve, for provable inference. It was measured on Llama 4 Maverick, a 400B-parameter mixture of experts model. Code: github.com/anthropics/FlashP… Blog post: anthropic.com/research/prova…

The uncomfortable truth is that almost everything we built for application security was designed for a different threat model, one where a human had days to think. At this scale and velocity it doesn't hold, and teaching an AI agent to drive those same tools doesn't fix it. Our prior approaches rested on pre-generated heuristics (rules, SAT/SMT) or hypotheses (fuzzing harnesses). They worked because a human could understand the problem first, define the path to a fix, then scale remediation. That luxury is gone. Discovery and remediation now need to happen almost simultaneously, and raising the bar with ineffective mitigations neither stops an AI-driven attacker nor buys time.
The window to patch software bugs is collapsing Of the bugs hackers actually exploit, ~87% are now being attacked on or before the day the bug is public knowledge That share was 23% in 2020 Charts of the Week: a16z.news/p/chart-of-the-wee…

claude found this one and built a 0-click rce chain: it takes 48min to leak a kernel pointer and defeat kaslr remotely, and another 5min to hijack the control flow and root the server over the network. patch it now (or disable mptcp).
AWWWWOOOOOOOGAAAAAAA 9.8 severity use-after-free vulnerability in the kernel’s IPv4 TCP stack just landed Time to patch! ubuntu.com/security/CVE-2026…

Code-execution flaw in UEFI firmware affects most servers on planet Earth: arstechnica.com/security/202… Great work by Alex Matrosov (Anthropic) and Dan Holmes-Mitra (Google)!

AI-assisted research is killing embargoes. Coordinated disclosure will never be the same. The industry used to have the luxury of testing or sitting on a fix for months. Not anymore. When everyone's using the same tools and the same intelligence to find vulnerabilities, you're not the only one finding that bug. Product security and PSIRT need a serious rethink: less gatekeeping, more proactive evaluation of security posture, and shipping fixes continuously at scale. The biggest impact will be in firmware and hardware, where disclosure timelines have historically stretched past 12 months. That mindset is a leftover from outdated processes and slow testing and bring-up environments.

Unfortunately, the complexity of the hardware and firmware supply chain has the same negative effect on how cryptographic artifacts are managed, or mismanaged, across the ecosystem. This is a reminder of the scale of the problem, based on just one documented data breach.
⛓️Confirmed, Intel OEM private key leaked, causing an impact on the entire ecosystem. It appears that Intel BootGuard may not be effective on certain devices based on the 11th Tiger Lake, 12th Adler Lake, and 13th Raptor Lake. Our investigation is ongoing, stay tuned for updates.

LLMs are great at finding bugs, but so are fuzzers. @5aelo compared the vulnerabilities found in V8 by BigSleep, an agentic system, with those found by the Fuzzilli fuzzer. projectzero.google/2026/10/f…