BigBlueButton vulnerabilities: known CVEs & security history
BigBlueButton · Comms / Conferencing · 49 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all BigBlueButton release lines — 49 in total. A CVE here doesn't mean your version is affected — check BigBlueButton's current status and the safe version to run.
Known BigBlueButton CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2020-27602 | critical | 9.8 | 1% | 2022 |
| CVE-2020-27605 | critical | 9.8 | 1% | 2020 |
| CVE-2020-12443 | critical | 9.8 | 4% | 2020 |
| CVE-2020-27613 | high | 8.4 | 0% | 2020 |
| CVE-2025-61602 | high | 7.5 | 0% | 2025 |
| CVE-2025-61601 | high | 7.5 | 0% | 2025 |
| CVE-2022-29169 | high | 7.5 | 1% | 2022 |
| CVE-2020-29043 | high | 7.5 | 1% | 2020 |
| CVE-2020-27610 | high | 7.5 | 1% | 2020 |
| CVE-2020-27603 | high | 7.5 | 3% | 2020 |
| CVE-2020-12112 | high | 7.5 | 5% | 2020 |
| CVE-2020-27611 | high | 7.3 | 1% | 2020 |
| CVE-2026-27466 | high | 7.2 | 0% | 2026 |
| CVE-2025-55200 | high | 7.1 | 0% | 2025 |
| CVE-2022-23488 | medium | 6.5 | 1% | 2022 |
| CVE-2022-31065 | medium | 6.5 | 1% | 2022 |
| CVE-2022-31064 | medium | 6.5 | 1% | 2022 |
| CVE-2022-29232 | medium | 6.5 | 1% | 2022 |
| CVE-2020-27607 | medium | 6.5 | 1% | 2020 |
| CVE-2020-27604 | medium | 6.5 | 1% | 2020 |
| CVE-2020-25820 | medium | 6.5 | 9% | 2020 |
| CVE-2023-43797 | medium | 6.3 | 0% | 2023 |
| CVE-2026-27736 | medium | 6.1 | 0% | 2026 |
| CVE-2021-4143 | medium | 6.1 | 1% | 2022 |
| CVE-2020-27608 | medium | 6.1 | 1% | 2020 |
| CVE-2020-12113 | medium | 6.1 | 1% | 2020 |
| CVE-2022-41964 | medium | 5.7 | 1% | 2022 |
| CVE-2023-43798 | medium | 5.6 | 0% | 2023 |
| CVE-2022-27238 | medium | 5.4 | 0% | 2022 |
| CVE-2023-42803 | medium | 5.3 | 1% | 2023 |
| CVE-2022-29235 | medium | 5.3 | 1% | 2022 |
| CVE-2020-28954 | medium | 5.3 | 1% | 2020 |
| CVE-2020-27609 | medium | 5.3 | 1% | 2020 |
| CVE-2020-27606 | medium | 5.3 | 1% | 2020 |
| CVE-2023-33176 | medium | 4.8 | 0% | 2023 |
| CVE-2022-23490 | medium | 4.3 | 0% | 2022 |
| CVE-2022-41961 | medium | 4.3 | 0% | 2022 |
| CVE-2022-41960 | medium | 4.3 | 0% | 2022 |
| CVE-2022-29236 | medium | 4.3 | 1% | 2022 |
| CVE-2022-29234 | medium | 4.3 | 1% | 2022 |
| CVE-2022-29233 | medium | 4.3 | 1% | 2022 |
| CVE-2020-28953 | medium | 4.3 | 1% | 2020 |
| CVE-2020-27612 | medium | 4.3 | 1% | 2020 |
| CVE-2020-29042 | low | 3.7 | 1% | 2020 |
| CVE-2020-27601 | low | 3.5 | 1% | 2022 |
| CVE-2023-42804 | low | 3.1 | 0% | 2023 |
| CVE-2022-41963 | low | 2.7 | 0% | 2022 |
| CVE-2022-41962 | low | 2.7 | 1% | 2022 |
| CVE-2026-27467 | low | 2 | 0% | 2026 |
Is my BigBlueButton version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your BigBlueButton version → · Monitor BigBlueButton for new CVEs →
BigBlueButton vulnerabilities — frequently asked
How many known vulnerabilities does BigBlueButton have?
IsItPatched tracks 49 CVEs for BigBlueButton. 3 are critical-severity and 11 high-severity. These span every release line — what matters is whether the version you run is affected.
Does BigBlueButton have any actively-exploited vulnerabilities?
None of BigBlueButton's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe BigBlueButton vulnerability?
Among tracked issues, CVE-2020-27602 (CRITICAL, CVSS 9.8) ranks highest — a Injection weakness.
Is BigBlueButton safe to use?
It depends on the version. The latest supported BigBlueButton release (3.0.29) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: BigBlueButton security status · BigBlueButton end-of-life · actively-exploited CVEs. Always verify against BigBlueButton's advisories — see our disclaimer.