CVE-2026-61736
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLightRAG 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLightRAG server prior to 1.5.4 defaults to CORS_ORIGINS=* with allow_credentials=True, which combined causes Starlette CORSMiddleware to improperly whitelist all origins for credentialed requests. This allows any malicious website visited by an authenticated user to silently send authenticated API calls, enabling data exfiltration (documents, knowledge graphs) or destructive operations like deleting the document store.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check LightRAG server versionIdentify the installed or running LightRAG version (e.g., check process args, container label, or package version) and compare it to the affected range: versions prior to 1.5.4 are vulnerableAffected if Installed version is prior to 1.5.4 and the server is accessible
-
Verify CORS_ORIGINS configurationInspect the LightRAG server configuration or environment variables for CORS_ORIGINS settingAffected if CORS_ORIGINS is set to wildcard (*) or not explicitly defined (using default)
-
Confirm allow_credentials settingCheck if allow_credentials is enabled in the CORS middleware configuration or environmentAffected if allow_credentials is set to True or enabled by default
-
Identify the dangerous combinationDetermine if CORS_ORIGINS=* and allow_credentials=True are both active simultaneously (this is the insecure configuration)Affected if Both CORS_ORIGINS=* and allow_credentials=True are in effect at the same time
A user is affected if running LightRAG server prior to version 1.5.4 with the default CORS configuration where CORS_ORIGINS=* and allow_credentials=True are both enabled, allowing any origin to make credentialed requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to LightRAG 1.5.4 or explicitly configure a whitelist of allowed origins instead of the wildcard (*) when credentials are enabled.
1.5.4 or later
- Upgrade LightRAG to version 1.5.4 or later using your package manager (e.g., pip install lightrag>=1.5.4)
- After upgrading, verify your CORS_ORIGINS environment variable or configuration is not set to '*' if allow_credentials is enabled in your deployment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61736 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-61736 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data