CVE-2026-62241

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.

CVSS 4.0

9.3CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

0.7% chance of exploitation in the next 30 days; higher than 51% of CVEs (scores of 2026-10-25)

CWEs

CWE-306, CWE-321

Published

2026-07-17

Modified

2026-10-24

Record from

the NVD, synced 2026-10-25

Affected

• mohibshaikh:clawvet

References

• https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9
• https://www.vulncheck.com/advisories/clawvet-hard-coded-jwt-secret-session-forgery
• https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9

Check your stackJSON