I have taken apart 221 advisories since April. I filed every one under the mistake it repeats. There are seventy mistakes in the drawer. Six of them hold 129 of the files. The industry does not have a vulnerability problem. It has six habits and a press office.
221 Case Files. Six Mistakes Are Behind 129 of Them.
pattern
A component whose bug-class keeps recurring. Patches address symptoms; the design holds the primitive.
That is the one-line definition of Design Debt Driver, the fattest folder in the cabinet. Seventy of the 221 files are in it. Nearly one advisory in three is a vendor fixing the same component again and calling it news.
How the count works
Every case file on this site is one advisory, read down to the diff. Each one gets tagged with the pattern it repeats, and some earn two; the average is 1.69. So the folder sizes below overlap and add to more than 129. The 129 is distinct files: a file in three of the six folders counts once. Every number here traces to a signed post you can open. If you think a file is in the wrong folder, the folder page lists every file in it, so go and argue with the diff.
Here are the six.
1. The same component, again (70 files)
Design Debt Driver. The bug is not in a line. It is in a decision the vendor made years ago and will not unmake, so the patches arrive in a series.
Apache ActiveMQ shipped a patch that denied one URL scheme. Six weeks later the same line denied fourteen. Then row two of that fourteen-row deny list got its own CVE. Ivanti's end-of-life branch served as a threat group's lab. Google's V8 compiler took a parameter named elidable and did not read it.
A deny list is a vendor writing down the attacks it has heard of. The attacker reads the list and picks number fifteen.
2. The feature is the bug (25 files)
Unpatchable Primitive. The thing being exploited is the thing the product is for. You cannot patch it out, so the vendor patches around it, forever.
vm2 is a sandbox for running untrusted JavaScript inside Node, and it has four independent defenses for a leak that lives in Node. PHP-CGI filtered a feature in 2012 and removed that feature in 2024, twelve years of filter later. Langflow has an endpoint named validate that compiles and runs the code it was asked to validate.
When the fix is "remove the feature", the previous fixes were theater.
3. Internal, because we said so (23 files)
Internal Only By Convention. Something is meant for the inside: a header, a route, an install script, a debug endpoint. Nothing enforces that. The name is the gate.
Weaver E-cology shipped an endpoint named debug, and the patch was a deletion. Chamilo's installer was install-only by filename. Nginx-UI put its install route on the public router and gated it with a clock. GPUStack shipped a flag named --force-auth-localhost that defaulted to false.
A comment that says "internal" is documentation. The network does not read documentation.
4. The data gets a vote (22 files)
Content Is Command. Outside content reaches an interpreter that treats it as instructions. Prompt injection is the fashionable instance. The pattern is as old as deserialization, and the AI tooling crowd is speedrunning it.
Flowise has a function named convertToValidJSONString that is eval. graphql-ruby loaded a schema by compiling it. In protobufjs, a type name was JavaScript. Oracle's PeopleSoft hub deserializes anyone, because it was built to deserialize its agents.
5. The key is the door (18 files)
Trust Inversion. The credential, token, or tool that was supposed to protect the system is the way in.
PAN-OS encrypted an authentication cookie with the TLS certificate, which is the one thing every visitor is handed. MagicMirror has a setting named hideConfigSecrets that hides them in one route and expands them in another. The Yarbo robot's message broker is not anonymous; the password is in the app.
6. Two copies, one check (18 files)
Parallel Implementation Gap. The same capability is written twice. One copy runs the security check. The other copy was written on a different day.
Astro shipped two /_image endpoints, and only one read the allowlist. MLflow's basic auth gated the Flask app and left three FastAPI routers open. Vite's file route returns 403; its WebSocket returns the file. LiteLLM patched one of four Jinja2 prompt managers.
What the six have in common
None of the six is a clever attack. Each needs the vendor to do, once more, a thing the vendor had already been caught doing.
That is why the advisories read alike. "Improper input validation." "A crafted request." "We are not aware of exploitation." The template hides the only useful fact, which is that this is the fourth time.
What to do with this
If you buy software: when an advisory lands, do not ask how bad it is. Ask which folder it is in and how many times that vendor has been in that folder. The vendors board keeps that count. A vendor on its third Design Debt Driver file in one component is telling you about the fourth.
If you ship software: you already know which of the six is yours. It is the one you just felt defensive about.
And if you want to check whether any of this is more than attitude: every vendor with enough files gets a plan, and every plan ends in a dated, signed prediction of that vendor's next advisory. Misses stay on the page.
Seventy mistakes in the drawer and the industry keeps reaching for the same six. Stop asking what the bug was. Ask which time this is.