IBM Langflow OSS 1.0.0 through 1.10.3 does not properly validate the username field, allowing attackers to inject path traversal sequences and bypass containment checks. This enables multiple severe impacts, including arbitrary directory deletion, cross-tenant data destruction, and JWT signing key deletion leading to session invalidation.
clawvet self-hosted API server (apps/api) before 0.7.5 hard-codes a fallback JWT secret ('clawvet-dev-secret-change-me') in auth.ts and ships it as the default in .env.example. Because GET /api/v1/scans returns scan records containing userId values without authentication, a remote unauthenticated attacker can harvest a victim's userId, forge a valid HS256 cg_session cookie offline using the known secret, and call GET /api/v1/auth/me to obtain the victim's email address, subscription plan, and secret apiKey. The published clawvet npm package (CLI only) is not affected.
| Version | Type | Source | Base | Exp | Imp |
|---|---|---|---|---|---|
| 3.1 | Primary | cve.org | 9.1 | — | — |
| 3.1 | Primary | NVD | 9.1 | 3.9 | 5.2 |
| 3.1 | Secondary | NVD | 9.1 | 3.9 | 5.2 |
| 4.0 | Primary | cve.org | 9.3 | — | — |
| 4.0 | Secondary | ENISA EUVD | 9.3 | — | — |
| 4.0 | Secondary | NVD | 9.3 | — | — |