# CVE-2026-81678: AVideo SSRF Guard Bypass via IPv6 Transition Addresses

> Unauthenticated attackers can bypass SSRF protections in AVideo to access internal services and cloud metadata by exploiting IPv6 transition address formats.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** GHSA-474r-333v-6p93, GHSA-pmq2-hv69-w45g

## What is CVE-2026-81678?

CVE-2026-81678 is a medium-severity server-side request forgery vulnerability in WWBN AVideo, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AVideo before 24.0 contains a server-side request forgery vulnerability in the isSSRFSafeURL function that fails to extract embedded IPv4 addresses from NAT64, 6to4, and Teredo IPv6 transition address formats. Unauthenticated attackers can bypass SSRF protections via the LiveLinks proxy endpoint to reach internal services and cloud metadata endpoints by encoding private IPv4 targets in transition address formats.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-81678?


## How do I fix CVE-2026-81678?

No fix has been published for CVE-2026-81678 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-81678 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81678 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-81678 and fix it if it is affected.

What it is: CVE-2026-81678 is a medium-severity server-side request forgery vulnerability in WWBN AVideo, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81678 exists.

Affected product: WWBN AVideo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-81678/ (Markdown: https://insights.sbomify.com/CVE-2026-81678/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-81678
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-81678
- OSV: https://osv.dev/vulnerability/CVE-2026-81678

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-81678/
Summaries are generated and may contain mistakes; the official description above is the record.