CVE-2026-62241

Mohibshaikh Clawvet authentication bypass

9.1 CRITICALPublic exploitEPSS 0.67%

Published17 Jul 2026

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 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

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

Affected products

Mohibshaikh Clawvet< 0.7.5

Remediation

Fixed in

Mohibshaikh Clawvet≥ 0.7.5

Patch & vendor advisories

https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9

References

https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9ExploitMitigationVendor Advisory
https://www.vulncheck.com/advisories/clawvet-hard-coded-jwt-secret-session-forgeryThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-62241 being actively exploited?

CVE-2026-62241 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.67%.

How severe is CVE-2026-62241?

CVE-2026-62241 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.67% probability of exploitation.

Which products are affected by CVE-2026-62241?

Affected products include Mohibshaikh Clawvet.

How do I fix CVE-2026-62241?

Upgrade affected software to a fixed version, for example Mohibshaikh Clawvet 0.7.5 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-62241 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.