CVE-2026-1114: LoLLMs Weak JWT Secret Key Access Control Flaw
LoLLMs
LoLLMs contains an improper access control vulnerability caused by a weak secret key used for JWT session management. Attackers can brute-force the secret key offline to forge administrative tokens.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.8
- EPSS
- 0.01 · top 56% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 7 Apr 2026
- last update
- 7 Apr 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-04-07CVE-2026-1114: LoLLMs is vulnerable to Improper Access Control through weak secret keyGitHub Advisory Database · github.com/advisories/GHSA-9296-v3fr-j92j
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 7 Apr 2026 · first reported 7 Apr 2026
- origin
- GitHub Advisory DatabaseVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 07:00Z · updated 2026-10-18 07:00Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-1114: LoLLMs Weak JWT Secret Key Access Control Flaw https://gcdradar.vercel.app/incidents/cve-2026-1114-lollms-weak-jwt-secret-key-access-control-flaw · AIR-2026-0557 · closed 2026-04-07 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-04-07 - AI role: Attack on AI - Products: LoLLMs - CVE ids: CVE-2026-1114 - CVSS: 9.8 ## Summary LoLLMs contains an improper access control vulnerability caused by a weak secret key used for JWT session management. Attackers can brute-force the secret key offline to forge administrative tokens. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-04-07: CVE-2026-1114: LoLLMs is vulnerable to Improper Access Control through weak secret key (https://github.com/advisories/GHSA-9296-v3fr-j92j) ## Sources - 2026-04-07 GitHub Advisory Database: CVE-2026-1114: LoLLMs is vulnerable to Improper Access Control through weak secret key https://github.com/advisories/GHSA-9296-v3fr-j92j Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.0LoLLMs CVE-2024-11302: Missing access check vulnerability in LoLLMs repository
Patch now · Disclosed · since 20 Mar 2025 · CVE-2024-11302
AI - closed8.8Hugging Face libraries Hugging Face Diffusers custom pipeline trust_remote_code bypass vulnerability
Patch now · Disclosed · since 7 May 2026 · CVE-2026-44827
AI - closed8.8Hugging Face libraries Hugging Face Diffusers trust_remote_code bypass allows remote code execution
Patch now · Disclosed · since 7 May 2026 · CVE-2026-44513
AI - closed5.3Flowise CVE-2026-8027: Authorization bypass in FlowiseAI Flowise user controller handler
Patch now · Disclosed · since 6 May 2026 · CVE-2026-8027
AI - closed3.7Flowise CVE-2026-8028: Information disclosure vulnerability in FlowiseAI Flowise
Patch now · Disclosed · since 6 May 2026 · CVE-2026-8028
AI - closed6.3Flowise Flowise API response handler exposes bcrypt password hashes
Patch now · Disclosed · since 6 May 2026 · CVE-2026-8026
AI