# CVE-2026-46404: BigBlueButton: Presentation URL Security Hardening

> Attackers can exploit insufficient URL validation to access internal network resources via Server-Side Request Forgery in BigBlueButton.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-xqm3-6q7q-4v5h

## What is CVE-2026-46404?

CVE-2026-46404 is a medium-severity server-side request forgery vulnerability in bigbluebutton, published on 16 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

BigBlueButton is an open-source virtual classroom. Prior to 3.0.23, the presentation URL validation did not properly restrict access to site local and link local addresses. The redirect following logic now pins resolved IPs. This issue is fixed in version 3.0.23.

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

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


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

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

## Is CVE-2026-46404 being exploited?

There is no known exploitation of CVE-2026-46404 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46404 is a medium-severity server-side request forgery vulnerability in bigbluebutton, published on 16 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46404 in the wild and no public exploit code.

Affected product: bigbluebutton. 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-46404/ (Markdown: https://insights.sbomify.com/CVE-2026-46404/index.md)
```

## Sources

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

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