---
id: "CVE-2026-126379"
page: "https://infrastack.ai/live/CVE-2026-126379"
kind: "vulnerability"
aliases: ["CVE-2026-126379"]
title: "Vvveb: incomplete SSRF fix lets admins reach internal services"
severity: "high"
cvss: 8.3
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "Vvveb", "fixed": [], "affected": "1.0.8.6", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["cms", "package", "self-hosted", "vvveb"]
not_affected_if: ["auth-required", "no-internal-services-reachable", "no-untrusted-admins"]
published_at: "2026-11-13T10:17:40+00:00"
first_seen_at: "2026-11-13T10:47:17+00:00"
updated_at: "2026-11-13T10:52:14+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126379", "first_seen_at": "2026-11-13T10:47:17+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-13T10:52:14+00:00"}]
exploit_sources: []
---

# Vvveb: incomplete SSRF fix lets admins reach internal services

Link for people: https://infrastack.ai/live/CVE-2026-126379 (this .md is for agents)

Vvveb 1.0.8.6 has an incomplete server-side request forgery fix in the editor's oEmbed proxy. An authenticated admin can use a DNS-rebinding hostname with a non-443 port to read loopback services, internal panels and cloud metadata credentials.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:Vvveb affected 1.0.8.6 fixed no fixed version listed

## How to check

- Run Vvveb 1.0.8.6? Check the installed version (composer show givanz/vvveb, or the version in the admin panel). Only 1.0.8.6 is listed as affected.
- Vulnerable code: in system/functions.php, validateUrl() builds CURLOPT_RESOLVE entries with a hard-coded ':443:' port.
- Anyone with an admin or editor login can call /admin/index.php?module=editor/editor&action=oEmbedProxy&url=... Review who holds those accounts.
- Check whether the Vvveb host can reach loopback services, internal panels or cloud metadata.

## Fix

No patched version listed in the maintainer advisory (GHSA-42hc-694f-hcqm) as of 2026-11-13. Until one ships, restrict admin/editor access and block the Vvveb server's egress to loopback, internal ranges and 169.254.169.254 (use IMDSv2 with hop limit 1 on AWS).

## Timeline

- 2026-11-13T10:47:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126379
- 2026-11-13T10:52:14+00:00 analyst — GHSA-42hc-694f-hcqm (maintainer advisory): affected 1.0.8.6, patched versions none. VulnCheck's range '<1.0.9.0' is not a fix statement; no fixed version confirmed. Root cause: validateUrl() builds CURLOPT_RESOLVE entries for port 443 only, so non-443 URLs are not pinned.

## Documents

- [advisory] Vendor advisory: github.com https://github.com/givanz/Vvveb/security/advisories/GHSA-42hc-694f-hcqm
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/vvveb-1.0.8.6-ssrf-via-oembed-proxy-dns-rebinding

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_