LightRAG Critical CORS Flaw Enables Data Theft

A critical security vulnerability, tracked as CVE-2026-61736, has been identified in the LightRAG server. The flaw stems from an insecure default configuration where the system combines a wildcard CORS origin with credential support, effectively allowing any external website to perform authenticated API calls on behalf of a logged-in user.

What's at Risk

The vulnerability affects the lightrag-hku package for Python. Organizations running internet-facing instances of LightRAG are at the highest risk, as the server is susceptible to unauthorized cross-origin credentialed requests. This exposure primarily impacts deployments where users maintain active sessions, as the flaw allows attackers to bypass standard cross-origin protections.

How the Flaw Works

This vulnerability is classified as CWE-942, or overly permissive cross-domain policy. In web security, Cross-Origin Resource Sharing (CORS) is designed to restrict how a browser allows web pages to interact with resources from a different domain. When a server is configured to echo the requesting origin back to the browser while simultaneously allowing credentials, it effectively disables the security boundary intended by the browser's same-origin policy.

Generally, this class of weakness allows an attacker to host a malicious script on a third-party site. If an authenticated user visits that site, the script can trigger background requests to the vulnerable server. Because the server explicitly tells the browser to include credentials, the browser attaches the user's session cookies or authentication tokens to the request, allowing the attacker to interact with the API as if they were the legitimate user.

How to Protect Your Systems

• Update to lightrag-hku version 1.5.4 or later immediately to resolve the insecure CORS configuration.
• Verify that your server environment variables do not explicitly override default security settings with insecure wildcard values.
• Restrict network access to your LightRAG instance by placing it behind a VPN or an authenticated proxy rather than exposing it directly to the public internet.
• Audit your application logs for unexpected cross-origin requests or unusual patterns originating from unknown domains.
• Implement strict Content Security Policy (CSP) headers to prevent browsers from executing unauthorized scripts that might attempt to interact with your API.

Given the CVSS 9.3 severity rating, this vulnerability represents a significant risk to data confidentiality. Promptly applying the vendor-provided patch is the only way to ensure the server no longer echoes arbitrary origins in its preflight responses, effectively closing the window for unauthorized credentialed access.