CVE-2026-32244
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDiscourse is an open-source discussion platform. In versions prior to 2026.1.4, 2026.3.1, 2026.4.1 and 2026.5.0-latest.1, outdated cached AI summaries can leak removed content to anonymous and unprivileged users who cannot regenerate summaries. This issue has been fixed in versions 2026.1.4, 2026.3.1, 2026.4.1 and 2026.5.0-latest.1. To work around this issue, restrict summary generation by tightening the allowed groups on the summarization Personas.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an information disclosure vulnerability in Discourse where cached AI summaries retain content that has been subsequently removed or deleted. Anonymous and unprivileged users who cannot regenerate summaries are served outdated cached versions containing content they should no longer have access to.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2026.1.0, < 2026.1.4>= 2026.3.0, < 2026.3.1>= 2026.4.0, < 2026.4.1= 2026.5.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Discourse versionCheck the installed Discourse version by navigating to /admin/about in the admin panel or by checking the version file in the Discourse installation directoryAffected if The installed version falls within any of these ranges: >= 2026.1.0 and < 2026.1.4, >= 2026.3.0 and < 2026.3.1, >= 2026.4.0 and < 2026.4.1, or exactly 2026.5.0
-
Confirm AI summarization is enabledNavigate to the admin panel, go to AI settings or Personas configuration, and verify whether AI summarization features are turned on for any groupAffected if AI summarization functionality is enabled for any user group in the system
-
Review summarization Persona permissionsIn admin settings under AI or Personas, examine which groups are allowed to generate and view summaries. Check if anonymous users or low-privilege groups have access to summarization featuresAffected if Anonymous users or unprivileged groups are permitted to access or view AI-generated summaries
-
Inspect cached summary storageExamine the database or cache storage where AI summaries are stored. Look for cached summaries associated with content that has since been deleted, archived, or had access restrictions appliedAffected if Cached summaries exist for content that has been removed, archived, or had its access permissions restricted after the summary was generated
You are affected if running an affected Discourse version with AI summarization enabled, where cached AI summaries can be accessed by anonymous or unprivileged users after the underlying content has been removed or restricted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.1.42026.3.12026.4.1
Upgrade to Discourse versions 2026.1.4, 2026.3.1, 2026.4.1, or 2026.5.0-latest.1. As a workaround, restrict summary generation by tightening allowed groups on the summarization Personas in the admin panel.
Upgrade to the latest fixed version for your branch: 2026.1.4, 2026.3.1, 2026.4.1, or 2026.5.0-latest.1 (recommended)
- 1. Identify your current Discourse version by checking the admin panel or running discourse/launcher logs
- 2. Determine which upgrade path applies based on your current version: if on 2026.1.x upgrade to 2026.1.4, if on 2026.3.x upgrade to 2026.3.1, if on 2026.4.x upgrade to 2026.4.1, or if on 2026.5.0 upgrade to 2026.5.0-latest.1
- 3. Back up your Discourse instance including database and uploads before upgrading
- 4. Run the Discourse upgrade command or use your deployment method (e.g., discourse/launcher rebuild app for Docker installations)
- 5. After upgrade, verify the new version is installed by checking the admin panel
- 6. As an additional precaution, verify that the summarization Personas settings have appropriately restricted groups configured to prevent access to sensitive content
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32244 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32244 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data