CVE-2026-62241: Missing Authentication for Critical Function in MohibShaikh clawvet
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.
AI Analysis
Technical Summary
The clawvet self-hosted API server (apps/api) before version 0.7.5 contains a hard-coded fallback JWT secret ('clawvet-dev-secret-change-me') in auth.ts and the default .env.example file. The GET /api/v1/scans endpoint returns scan records with userId values without requiring authentication. An attacker can use the known secret to forge a valid HS256 cg_session cookie offline, then call GET /api/v1/auth/me to retrieve the victim's email, subscription plan, and secret apiKey. The published clawvet npm package (CLI only) is not affected by this vulnerability.
Potential Impact
An unauthenticated remote attacker can impersonate users by forging session cookies due to the hard-coded JWT secret. This leads to unauthorized disclosure of sensitive user information such as email addresses, subscription plans, and secret API keys. The vulnerability severely compromises user privacy and security.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid deploying affected versions (<0.7.5) of the clawvet self-hosted API server. Changing the default JWT secret to a strong, unique value and restricting access to the API endpoints can help mitigate risk.
CVE-2026-62241: Missing Authentication for Critical Function in MohibShaikh clawvet
Description
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 v4.0
Score 9.3critical
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The clawvet self-hosted API server (apps/api) before version 0.7.5 contains a hard-coded fallback JWT secret ('clawvet-dev-secret-change-me') in auth.ts and the default .env.example file. The GET /api/v1/scans endpoint returns scan records with userId values without requiring authentication. An attacker can use the known secret to forge a valid HS256 cg_session cookie offline, then call GET /api/v1/auth/me to retrieve the victim's email, subscription plan, and secret apiKey. The published clawvet npm package (CLI only) is not affected by this vulnerability.
Potential Impact
An unauthenticated remote attacker can impersonate users by forging session cookies due to the hard-coded JWT secret. This leads to unauthorized disclosure of sensitive user information such as email addresses, subscription plans, and secret API keys. The vulnerability severely compromises user privacy and security.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid deploying affected versions (<0.7.5) of the clawvet self-hosted API server. Changing the default JWT secret to a strong, unique value and restricting access to the API endpoints can help mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-13T16:41:09.007Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a59784368715ace4305da84
Added to database: 07/17/2026, 00:33:07 UTC
Last enriched: 08/15/2026, 13:47:42 UTC
Last updated: 08/31/2026, 10:52:10 UTC
Views: 142
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.