LightRAG: Hardcoded JWT Signing Secret Allows Authentication Bypass
GHSA-mcww-4hxq-hfr3 · CVE-2026-30762 · PYSEC-2026-2593
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Subject: Security Vulnerability Report Hardcoded JWT Secret (CVE-2026-30762)
Hi HKUDS team,
I'm writing to report a security vulnerability I discovered in LightRAG v1.4.10. This has been assigned CVE-2026-30762 by MITRE.
Vulnerability: Hardcoded JWT signing secret
Type: Improper Authentication (CWE-287)
Severity: High
Attack Vector: Remote / Unauthenticated
Summary:
The file lightrag/api/config.py (line 397) uses a default JWT secret "lightrag-jwt-default-secret" when the TOKEN_SECRET environment variable is not set. The AuthHandler in lightrag/api/auth.py (lines 24-25) uses this secret to sign and verify tokens. An unauthenticated attacker can forge valid JWT tokens using the publicly known default secret and gain access to any protected endpoint.
Reproduction:
- Install LightRAG v1.4.10 with AUTH_ACCOUNTS configured but no TOKEN_SECRET set
- Use PyJWT to sign a token: jwt.encode({"sub": "admin", "role": "user"}, "lightrag-jwt-default-secret", algorithm="HS256")
- Send a request to any protected endpoint with the header: Authorization: Bearer
- Access is granted without valid credentials
Suggested Fix:
Require TOKEN_SECRET to be explicitly set when AUTH_ACCOUNTS is configured. Refuse to start the API server if authentication is enabled but no custom secret is provided.
I'm following a 90-day responsible disclosure timeline from today's date. Please let me know if you have any questions or need additional information.
Best regards,
Venkata Avinash Taduturi
Ready to move
Start Securing
Free, no credit card | First findings in minutes