Skip to content
Web

CVE-2026-61736

9.3
Critical
EPSS 1%Patch availableJul 16, 2026

CORS misconfiguration allows credentialed cross-origin API calls, enabling data theft or deletion.

common questions

Is CVE-2026-61736 being exploited?

Not confirmed. CVE-2026-61736 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.4% probability of exploitation in the next 30 days.

How severe is CVE-2026-61736?

CVE-2026-61736 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-61736?

Yes. A fix has been recorded for CVE-2026-61736. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-61736 affect?

CVE-2026-61736 affects LightRAG versions prior to 1.5.4 (default server with CORS_ORIGINS=* and allow_credentials=True). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-61736?

Upgrade to LightRAG ≥1.5.4; restrict CORS_ORIGINS and disable allow_credentials for public origins.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
LightRAG versions prior to 1.5.4 (default server with CORS_ORIGINS=* and allow_credentials=True)
impact

Malicious sites visited by an authenticated user can make credentialed API calls to exfiltrate documents/knowledge graph or delete the document store.

action required

Immediate action required

affected versions
HKUDS LightRAG
  • affected< 1.5.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free