LightRAG: Hardcoded JWT Signing Secret Allows Authentication Bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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 TOKENSECRET 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: 1. Install LightRAG v1.4.10 with AUTHACCOUNTS configured but no TOKENSECRET set 2. Use PyJWT to sign a token: jwt.encode({"sub": "admin", "role": "user"}, "lightrag-jwt-default-secret", algorithm="HS256") 3. Send a request to…

Published by the source

4 Apr 2026, 06:14 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:40 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-mcww-4hxq-hfr3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-mcww-4hxq-hfr3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-30762

Advisory: LightRAG: Hardcoded JWT Signing Secret Allows Authentication Bypass
IDs: CVE-2026-30762, GHSA-mcww-4hxq-hfr3
Record: https://patchnext.com/advisories/cve-2026-30762 (revision 2, source checked 26 Oct 2026, 13:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: lightrag-hku 1.4.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI lightrag-hku: affected <= 1.4.12; fixed in 1.4.13

## Suggested inspection (read-only)
- `python -m pip show lightrag-hku`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on lightrag-hku.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mcww-4hxq-hfr3 (OSV record GHSA-mcww-4hxq-hfr3 lists affected ranges: PyPI lightrag-hku >=0 <1.4.13 (fixed))
- Verified: https://github.com/advisories/GHSA-mcww-4hxq-hfr3 (GitHub-reviewed advisory GHSA-mcww-4hxq-hfr3 lists affected ranges: PyPI lightrag-hku >=0 <=1.4.12)

Commands are suggestions: review each one before running it.