CVE-2026-61740

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-44671 (ENISA EUVD) · GHSA-f4vv-55c2-5789 (GitHub Security Advisories) · PYSEC-2026-3475 (OSV.dev)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 15, 2026

Last Modified

October 24, 2026

Advisory Details (4)

Auto-updated Oct 8, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

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-5789
GitHub release Patch Available

v1.5.4

Patch available: HKUDS/LightRAG v1.5.4

https://github.com/HKUDS/LightRAG/releases/tag/v1.5.4
GitHub pull request 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/3319
GitHub commit Patch Available

commit f7819aa3a49a (HKUDS/LightRAG)

Patch available: HKUDS/LightRAG v1.5.4 (contains commit f7819aa3a49a)

https://github.com/HKUDS/LightRAG/commit/f7819aa3a49a9d8d92eed8251d82d6ebcafa8cba

Vendor Advisories for CVE-2026-61740(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piplightrag-hku @ 1.5.4 (fixes < 1.5.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
lightrag-hku0.0.2 ... 1.5.3 (87 versions)
  • every version up to 1.5.4: fixed in 1.5.4
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 210 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 03:09 UTCEchelonGraph re-scored
  2. 2026-11-13 03:09 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-12 02:18 UTCEchelonGraph re-scored
  5. 2026-11-12 02:18 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-11-11 01:26 UTCEchelonGraph re-scored
  8. 2026-11-11 01:26 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  9. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-11-10 00:35 UTCEchelonGraph re-scored
  11. 2026-11-10 00:35 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  12. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-11-08 23:45 UTCEchelonGraph re-scored
  14. 2026-11-08 23:45 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  15. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-11-07 22:55 UTCEchelonGraph re-scored
  17. 2026-11-07 22:55 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  18. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-11-06 22:00 UTCEchelonGraph re-scored
  20. 2026-11-06 22:00 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  21. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-11-06 14:25 UTCOSV refresh
  23. 2026-11-05 21:10 UTCEchelonGraph re-scored
  24. 2026-11-05 21:10 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  25. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 75 more
  1. 2026-11-04 20:20 UTCEchelonGraph re-scored
  2. 2026-11-04 20:20 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  3. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-11-03 19:29 UTCEchelonGraph re-scored
  5. 2026-11-03 19:29 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  6. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-11-02 18:39 UTCEchelonGraph re-scored
  8. 2026-11-02 18:39 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  9. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-11-01 17:48 UTCEchelonGraph re-scored
  11. 2026-11-01 17:48 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-f4vv-55c2-5789 · GitHub severity CRITICAL
  14. 2026-10-31 16:57 UTCEchelonGraph re-scored
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-30 15:54 UTCEchelonGraph re-scored
  18. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-29 15:05 UTCEchelonGraph re-scored
  20. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-10-28 14:14 UTCEchelonGraph re-scored
  22. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-27 03:14 UTCEchelonGraph re-scored
  24. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-25 22:19 UTCEchelonGraph re-scored
  26. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-10-25 14:14 UTCEchelonGraph re-scored
  28. 2026-10-24 21:26 UTCEchelonGraph re-scored
  29. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  30. 2026-10-24 15:54 UTCEchelonGraph re-scored
  31. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  32. 2026-10-23 15:03 UTCEchelonGraph re-scored
  33. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  34. 2026-10-22 14:10 UTCEchelonGraph re-scored
  35. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-10-21 13:17 UTCEchelonGraph re-scored
  37. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-10-20 12:17 UTCEchelonGraph re-scored
  39. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  40. 2026-10-19 11:25 UTCEchelonGraph re-scored
  41. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  42. 2026-10-18 03:25 UTCEchelonGraph re-scored
  43. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  44. 2026-10-17 08:09 UTCEchelonGraph re-scored
  45. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  46. 2026-10-16 07:18 UTCEchelonGraph re-scored
  47. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-10-15 06:13 UTCEchelonGraph re-scored
  49. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-10-14 01:50 UTCEchelonGraph re-scored
  51. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  52. 2026-10-12 22:05 UTCEchelonGraph re-scored
  53. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-10-12 15:50 UTCEchelonGraph re-scored
  55. 2026-10-11 19:34 UTCEchelonGraph re-scored
  56. 2026-10-11 16:49 UTCEchelonGraph re-scored
  57. 2026-10-11 14:11 UTCEchelonGraph re-scored
  58. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  60. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  61. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  63. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  64. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  65. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  66. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  67. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  68. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  69. 2026-10-01 12:41 UTCEchelonGraph re-scored
  70. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  71. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  72. 2026-09-28 08:46 UTCEchelonGraph re-scored
  73. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  74. 2026-09-24 08:53 UTCEchelonGraph re-scored
  75. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile

Frequently asked(5)

What is CVE-2026-61740?
CVE-2026-61740 is a critical-severity vulnerability; its CVE record was published on July 15, 2026. 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…
When was the CVE record for CVE-2026-61740 published?
The CVE record for CVE-2026-61740 was published on July 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-61740 actively exploited?
CVE-2026-61740 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61740?
CVE-2026-61740 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61740?
A fix for CVE-2026-61740 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61740 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61740

Explore →

Is Your Infrastructure Affected by CVE-2026-61740?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.