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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9 Exploit, Mitigation, Vendor Advisory
- https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9 Exploit, Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.3 · mohibshaikhNVD modified 2026-10-24 20:10
Affected (CPE criteria) 1
cpe:2.3:a:mohibshaikh:clawvet:*:*:*:*:*:node.js:*:*
References 3
- https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9 Exploit, Mitigation, Vendor Advisory
- https://www.vulncheck.com/advisories/clawvet-hard-coded-jwt-secret-session-forgery Third Party Advisory
- https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9 Exploit, Mitigation, Vendor Advisory