CVE-2026-1114Critical· 9.8▾ MidnightLoLLMs is vulnerable to Improper Access Control through weak secret key
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 53.9 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.5%
In parisneo/lollms version 2.1.0, the application's session management is vulnerable to improper access control due to the use of a weak secret key for signing JSON Web Tokens (JWT). This vulnerability allows an attacker to perform an offline brute-force attack to recover the secret key. Once the secret key is obtained, the attacker can forge administrative tokens by modifying the JWT payload and resigning it with the cracked secret. This enables unauthorized users to escalate privileges, impersonate the administrator, and gain access to restricted endpoints. The issue is resolved in version 2.2.0.
lollms < 2.2.0Upgrade to a patched release:
lollms 2.2.0Connected by shared product, vendor, weakness, or advisory.
CVE-2024-4078Critical· 9.8LoLLMS Command Injection vulnerability
CVE-2024-5824High· 7.4lollms path traversal vulnerability allows overriding of config.yaml file, leading to RCE
CVE-2024-6281High· 7.3LoLLMS vulnerable to Expected Behavior Violation
CVE-2026-1117High· 8.2Lollms has an Improper Access Control vulnerability
CVE-2024-3429Critical· 9.8LoLLMS Path Traversal vulnerability
CVE-2026-1116Medium· 6.1A Cross-site Scripting (XSS) vulnerability was identified in the `from_dict` method of the `AppLollmsMessage` class in parisneo/lollms pr…