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.
CVE-2026-62241
CRITICALPre-NVD 9.19.1—Trending — 4 sources updated this weekElevated
EchelonGraph scoreHIGH confidence
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-17. a secondary CVSS source baseline 9.1; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EG Risk
- 72(Attend)EG Risk 72/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity91% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 31.5%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 17, 2026
Advisory Details (2)
Auto-updated Jul 17, 2026🔬 Proof of concept available. Patch available. Sources: github.
generic
clawvet < 0.7.5 Hard-coded JWT Secret Session Forgery | Advisories | VulnCheck
https://www.vulncheck.com/advisories/clawvet-hard-coded-jwt-secret-session-forgerygithub Patch Available🟡 PoC Available
Hard-coded JWT Secret Allows Session Forgery and API Key Disclosure · Advisory · MohibShaikh/clawvet · GitHub
https://github.com/MohibShaikh/clawvet/security/advisories/GHSA-9mww-p953-jfc9Vendor Advisories for CVE-2026-62241(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 14:23 UTCEG score recompute
- 2026-07-18 14:23 UTCGHSA enrichment
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 04:35 UTCGHSA enrichment
- 2026-07-17 00:24 UTCEG score recompute
- 2026-07-17 00:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306 · CWE-321
- CVE-2011-10013EG 10.0CRITICAL
- CVE-2014-125124EG 10.0CRITICAL
- CVE-2017-2637EG 10.0EPSS 91%CRITICAL
- CVE-2016-9335EG 10.0CRITICAL
- CVE-2010-5326EG 10.0 KEVEPSS 97%CRITICAL
- CVE-2018-25134EG 9.8CRITICAL
- CVE-2012-10030EG 9.8CRITICAL
- CVE-2018-21132EG 9.8CRITICAL
- CVE-2014-3449EG 9.8CRITICAL
- CVE-2006-0062EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-62241?
CVE-2026-62241 is a critical vulnerability published on July 17, 2026. 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…
When was CVE-2026-62241 disclosed?
CVE-2026-62241 was first published in the National Vulnerability Database on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62241 actively exploited?
CVE-2026-62241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-62241?
CVE-2026-62241 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-62241?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62241, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62241
Is Your Infrastructure Affected by CVE-2026-62241?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.