-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 NEFARIOUSPLAN-CANONICAL-V1 {"body_md":"> The patch removes three lines. The CVE names one.\n\nThat is the last line of [CVE-2026-30824: Flowise's Auth-Bypass Whitelist Has No Criterion. The 3.0.13 Patch Removes Three Lines.](/posts/flowise-cve-2026-30824-whitelist-has-no-criterion). Read on its own it describes one advisory. Read next to the other two files on this vendor it describes the shape of every advisory.\n\n## Flowise picks the shorter line.\n\nI have read these three case files back to back. The habit does not hide. Flowise does not miss bugs. Flowise picks the primitive that is already in the file over the primitive that would be correct, ships, and when the shortcut lands a CVE, patches only the thing that broke. The function that returned the entity gets a runtime scrubber. The list that had no criterion loses three lines. The parser that was an interpreter gets a different interpreter.\n\nThree files, three CVEs, three patches, one editorial move. The admission is the smallest possible.\n\nThe correct primitive was available every time. The vendor reached one line shorter.\n\n## The function returned the whole row.\n\n[CVE-2025-58434: Flowise Sent the Reset Token to the Inbox. It Also Sent It to the Caller.](/posts/flowise-forgot-password-token-in-the-response) is the password-reset endpoint that handed the token back to the caller in the HTTP response, next to the bcrypt hash and the expiry. A second channel existed. The email was fine. The JSON was the problem.\n\nThe fix is `sanitizeUser`, three `delete` statements on a mutable entity.\n\n> `sanitizeUser` is a denylist: three columns the author remembered to scrub.\n\nThe author had TypeORM. TypeORM supports DTO mapping. class-validator was already in the dependency graph. A typed response object would have made the function's signature itself refuse the conflation. The author deleted three fields and moved on. The next sensitive column on the User entity is a CVE waiting for someone to add it.\n\n## The whitelist was never a category.\n\n[CVE-2026-30824: Flowise's Auth-Bypass Whitelist Has No Criterion. The 3.0.13 Patch Removes Three Lines.](/posts/flowise-cve-2026-30824-whitelist-has-no-criterion) is the auth-bypass surface named `WHITELIST_URLS`. Login flows are on it, because login has to be reachable before authentication. Health probes are on it, because the load balancer has to decide. The NVIDIA NIM container-control routes were on it, because somebody added them. The middleware does not read why an entry is on the list. It reads that one is.\n\nThe JWT branch of the middleware existed already. UI traffic sent `x-request-from: internal` and got verified against a cookie. That is the correct primitive for a route the UI alone should call. The developer did not use it.\n\n> The mechanism for expressing that intent existed in the codebase already; the JWT branch was already there. They did not use it. They used the whitelist, because the whitelist was the simpler thing to add a line to.\n\nThe 3.0.13 patch did not add a criterion to the list. It created a second list, `API_KEY_BLACKLIST_URLS`, whose only entry is the one route the CVE named. Two other entries were removed from `WHITELIST_URLS` in the same commit, the vector-upsert route and the Prometheus scrape, and neither has a public CVE assignment that surfaces under the release notes. The advisory picked the loudest one. The commit knew about three.\n\n## The parser was the runtime.\n\n[CVE-2025-59528: Flowise's convertToValidJSONString Is eval. The Patch Is JSON5.](/posts/flowise-converttovalidjsonstring-is-eval) is the Custom MCP config field that ran whatever the authenticated user typed, because the function that lifted JS-style object literals into JSON called `Function('return ' + input)()`. The function name was the admission. The input is not valid JSON. The author needed something that would accept JSON-ish. The author reached for the JavaScript runtime.\n\n> The bug was not what the input contained. The bug was that the parser was the JavaScript runtime.\n\nJSON5 was on npm before this integration existed. The 3.0.6 patch is `import JSON5 from 'json5'` and one expression swap. The function keeps its name. The function keeps its contract. The function still accepts JSON-ish text through a permissive parser. The fix picked a parser whose permissiveness does not include a shell.\n\n## The same move, three times.\n\nThree services. Three primitives. One habit.\n\nThe entity was the response object. The list was the auth decision. The runtime was the parser. Each time, two different responsibilities were loaded onto one primitive because that primitive was closer to hand than the correct one. Each time, the correct primitive was available in the same codebase, on npm, or one import away. Each time, the fix did not separate the responsibilities. It changed what the single primitive emitted, accepted, or listed.\n\nThat is a style. It is a style the vendor has not acknowledged and has not retired. The 3.0.6 release tagged on September 15, 2025 shipped fixes for two of these advisories inside the same version bump. The style survived the release, because the fixes are the shape the style produces.\n\n## Where the charge does not reach.\n\nThe fixes land. GHSA-wgpv-6j63-x5ph was published September 12, 2025 and v3.0.6 was tagged September 15, 2025, three days later. PR #5167 is one line on the return statement and a small, precise helper. PR #5913 hardens the reset-password comparison against an empty-string bypass six months later. The 3.0.13 whitelist patch removes three lines and creates the second list in one commit. The maintainers merge the patches. The patches work for the instance each one names.\n\nThe MCP stdio capability is not the vendor's fault. MCP-over-stdio runs commands on the host as a documented capability of the protocol. The planned mitigation to deprecate stdio and allow only remote MCP by URL closes a capability of the protocol, not a Flowise bug. The charge is `convertToValidJSONString`, not stdio.\n\nThe ORM is not the vendor's fault. TypeORM round-trips full rows because that is what an ORM does. The JSON serializer walks reachable fields because that is what a serializer does. The service was supposed to type its boundary and did not.\n\nThe canvas is a legitimate thing to build. The sharing model is a legitimate thing to ship. The NIM integration is a legitimate thing for an LLM platform to offer. The charge is not any of those products. The charge is how the lines go in.\n\n## The next one is in three files.\n\nOpen `packages/server/src/utils/constants.ts`. Read the `WHITELIST_URLS` entries. For each one, say out loud what makes it belong on a list that skips authentication. If the sentence is \"login has to be reachable before login,\" it belongs. If the sentence is \"we did not want Prometheus's scraper to need an API key,\" it does not belong, and in the 3.0.13 commit it was removed. Any entry added after that commit is the next line to check. The constant is the admission surface.\n\nOpen `packages/server/src/utils/sanitize.util.ts`. Count the `delete` statements. Open the User entity and count the columns. If the User entity has grown since the sanitizer shipped and the sanitizer has not, the gap is the surface. Any controller that calls `res.json(user)` without routing through the sanitizer is the next instance.\n\nOpen the service files under `packages/server/src/services/nodes/` whose node accepts a configuration blob. Look for the parse step. If the parse runs through anything other than `JSON.parse` or `JSON5.parse` on user-shaped text, read the function. If it runs through `Function`, `vm.runInThisContext`, `eval`, or a string-concatenated code path, the node is the next instance. The permissive parser is the end of the symptom. It is not the end of the question.\n\nThe function names recur. A list whose name is `WHITELIST_URLS` or `ALLOWED_PATHS` and whose entries were added one at a time. A scrubber whose name is `sanitizeX` and whose body is a fixed number of `delete`s. A converter whose name begins with `convertTo` or `normalize` and admits that the input is not what it should be. The symptoms name themselves consistently. The style that produces them is the thing to watch.\n\n## The next advisory is one of two shapes.\n\nThe next Flowise advisory will be one of two shapes.\n\nEither a new sensitive column added to the User entity after September 2025, returned through a controller whose path did not route through `sanitizeUser`, found in an endpoint the maintainers did not update when they added the three deletes. The CVE will be high severity. The PoC will be two unauthenticated HTTP requests. The fix will be a fourth `delete` in `sanitize.util.ts`.\n\nOr a new entry added to `WHITELIST_URLS` after the 3.0.13 cleanup, added for a reason that reads sensibly on the commit line, exempting a route that calls into a privileged subsystem on the host. The fix will remove the entry and leave the whitelist's selection criterion still unwritten.\n\nIf a third shape arrives, it will be a function whose name begins with `convertTo`, `parseAs`, or `normalize`, and whose body treats a JavaScript primitive as a general-purpose interpreter for user-shaped text. The fix will swap the primitive. The function will keep the name.\n\nYou wrote `convertToValidJSONString`. You wrote `sanitizeUser`. You wrote `WHITELIST_URLS`. Each name admits that the thing it does is a workaround for the thing it should be. You have shipped the admission three times, and you have patched the admission three times by changing what sits inside the name.","closing_line":"The name is the bug. Rename it, type it, or split it, and the next advisory writes itself.","hook_md":"Three Flowise advisories, three one-line patches, one habit the advisories never name. The vendor keeps picking the primitive that is already in the file over the primitive that would be correct, and the next CVE gets the fix sized to the smallest admission the commit can afford.","post_id":869,"slug":"the-nefarious-plan-of-flowiseai","title":"The Nefarious Plan of FlowiseAI","type":"editorial","unreadable_sentence":"The vendor reached one line shorter."} -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQRf0htP5+SjynlxywneZjl4jgkQJgUCavqSTAAKCRDeZjl4jgkQ Jt9OAP46cYGTZSAOBLWrIxc7mkADezcsWvrdZyOw/ykgmKENNgEA7+XtejXmptAn C7OiiriXDeFRDtL8wa4dWDh6Obrxxg4= =ryXB -----END PGP SIGNATURE-----