# CVE-2026-86722: AVideo Authentication Bypass via SQL Cache Invalidation

> Attackers with valid passwords can bypass email two-factor authentication on new devices due to stale SQL cache invalidation in AVideo.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/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:** 8 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-c785-w9vv-8rm9, GHSA-wmhg-p72j-72gf

## What is CVE-2026-86722?

CVE-2026-86722 is a high-severity authentication bypass vulnerability in WWBN AVideo, published on 8 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 contains an authentication bypass vulnerability where sqlDAL caches empty result sets that writeSql never invalidates. Attackers with a valid password can bypass email two-factor authentication on new devices because the confirmation code hash fails to generate from the stale cached empty result.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-86722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86722 is a high-severity authentication bypass vulnerability in WWBN AVideo, published on 8 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-86722 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-86722/ (Markdown: https://insights.sbomify.com/CVE-2026-86722/index.md)
```

## Sources

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

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