CVE-2026-62241

clawvet < 0.7.5 Hard-coded JWT Secret Session Forgery

Published Jul 17, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Clawvet, a self‑hosted API server, embeds a hard‑coded JWT secret ('clawvet‑dev‑secret‑change‑me') in auth.ts before version 0.7.5. The default secret is also shipped in .env.example. Because the endpoint GET /api/v1/scans returns scan records containing userId values without requiring authentication, an attacker who can query the endpoint can harvest a victim’s userId. With the known secret, the attacker can construct a valid HS256 cg_session cookie offline and then call GET /api/v1/auth/me to obtain the victim’s email, subscription plan, and secret apiKey.

Affected Systems

Vendor: MohibShaikh. Product: clawvet API server. Versions affected are all releases before 0.7.5; the advisory notes that only the server component (apps/api) is impacted and the npm package, which is CLI only, is not affected.

Risk and Exploitability

CVSS score of 9.3 indicates critical impact. The EPSS score of < 1% suggests a low probability of exploitation in the wild, and the vulnerability is not listed in the CISA KEV catalog. The attack path is remote, unauthenticated: a client can simply request scan data, harvest the userId, forge a session cookie using the hard‑coded secret, and then query the personal information endpoint. The lack of authentication on the scans endpoint and the use of a predictable secret make exploitation straightforward once a victim’s userId is known.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade clawvet to version 0.7.5 or later to remove the hard‑coded secret
  • Replace the default JWT signing secret in the environment with a unique, high‑entropy value and ensure that secrets are not shipped in example configuration files
  • Rotate any API keys that could have been accessed if the attacker successfully forged a session; regenerate new keys and verify that the application signs new tokens with the updated secret
  • As a temporary measure, restrict access to the GET /api/v1/scans endpoint to authenticated users or otherwise deny unauthenticated requests

Generated by OpenCVE AI on September 24, 2026 at 23:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Mohibshaikh
Mohibshaikh clawvet
Vendors & Products Mohibshaikh
Mohibshaikh clawvet
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title clawvet < 0.7.5 Hard-coded JWT Secret Session Forgery
Weaknesses CWE-306
CWE-321
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

  • CWE-321

    Use of Hard-coded Cryptographic Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 14, 2026, 4:50 PM
Reserved
Jul 13, 2026, 4:41 PM
Status
Analyzed
Published
Jul 17, 2026, 2:18 AM
Modified
Oct 24, 2026, 8:10 PM