# CVE-2026-64626: AVideo Encoder downloadURL SSRF via unpinned retry fallback

> Authenticated attackers can exploit an unpinned retry fallback in AVideo's encoder to perform blind SSRF attacks against internal network targets.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-fr98-mjq9-7jmj, GHSA-rqr2-9jm2-2q9j

## What is CVE-2026-64626?

CVE-2026-64626 is a medium-severity server-side request forgery vulnerability in WWBN AVideo, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AVideo versions from commit 0dbadbca through latest master contain a server-side request forgery vulnerability in the encoder download-by-URL flow due to an unpinned retry fallback that bypasses DNS pinning validation. An authenticated attacker can supply a downloadURL that redirects to an internal address, causing the unpinned retry to follow the redirect and reach internal targets for blind SSRF attacks.

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

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


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

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

## Is CVE-2026-64626 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64626 is a medium-severity server-side request forgery vulnerability in WWBN AVideo, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-64626 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-64626/ (Markdown: https://insights.sbomify.com/CVE-2026-64626/index.md)
```

## Sources

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

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