# CVE-2026-84476: WWBN AVideo Authentication Bypass via X-Real-IP Header

> Attackers can bypass login rate limiting by spoofing IP headers, enabling unlimited credential guessing and potential account takeover.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/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-gg65-574p-h4wc, GHSA-mm87-mmw2-x2jf

## What is CVE-2026-84476?

CVE-2026-84476 is a high-severity 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 fails to validate trusted proxies before accepting X-Real-IP and X-Forwarded-For headers, allowing attackers to spoof the client address used by enforceRateLimit(). Attackers can rotate the header value per request to bypass login rate limiting and perform unlimited credential guessing attacks.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-84476 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84476 is a high-severity 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-84476 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-84476/ (Markdown: https://insights.sbomify.com/CVE-2026-84476/index.md)
```

## Sources

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

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