Loading story…
HKUDS disclosed and fixed CVE-2026-61740, a critical authentication bypass in LightRAG versions prior to 1.5.4 that could let remote unauthenticated attackers reach endpoints intended to be protected by LIGHTRAG_API_KEY. In affected deployments where LIGHTRAG_API_KEY was set but AUTH_ACCOUNTS was left unset, the application could fall back to a hardcoded DEFAULT_TOKEN_SECRET, enabling guest JWT creation through public endpoints and defeating API-key enforcement. The flaw carries a CVSS 4.0 score of 9.3 and is mapped to CWE-287 and CWE-798.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
A critical authentication bypass vulnerability affecting LightRAG versions before 1.5.4 was disclosed as CVE-2026-61740. The issue allows remote unauthenticated attackers to mint guest JWTs via public endpoints and bypass API-key protection when LIGHTRAG_API_KEY is set but AUTH_ACCOUNTS is unset; the fix is available in version 1.5.4.
On 2026-06-24, HKUDS committed a fix to LightRAG's combined authentication logic to prevent guest JWTs signed with the default token secret from bypassing X-API-Key checks in API-key-only deployments. The change also added regression tests covering the bypass scenario and preserving intended guest access in fully open mode.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A critical missing-authentication flaw tracked as **CVE-2026-61808** affects **LightRAG** through version `1.5.4`, leaving its API server exposed in the default configuration by binding to `0.0.0.0` with authentication disabled. The issue allows unauthenticated remote attackers to reach sensitive API functions over the network and perform actions including reading indexed document content, uploading or deleting documents, modifying the knowledge graph, canceling pipelines, clearing caches, and consuming LLM resources. The vulnerability is rated **CVSS 9.8** and mapped to **CWE-306**. LightRAG addressed the issue in `1.5.5rc1` with code, test, and documentation changes that add startup warnings when the service is bound to a non-loopback address without authentication and when `WHITELIST_PATHS` leaves `/api/*` routes publicly accessible. The patch also improves detection of wildcard whitelist entries such as `/*`, updates container examples and deployment guidance, and warns operators that Ollama-compatible endpoints can remain exposed unless access is restricted, such as limiting `WHITELIST_PATHS` to `/health`. Recommended mitigations are to upgrade, enable `LIGHTRAG_API_KEY` or `AUTH_ACCOUNTS` with `TOKEN_SECRET`, and restrict network access to the API server.
Aug 7, 2026
A critical vulnerability in **LiteLLM** tracked as `CVE-2026-49468` allows attackers to bypass authentication through **Host header injection** and reach protected management endpoints. The flaw affects LiteLLM versions earlier than **`1.84.0`** and stems from a mismatch in how the authentication layer evaluates routes versus how **FastAPI** ultimately dispatches them, creating a path for unauthenticated access under specific conditions. The issue is classified as **`CWE-290`** and has been rated **CVSS 9.5**, with researchers describing it as network-exploitable with low attack complexity and no user interaction required. The vulnerability was responsibly disclosed by **Le The Thang** of **KCSC** and **Kim Ngoc Chung** of **One Mount Group**, and LiteLLM maintainers have released a fix in version **`1.84.0`** with no configuration changes required. There is no confirmed evidence of active exploitation, and **LiteLLM Cloud** customers are reportedly not affected. Self-hosted deployments may also be shielded if upstream infrastructure such as **Cloudflare**, **WAFs**, reverse proxies with strict allowlists, or host-validating load balancers normalize or reject malformed Host headers before requests reach the application.
Jun 29, 2026
Attackers began exploiting **CVE-2026-42208** in LiteLLM shortly after public disclosure, using a pre-authentication SQL injection flaw in the product’s `Authorization: Bearer` verification path to query the backend PostgreSQL database without logging in. The vulnerability, also tracked as `GHSA-r75f-5x8p-qvmc`, affects LiteLLM versions **1.81.16 through 1.83.6** and was fixed in **v1.83.7** after the project replaced vulnerable string interpolation with a parameterized query. Sysdig said the first observed exploitation attempt arrived **36 hours and seven minutes** after the advisory was indexed, with activity focused on enumerating high-value tables holding virtual API keys, provider credentials, verification tokens, and environment-based configuration. Researchers described the intrusion attempts as targeted rather than opportunistic, citing knowledge of Prisma-generated PostgreSQL table names and `UNION`-based column discovery; while no confirmed follow-on abuse was observed, defenders are being urged to patch exposed instances immediately, rotate all stored secrets, and review logs and billing accounts for signs of compromise.
Jun 29, 2026