The "vulnerable window" risk check
Technique
Judge a security bug by two things: how long until everyone actually runs the fix, and how much access the attack gives. A bug in your own server is fixed once; one in software users install or in a library you rely on stays open until everyone updates.
Theo's current stance
Theo argues these two factors now decide how bad a bug is, because AI makes spotting and exploiting bugs nearly free.
Try it
- When a bug is announced, ask your agent: is it in our own server, or in software and libraries we must update and redeploy?
- Ask what an attacker would get: a peek at some data, or full control of a system.
- Patch first what is internet-facing and gives full control.
First seen
9:00
…the only remaining pieces are how long does it take to get the patch out and how much access does the exploit give the attackers?
Every mention
9:00
…the only remaining pieces are how long does it take to get the patch out and how much access does the exploit give the attackers?
8:11
Most importantly, how much access do you get? Is this a bug that lets you see some redacted characters from an email address or is this a bug that lets you take over a system?
Theo Daily is unofficial and not affiliated with Theo or t3.gg. Written by Claude Opus 5.5 from each video's transcript.