# CVE-2026-91967: AVideo through 29.0 Blind SSRF via getHeaderContentTypeFromURL

> Authenticated users can exploit blind SSRF in AVideo to probe internal hosts via crafted video links, potentially exposing internal network information.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/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:** 15 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-c7vx-mcw6-m8m4, GHSA-vjgr-5x63-cq96

## What is CVE-2026-91967?

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

### Official description

AVideo through 29.0 contains a blind server-side request forgery vulnerability in the getHeaderContentTypeFromURL function that issues get_headers() calls guarded only by format validation. Authenticated users with canUpload permission can store attacker-chosen URLs as video links, triggering vulnerable function execution on every video watch page render to probe internal hosts using content-type oracles and timing-based detection.

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

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


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

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

## Is CVE-2026-91967 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91967 is a medium-severity server-side request forgery vulnerability in WWBN AVideo, published on 15 Sep 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-91967 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-91967/ (Markdown: https://insights.sbomify.com/CVE-2026-91967/index.md)
```

## Sources

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

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