CVE-2026-8182

COMPONENT VERSION RANGE

NewScan fingerprints Langflow from its response and reports this CVE when the detected version falls inside the affected range below.

ONE row for the whole 2026-08-06 IBM Langflow OSS batch, the Open WebUI precedent above: 21 ids, every one of them 'IBM Langflow OSS 1.0.0 through 1.10.3', so 21 rows would be 21 findings whose single action is the same upgrade. `cve` carries CVE-2026-8182 - not the highest CVSS (four are 8.8) but the only one that needs no credential at all ('anyone on the internet can execute arbitrary code on the server without any credentials via 2 HTTP requests'), and the headline is what an operator reads first. The rest publish to /cve via `cves`, and they are worth reading as a set: authentication bypass on the MCP composer endpoint with mcp_composer_enabled=true by DEFAULT (CVE-2026-8446), AST-scan and Agentic-Assistant validation bypasses back to code execution (17632, 17633, 9196, 8478, 17630, 17625, 17623), arbitrary file read of the JWT signing secret and the SQLite DB (7646) and of server environment variables (10128), path traversal via the username and via knowledge-base names (7658, 7869, 8183), SSRF (9081, 7657), cross-user chat-history access (9130), and Fernet keys derived from Python's non-cryptographic random (8470, 9205). RANGE IS THE ADVISORY'S OWN WORDING, NOT A GUESSED FIX: `le 1.10.3` inclusive because every id reads 'through 1.10.3' and no vendor fixed version is named in the batch - inventing `lt 1.11.0` would flag a patched 1.10.4 install, which is the one failure mode worse than under-reporting (docs/severity-standard.md, and /daily-cve 5b claim 3). `ge 1.0.0` for the same reason, so a 0.x build is not claimed. Overlaps the CVE-2025-3248 row above on purpose: that one is KEV, separately probed in-band by test_langflow_rce, and has its own earlier fixed version (1.3.0), so an install on 1.2.0 correctly reads both. Version source is /api/v1/version ({"version":"1.2.0",...,"package":"Langflow"}) via the tech_signatures row added 2026-08-05; that path is NOT in the discovery wordlist, so like the row above this one only becomes reachable once the interface_tools change that feeds probe_unauth_interfaces responses to techdb ships in an IMAGE - live at the next release, not from the pack bundle. JOIN VERIFIED 2026-08-06 against the real product (langflowai/langflow:1.2.0, /api/v1/version answered anonymously): techdb captured 1.2.0 and known_vulns_for returned this row plus CVE-2025-3248; re-run with the reported version at 1.10.4 and 1.11.0, this row correctly does not fire.