Tap Notes: The Degraded Path
Two items today, which is the right number when only two are worth your time. Both are about what happens at the checkpoint. One asks whether the human can still answer a question about the code. The other asks what the code does when the check itself breaks.
Show HN: Sphinx – A hook that quizzes you on your AI’s code before shipping
Sphinx is a free, open-source hook for your coding agent workflow. Before a push, it generates a questionnaire from your diff and checks whether you understand how the code you’re about to ship works. It’s at 211 points on Hacker News, with a lively comment thread.
Why it matters: Most agent-review tooling asks a second model to check the first one’s work. Sphinx asks whether the human can still participate. If you can’t answer basic questions about a diff your agent wrote, you aren’t reviewing it. You’re rubber-stamping it, and the green checkmark you get afterward is worse than no checkmark. A quiz is a blunt instrument, and I’d expect people to learn to game it. Still, someone built the discipline answer instead of writing another essay about cognitive debt. The cost is friction, and friction is the point.
UpdraftPlus Patches a Site-Takeover Vulnerability (June 2026)
In June, the WordPress backup plugin UpdraftPlus fixed CVE-2026-10795, an unauthenticated authentication bypass (CVSS 8.1) in versions 1.26.4 and earlier. On sites previously connected to its remote-management service, forged RPC requests ran with administrator privileges. That meant malicious plugin uploads and arbitrary code execution. The fix landed in 1.26.5.
Why it matters: The patch is old news, and the bug class isn’t. RSA decryption failed, the return value went unchecked, and the code fell through to a deterministic fallback configuration. The attacker never has to break RSA. They only have to trigger the failure branch, and that branch is reproducible by construction. It’s if (!verify()) { /* log and continue */ } wearing a cryptography costume.
The dangerous bugs usually aren’t in the strong path. They’re in the degraded path: fallbacks, defaults, error branches that “gracefully” keep going. Agent guardrails have the same shape. The defense holds until an edge case arrives, and then the system continues with attacker-controlled input. Fail-closed is a discipline, not a default.
The second lesson is stored authority. Forged requests ran as whichever admin had connected the service, possibly years earlier. A connection made once becomes a standing privilege for anyone who can ride it, which is also the problem with long-lived API tokens and overpermissioned CLI tools. And a backup plugin needs deep filesystem and database access by design, so when one fails, the damage reaches everything.
Put the two items side by side. Sphinx is a checkpoint that fails closed on purpose: it won’t let you through until you prove something. UpdraftPlus is a checkpoint that failed open by accident. If you’re building a gate for agents, test the branch where the gate itself breaks.
🪨