Vulnerability Database · Bitnami · Package report

discourse: vulnerability history, versions and safety

discourse is a package in the Bitnami ecosystem. Vulert records 288 vulnerabilities for it across 64 affected ranges, from Jan 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
288 vulnerabilities recorded C6 H45 M208 L28 U1
i
20 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
138 in the last 12 months

Most recent disclosure 21 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on discourse i

Updated on 23 Oct 2026

Careful: 20 of the 288 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 288 vulnerabilities on record across 2 years, 138 in the last year.

What to do: Plan around the 20 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 288 over 2 years · 138 in the last year i
  • Latest disclosure 21 Oct 2026 i
  • Highest CVSS n/a i
  • With no published fix 20 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 2026.8.0 (exclusive) 8
up to 2026.7.0 (exclusive) 2
up to 2026.6.1 (exclusive) 1
up to 2026.3.0 (exclusive) 1
up to 2026.1.9 (exclusive) 3
up to 2026.1.7 (exclusive) 3
up to 2026.1.6 (exclusive) 13
from 2026.1.0 up to 2026.1.5 (exclusive) 11
from 2026.1.0 up to 2026.1.4 (exclusive) 11
up to 2026.1.4 (exclusive) 3
from 2026.1.0 up to 2026.1.3 (exclusive) 17
from 2026.1.0 up to 2026.1.2 (exclusive) 32
up to 2025.12.2 (exclusive) 17
up to 2021-09-14.0.0 (exclusive) 1
up to 3.6.2 (exclusive) 1
up to 3.5.4 (exclusive) 14
up to 3.5.3 (exclusive) 1
up to 3.5.1 (exclusive) 3
up to 3.5.0 (exclusive) 2
up to 3.4.7 (exclusive) 1
up to 3.4.6 (exclusive) 1
up to 3.4.4 (exclusive) 3
up to 3.4.3 (exclusive) 1
up to 3.4.0 (exclusive) 5
up to 3.3.3 (exclusive) 7
up to 3.3.2 (exclusive) 6
up to 3.3.1 (exclusive) 1
up to 3.2.5 (exclusive) 2
up to 3.2.3 (exclusive) 7
up to 3.2.1 (exclusive) 5
up to 3.2.0 (exclusive) 6
up to 3.1.4 (exclusive) 3
from 3.1.0 up to 3.1.3 (exclusive) 1
up to 3.1.1 (exclusive) 3
up to 3.1.0 (exclusive) 9
up to 3.0.6 (exclusive) 5
up to 3.0.5 (exclusive) 2
up to 3.0.4 (exclusive) 4
up to 3.0.3 (exclusive) 1
up to 3.0.1 (exclusive) 9
up to 3.0.0 (exclusive) 1
up to 2.9.0 (exclusive) 2
up to 2.8.14 (exclusive) 7
up to 2.8.13 (exclusive) 2
up to 2.8.10 (exclusive) 3
up to 2.8.9 (exclusive) 4
up to 2.8.8 (exclusive) 1
up to 2.8.7 (exclusive) 1
up to 2.8.4 (exclusive) 2
up to 2.8.3 (exclusive) 3
up to 2.8.2 (exclusive) 1
up to 2.8.1 (exclusive) 1
up to 2.7.13 (exclusive) 3
up to 2.7.12 (exclusive) 1
up to 2.7.11 (exclusive) 3
up to 2.7.9 (exclusive) 1
up to 2.7.8 (exclusive) 4
up to 2.7.7 (exclusive) 1
from 2.3.2 up to 2.3.3 (exclusive) 1
all releases, no fix published yet 16
from 2.9.0-beta5 onwards, no fix published yet 1
from 3.1.0-beta2 onwards, no fix published yet 1
from 3.1.0-beta5 onwards, no fix published yet 1
from 1.1.0-beta1 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 129
  • 2025 22
  • 2026 137

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 138 of the 288 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About discourse

Is discourse safe to use?

Vulert records 288 vulnerabilities for discourse in Bitnami: 6 critical, 45 high, 208 medium and 28 low, plus 1 not yet rated. 20 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does discourse have?

288 vulnerabilities are recorded for discourse in the Bitnami ecosystem: 6 critical, 45 high, 208 medium and 28 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new discourse vulnerabilities disclosed?

138 vulnerabilities were recorded for discourse in the last 12 months, and the oldest entry in this database dates to 31 Jan 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of discourse are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor discourse for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the discourse version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.