LearnCTEM.com, Best CTEM Learning Platform
CVE Intelligence Hub

CVE-2026-126379: Vvveb Server Side Request Forgery Vulnerability

CVE-2026-126379 explained: high Server Side Request Forgery in Vvveb. CVSS 8.3. Affected versions, detection, fixes and CTEM priority.

Last updated: Nov 13, 2026

CVSS
8.3 HIGH
EPSS
0.35%
CISA KEV
Not listed
CWE
CWE-918

Sources: National Vulnerability Database, CVE.org, CISA KEV, FIRST EPSS

CVE-2026-126379 Overview

Vvveb 1.0.8.6 contains an incomplete server-side request forgery fix that allows authenticated admin users to bypass DNS pinning by requesting non-443 URLs. Attackers can supply a rebinding hostname to the editor oEmbedProxy url parameter to read loopback services, internal panels, and cloud metadata credentials.

Critical Impact

Remote, authenticated attackers can exploit this Server Side Request Forgery in Vvveb. The CVSS base score is 8.3 (High).

Affected Products

  • Vvveb: see the vendor advisory for the exact affected versions

Discovery Timeline

  • 2026-11-13: CVE-2026-126379 published to the National Vulnerability Database by disclosure@vulncheck.com
  • 2026-11-13: last updated in the NVD database

Technical Details for CVE-2026-126379

Vulnerability Analysis

CVE-2026-126379 is a Server Side Request Forgery weakness (CWE-918: Server Side Request Forgery) in Vvveb. Based on its CVSS vector, the flaw can be reached over the network, needs some level of access, and needs no user interaction. The server can be made to send requests to internal or arbitrary systems.

With a CVSS base score of 8.3 and an EPSS exploitation probability of 0.35 percent, apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Root Cause

The weakness is classified as CWE-918: Server Side Request Forgery. The server can be made to send requests to internal or arbitrary systems.

Attack Vector

Based on the CVSS vector, the flaw can be reached over the network, needs some level of access, and needs no user interaction. Attack complexity is low complexity.

No exploitation in the wild is confirmed by CISA at the time of the last update. Check the references below for any vendor or researcher proof of concept.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Detection Methods for CVE-2026-126379

Detection Strategies

  • Inventory every instance of Vvveb and compare the running version with the affected range above.
  • Check external attack surface scans for internet facing instances of the component.
  • Run an authenticated vulnerability scan once your scanner ships a check for this CVE.

Monitoring Recommendations

  • Forward Vvveb application, access and audit logs to your SIEM for retrospective hunting.
  • Alert on new processes, configuration changes or outbound connections from the affected service.
  • Track the vendor advisory and the CISA KEV catalog for changes in exploitation status.

How to Mitigate CVE-2026-126379

Immediate Actions Required

  • Apply the fixed version of Vvveb named in the vendor advisory.
  • Prioritize internet facing and business critical instances first.
  • Rescan after the change to confirm the exposure is closed.

Patch Information

Use the fixed version listed in the vendor advisory for Vvveb.

Workarounds

  • If patching must wait, restrict network access to the affected service and place it behind authentication or a web application firewall rule.

CWE References

Technical References

This entry is built directly from NVD, CISA KEV and EPSS data. Verify fixed versions in the vendor advisory before you deploy.

Frequently asked questions

CVE-2026-126379 is a high severity Server Side Request Forgery in Vvveb with a CVSS score of 8.3. Apply the vendor fix and confirm exposure on internet facing and business critical assets first.

Related CVEs

CRITICAL10.0
CVE-2026-121356
Adobe Connect

Adobe Connect is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation. Exploitation of this issue does not require user interaction. Scope is changed.

Nov 10, 2026
CRITICAL10.0
CVE-2026-121889
Adobe Connect

Adobe Connect is affected by a Server-Side Request Forgery (SSRF) vulnerability that could result in privilege escalation. Exploitation of this issue does not require user interaction. Scope is changed.

Nov 10, 2026
CRITICAL10.0
CVE-2026-26222
Beyond Altec Doclink

Altec DocLink (now maintained by Beyond Limits Inc.) version 4.0.336.0 exposes insecure .NET Remoting endpoints over TCP and HTTP/SOAP via Altec.RDCHostService.exe using the ObjectURI "doclinkServer.soap". The service does not require authentication and is vulnerable to unsafe object unmarshalling, allowing remote attackers to read arbitrary files from the underlying system by specifying local file paths. Additionally, attackers can coerce SMB authentication via UNC paths and write arbitrary files to server locations. Because writable paths may be web-accessible under IIS, this can result in unauthenticated remote code execution or denial of service through file overwrite.

Feb 24, 2026
CRITICAL10.0
CVE-2026-32186
Microsoft Bing

Server-side request forgery (ssrf) in Microsoft Bing allows an unauthorized attacker to elevate privileges over a network.

Apr 3, 2026
CRITICAL10.0
CVE-2026-34162
Fastgpt

FastGPT is an AI Agent building platform. Prior to version 4.14.9.5, the FastGPT HTTP tools testing endpoint (/api/core/app/httpTools/runTool) is exposed without any authentication. This endpoint acts as a full HTTP proxy — it accepts a user-supplied baseUrl, toolPath, HTTP method, custom headers, and body, then makes a server-side HTTP request and returns the complete response to the caller. This issue has been patched in version 4.14.9.5.

Mar 31, 2026
CRITICAL10.0
CVE-2026-32871
Jlowin Fastmcp

FastMCP is a Pythonic way to build MCP servers and clients. Prior to version 3.2.0, the OpenAPIProvider in FastMCP exposes internal APIs to MCP clients by parsing OpenAPI specifications. The RequestDirector class is responsible for constructing HTTP requests to the backend service. A vulnerability exists in the _build_url() method. When an OpenAPI operation defines path parameters (e.g., /api/v1/users/{user_id}), the system directly substitutes parameter values into the URL template string without URL-encoding. Subsequently, urllib.parse.urljoin() resolves the final URL. Since urljoin() interprets ../ sequences as directory traversal, an attacker controlling a path parameter can perform path traversal attacks to escape the intended API prefix and access arbitrary backend endpoints. This results in authenticated SSRF, as requests are sent with the authorization headers configured in the MCP provider. This issue has been patched in version 3.2.0.

Apr 2, 2026
Your next credential

Earn your free CTEM certification.

Learn to scope, prioritize, validate and mobilize fixes for CVEs like CVE-2026-126379 with a free CTEM certification.

Free to takePublicly verifiable

Beginner / Practitioner / Program Leader

Explore certifications