Notes from
the red side.
CVE-2026-123790: ComfyUI-Easy-Use Unauthenticated RCE via the Preview Save Route
The handler had a containment check. It checked the folder, then joined an attacker-chosen filename onto it, then wrote somewhere else entirely. A copy of the same code in its parent project had been fixed two years earlier.
What this notebook actually covers.
- Notes published
- 104
- CVEs disclosed
- 13
- Labs solved
- 87PortSwigger
- XSS
- 24
- SQL Injection
- 17
- Vulnerability Research
- 13
- Authentication
- 11
- Access Control
- 10
- Business Logic
- 10
- CSRF
- 10
- API Testing
- 5
- Active Directory
- 1
- Cloud / AI
- 1
- Methodology
- 1
- Web
- 1
CVE-2026-105744: Docling Arbitrary File Read/Write via Untrusted TikZ
Docling validated every path it copied into the build directory, then handed the document to a Turing-complete typesetter that opens files on its own authority. The guard was real; it was just in the wrong layer.
CVE-2026-86775: knowns Path Traversal via the Document API
The same unsafe filepath.Join that produced one CVE through the MCP tools produced a second one through the HTTP Document API — this time with write, delete, and directory creation attached.
CVE-2026-86543: knowns Unauthenticated Management API Exposure
A developer tool that binds 0.0.0.0, disables its own auth middleware when no password is set, and exposes an unauthenticated tunnel-start endpoint does not just have an exposure problem — it has a self-publishing one.
CVE-2026-86544: knowns Authorization Bypass via Misclassified Code Actions
The permission system worked exactly as designed. It just had the wrong answer to the only question that mattered: is code.replace a read or a write?