# CVE-2026-84479: WWBN AVideo Authentication Bypass via User-Agent Header

> Attackers can bypass two-factor authentication and audit logging by spoofing the User-Agent header in WWBN AVideo.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-5vfg-9qx8-h8wf, GHSA-m9m3-gwh2-337c

## What is CVE-2026-84479?

CVE-2026-84479 is a critical authentication bypass vulnerability in WWBN AVideo, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WWBN AVideo (current e01e41ecc and earlier) makes three login-time security controls depend solely on the client-supplied User-Agent header. The isAVideoEncoder()/isAVideoMobileApp() checks match HTTP_USER_AGENT against a hardcoded literal ("AVideoEncoder"/"AVideoMobileApp") with no IP check or shared secret. An attacker who submits valid credentials and sets User-Agent: AVideoEncoder bypasses two-factor authentication, skips brute-force captcha escalation, and avoids being recorded in the login/device audit history. No patch is available at the time of publication.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-84479 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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