# CVE-2026-62241: clawvet < 0.7.5 Hard-coded JWT Secret Session Forgery

> Remote attackers can forge session cookies using a hard-coded JWT secret to access victim account details and API keys.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-9mww-p953-jfc9, GHSA-xrvw-c6vh-v4r5

## What is CVE-2026-62241?

CVE-2026-62241 is a critical vulnerability in MohibShaikh clawvet, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-62241?

It affects 1 product.


Products: Mohibshaikh Clawvet.

## How do I fix CVE-2026-62241?

No fix has been published for CVE-2026-62241 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62241 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62241 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62241 and fix it if it is affected.

What it is: CVE-2026-62241 is a critical vulnerability in MohibShaikh clawvet, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62241 exists.

Affected product: MohibShaikh clawvet. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62241/ (Markdown: https://insights.sbomify.com/CVE-2026-62241/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62241
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62241
- OSV: https://osv.dev/vulnerability/CVE-2026-62241

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62241/
Summaries are generated and may contain mistakes; the official description above is the record.