# CVE-2026-27466: BigBlueButton: Exposed ClamAV port enables Denial of Service

> Remote attackers can cause denial of service by exploiting exposed ClamAV ports resulting from flawed documentation instructions.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2026
- **Updated:** 24 Feb 2026
- **Also known as:** GHSA-wmhx-qw2p-w6gc

## What is CVE-2026-27466?

CVE-2026-27466 is a high-severity vulnerability in bigbluebutton, published on 21 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BigBlueButton is an open-source virtual classroom. In versions 3.0.21 and below, the official documentation for "Server Customization" on Support for ClamAV as presentation file scanner contains instructions that leave a BBB server vulnerable for Denial of Service. The flawed command exposes both ports (3310 and 7357) to the internet. A remote attacker can use this to send complex or large documents to clamd and waste server resources, or shutdown the clamd process. The clamd documentation explicitly warns about exposing this port. Enabling ufw (ubuntu firewall) during install does not help, because Docker routes container traffic through the nat table, which is not managed or restricted by ufw. Rules installed by ufw in the filter table have no effect on docker traffic. In addition, the provided example also mounts /var/bigbluebutton with write permissions into the container, which should not be required. Future vulnerabilities in clamd may allow attackers to manipulate files in that folder. Users are unaffected unless they have opted in to follow the extra instructions from BigBlueButton's documentation. This issue has been fixed in version 3.0.22.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Bigbluebutton Bigbluebutton.

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

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

## Is CVE-2026-27466 being exploited?

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

## Other vulnerabilities in bigbluebutton

- [CVE-2020-27602](https://insights.sbomify.com/CVE-2020-27602/): Other in n/a (critical 9.8)
- [CVE-2020-27605](https://insights.sbomify.com/CVE-2020-27605/): Code injection in n/a (critical 9.8)
- [CVE-2020-12443](https://insights.sbomify.com/CVE-2020-12443/): Path traversal in n/a (critical 9.8)
- [CVE-2020-27613](https://insights.sbomify.com/CVE-2020-27613/): Hardcoded credentials in n/a (high 8.4)
- [CVE-2021-4143](https://insights.sbomify.com/CVE-2021-4143/): Cross-site Scripting (XSS) - Generic in bigbluebutton/bigbluebutton (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27466 is a high-severity vulnerability in bigbluebutton, published on 21 Feb 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-27466 exists.

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

## Sources

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

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