What is the CVSS score of CVE-2026-33340?

CVE-2026-33340 has a CVSS 3.1 base score of 9.1 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. EPSS exploitation probability: 0.0%.

Which versions of Lollms Webui are affected by CVE-2026-33340?

A critical, unpatched vulnerability in LoLLMs WEBUI allows attackers to bypass authentication and force your servers to make unauthorized requests to internal systems and cloud services, potentially…

Is there a public PoC exploit available for CVE-2026-33340?

Yes, a public proof-of-concept exploit is available for CVE-2026-33340. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-33340?

Within 24 hours: Audit all systems running LoLLMs WEBUI, isolate affected instances from production networks, and disable the `/api/proxy` endpoint if possible. Within 7 days: Deploy WAF rules to block malicious proxy requests, implement strict network segmentation to limit server egress, and conduct forensic analysis for signs of exploitation. Within 30 days: Evaluate alternative solutions, plan decommissioning of LoLLMs WEBUI, or prepare for immediate patching once the vendor releases a fix.

Lollms Webui CVE-2026-33340

EUVD-2026-14928 CRITICAL

Missing Authentication for Critical Function (CWE-306)

2026-03-24 GitHub_M

Authentication Bypass SSRF Lollms Webui Parisneo

9.1

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

9.1 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Lifecycle Timeline

Re-analysis Queued

Apr 20, 2026 - 20:37 vuln.today

cvss_changed

EUVD ID Assigned

Mar 24, 2026 - 16:30 euvd

EUVD-2026-14928

Analysis Generated

Mar 24, 2026 - 16:30 vuln.today

CVE Published

Mar 24, 2026 - 15:58 nvd

CRITICAL 9.1

DescriptionGitHub Advisory

LoLLMs WEBUI provides the Web user interface for Lord of Large Language and Multi modal Systems. A critical Server-Side Request Forgery (SSRF) vulnerability has been identified in all known existing versions of lollms-webui. The @router.post("/api/proxy") endpoint allows unauthenticated attackers to force the server into making arbitrary GET requests. This can be exploited to access internal services, scan local networks, or exfiltrate sensitive cloud metadata (e.g., AWS/GCP IAM tokens). As of time of publication, no known patched versions are available.

AnalysisAI

A critical Server-Side Request Forgery (SSRF) vulnerability exists in the LoLLMs WEBUI application, allowing unauthenticated remote attackers to force the server to make arbitrary GET requests through the /api/proxy endpoint. All known existing versions of lollms-webui are affected, and as of publication, no patched version is available. Attackers can exploit this to access internal services, scan local networks, or exfiltrate sensitive cloud metadata such as AWS or GCP IAM tokens.

Technical ContextAI

LoLLMs WEBUI (Lord of Large Language and Multi-modal Systems Web User Interface) is a web-based interface for managing large language models, identified by CPE cpe:2.3:a:parisneo:lollms-webui. The vulnerability stems from CWE-306 (Missing Authentication for Critical Function), where the API proxy endpoint at /api/proxy in the lollms/server/endpoints/lollms_apps.py file accepts unauthenticated POST requests and performs GET requests to arbitrary URLs specified by the attacker. This classic SSRF flaw allows attackers to abuse the server's network position and privileges to access resources that should be restricted, including internal services on localhost, private network ranges (RFC 1918), and cloud metadata endpoints (169.254.169.254) that expose sensitive credentials and configuration data.

RemediationAI

As of this advisory's publication, no patched version of lollms-webui is available from the vendor. Organizations must implement immediate compensating controls until a patch is released. Deploy a reverse proxy or web application firewall (WAF) in front of the lollms-webui application to block all unauthenticated access to the /api/proxy endpoint, or implement authentication requirements at the network layer. Restrict network egress from the server running lollms-webui to prevent it from making outbound connections to internal networks (RFC 1918 ranges: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), localhost (127.0.0.0/8), link-local addresses (169.254.0.0/16), and other sensitive ranges. In cloud environments, block access to metadata endpoints (169.254.169.254) using host-based firewall rules or security groups. Consider temporarily disabling the lollms-webui service if it is not business-critical until an official patch becomes available. Monitor the GitHub repository and security advisory at https://github.com/ParisNeo/lollms-webui/security/advisories/GHSA-mcwr-5469-pxj4 for patch release announcements.