Sibling-path divergence, a bug pattern
- hypothesisevidence level
- writeup
- 2026-11-15
- #vulnmind
- #static-analysis
- #bug-class
The pattern
Two code paths do structurally similar things, and both should enforce the same security check. One does. The other does not.
It tends to appear when a feature is reachable two ways, for example through two entry points that reach the same underlying action. The check gets written into the first path, and the second path was added later or by someone else.
Where it comes from
The pattern was extracted from three reports I made to a bug bounty program. All three were closed as duplicates, which is normal in this work and means the issues were real but someone else reported them first. This document describes the shape of the bug class only. It names no product, file, line or vulnerable code, and it never will.
The detector
A static analyzer for TypeScript and JavaScript that looks for sibling paths where one enforces a check and the other does not is being built. Its status is in progress.
Status of the claim
Hypothesis. The pattern is real in the sense that it recurred three times. Whether a static analyzer can find it reliably is unproven, and no effectiveness claim is made.