CVE-2026-61736

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-20. A secondary CVSS source baseline 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-44670 (ENISA EUVD) · GHSA-6x6h-qqr7-855w (GitHub Security Advisories) · PYSEC-2026-3474 (OSV.dev)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.4%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

LightRAG provides simple and fast retrieval-augmented generation. Prior to 1.5.4, the server defaults to CORS_ORIGINS=* combined with allow_credentials=True in lightrag/api/lightrag_server.py, causing Starlette CORSMiddleware to effectively whitelist every origin for credentialed cross-origin requests. Any malicious website visited by an authenticated LightRAG user can silently make authenticated API requests, exfiltrating documents and knowledge graph data or performing destructive actions such as deleting the document store. This vulnerability is fixed in 1.5.4.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/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.
Exploitation1.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
1.4%
EPSS %ILE
73rd
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.GitHub Security Advisory CVSS
EG Likelihood
1.4% 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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 (6)

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

CORS Wildcard + Credentials Enables Any-Origin Credentialed Requests · Advisory · HKUDS/LightRAG · GitHub

https://github.com/HKUDS/LightRAG/security/advisories/GHSA-6x6h-qqr7-855w
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): don't pair wildcard CORS origin with credentials

Patch available: HKUDS/LightRAG v1.5.4 (PR #3317 merged 2026-06-24)

https://github.com/HKUDS/LightRAG/pull/3317
GitHub commit Patch Available

commit ebba6548639c (HKUDS/LightRAG)

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

https://github.com/HKUDS/LightRAG/commit/ebba6548639c0f2e8919100eff76b401f1222252
GitHub commit Patch Available

commit df68d75f9dc2 (HKUDS/LightRAG)

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

https://github.com/HKUDS/LightRAG/commit/df68d75f9dc29dd340ffb6794b48f48c4fdc9a2d
GitHub commit Patch Available

commit 09567a4c983f (HKUDS/LightRAG)

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

https://github.com/HKUDS/LightRAG/commit/09567a4c983f580050db63569dd477122c058c3d

Vendor Advisories for CVE-2026-61736(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.3)—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(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 43× 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 v3 → 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 206 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 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-61736.yaml
    Published Sep 14, 2026

    LightRAG <= 1.5.3 - Credentialed CORS Wildcard

    Open source ↗

Frequently asked(5)

What is CVE-2026-61736?
CVE-2026-61736 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, the server defaults to CORS_ORIGINS=* combined with allow_credentials=True in lightrag/api/lightrag_server.py, causing Starlette CORSMiddleware to effectively whitelist every origin for credentialed cross-origin…
When was the CVE record for CVE-2026-61736 published?
The CVE record for CVE-2026-61736 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-61736 actively exploited?
CVE-2026-61736 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.4% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61736?
CVE-2026-61736 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-61736?
A fix for CVE-2026-61736 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61736 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-61736

Explore →

Is Your Infrastructure Affected by CVE-2026-61736?

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