LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.4, when LightRAG is deployed with LIGHTRAG_API_KEY set but AUTH_ACCOUNTS unset, X-API-Key protection can be bypassed because lightrag/api/auth.py falls back to a hardcoded DEFAULT_TOKEN_SECRET, /auth-status and /login can mint guest JWTs, and combined_dependency in lightrag/api/utils_api.py accepts a valid guest token before checking the API key. A remote unauthenticated attacker can call endpoints guarded by combined_auth, including document read, upload, deletion, graph mutation, and query endpoints. This vulnerability is fixed in 1.5.4.
CVE-2026-61740
CRITICALPre-NVD 9.39.3Elevated
EchelonGraph scoreLOW confidence
This critical-severity CVE scores 9.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cna:github_m
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 9.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.3
- EG Score
- 9.3(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available
Authentication bypass: hardcoded DEFAULT_TOKEN_SECRET and public /auth-status defeat LIGHTRAG_API_KEY protection · Advisory · HKUDS/LightRAG · GitHub
https://github.com/HKUDS/LightRAG/security/advisories/GHSA-f4vv-55c2-5789github_release Patch Available
v1.5.4
Patch available: HKUDS/LightRAG v1.5.4
https://github.com/HKUDS/LightRAG/releases/tag/v1.5.4github_pr Patch Available
fix(api): stop guest tokens from bypassing X-API-Key auth
Patch available: HKUDS/LightRAG v1.5.4 (PR #3319 merged 2026-06-24)
https://github.com/HKUDS/LightRAG/pull/3319github_commit Patch Available
commit f7819aa3a49a (HKUDS/LightRAG)
Patch available: HKUDS/LightRAG v1.5.4 (contains commit f7819aa3a49a)
https://github.com/HKUDS/LightRAG/commit/f7819aa3a49a9d8d92eed8251d82d6ebcafa8cbaWeakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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-15 14:51 UTCEG score recompute
- 2026-07-15 14:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-798 · CWE-287
Frequently asked(4)
What is CVE-2026-61740?
CVE-2026-61740 is a critical vulnerability published on July 15, 2026. LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.4, when LightRAG is deployed with LIGHTRAGAPIKEY set but AUTHACCOUNTS unset, X-API-Key protection can be bypassed because lightrag/api/auth.py falls back to a hardcoded DEFAULTTOKENSECRET, /auth-status and /login can…
When was CVE-2026-61740 disclosed?
CVE-2026-61740 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-61740?
CVE-2026-61740 has a CVSS v3 base score of 9.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-61740?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61740, 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-61740
Is Your Infrastructure Affected by CVE-2026-61740?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.