Internal data disclosure via IPv6 SSRF guard bypass
Published Oct 1, 2026 · Updated Oct 1, 2026
SSRF in the editor oEmbed proxy in givanz Vvveb 1.0.8.5 and earlier allows remote authenticated users to read internal HTTP responses. The validateUrl() guard checks only IPv4 addresses, so an IPv6 literal or AAAA-only host passes its private-range check before getUrl() fetches the URL and the proxy returns the response body. Admin-panel access with the site_admin role or higher is required; exposed responses can include internal service data or cloud metadata credentials.
Summary
What happened
SSRF in the editor oEmbed proxy in givanz Vvveb 1.0.8.5 and earlier allows remote authenticated users to read internal HTTP responses. The validateUrl() guard checks only IPv4 addresses, so an IPv6 literal or AAAA-only host passes its private-range check before getUrl() fetches the URL and the proxy returns the response body. Admin-panel access with the site_admin role or higher is required; exposed responses can include internal service data or cloud metadata credentials.
The record
- CVE
- CVE-2026-55232
- Published
- Oct 1, 2026
- Updated
- Oct 1, 2026
- Vendor
- givanz
- Product
- Vvveb
- Classifications
- CWE-918, T1552.005
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Oct 1, 2026CVE publishedPublication date reported by the CVE source.
- Oct 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.8.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Upstream advisory IPv6 oEmbed proxy proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started