Skip to main content
VulnerabilityPublished Updated

CVE-2026-55232: givanz Vvveb · Server-Side Request Forgery (SSRF)

Affects givanz VvvebSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 1.0.8.6 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.8.6
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade Vvveb and givanz/Vvveb to 1.0.8.6.

Affected software

ProductAffectedFixed in
givanzVvvebAffected
  • <1.0.8.6
Fixed in
  • 1.0.8.6
GitHubgivanz/Vvvebpkg:github/givanz/VvvebOther threatsAffected
  • <1.0.8.6
Fixed in
  • 1.0.8.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vvveb to version 1.0.8.6 or later, where this SSRF vulnerability has been patched. No other mitigation is required as the fix is official and complete.

Description

Vvveb CMS versions prior to 1.0.8.6 contain a Server-Side Request Forgery (SSRF) vulnerability. The SSRF guard only resolves IPv4 addresses and does not inspect IPv6 addresses, allowing authenticated admin users to bypass private-range checks using IPv6 literals or domains with only AAAA records. This enables reading of internal-only services and cloud metadata, including IAM credentials. The issue is patched in version 1.0.8.6.

References

Community reviews

Loading reviews…