Skip to content
Noroxi
CVE-2026-32244· NVD / CVE Program· CNA GitHub_M

Discourse: Cached outdated summaries can leak removed content

Discourse 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.

MediumCVSS 5.3 · v3.1—No exploit No fix recorded
Published
May 18, 2026
Updated
Jul 24, 2026
EPSS
0.4% · 30th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
discoursediscourse

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • discourse discourse2026.1.0 and later · before 2026.1.4
  • discourse discourse2026.3.0 and later · before 2026.3.1
  • discourse discourse2026.4.0 and later · before 2026.4.1
  • discourse discourse2026.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • discourse discourse

    • < 2026.1.4, >= 2026.3.0-latest, < 2026.3.1, >= 2026.4.0-latest, < 2026.4.1, >= 2026.5.0-latest, < 2026.5.0-latest.1affected

Other highest-scoring records for the same primary product.

  • CVE-2021-41163RCE via malicious SNS subscription payload
    45Plan
  • CVE-2025-68662FinalDestination hostname matching allows SSRF protection bypass
    39Monitor
  • CVE-2023-47121Discourse SSRF vulnerability in Embedding
    39Monitor
  • CVE-2026-55674Discourse: Cache poisoning/XSS via color scheme cookies
    37Monitor
  • CVE-2026-53963Discourse: Stored-XSS in 2FA delete confirmation modal
    36Monitor
  • CVE-2024-49765Bypass of Discourse Connect using other login paths if enabled in Discourse
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-53991515 days apartPotential Backup file leaked via Nginx in Discourse
    32Monitor
  • CVE-2026-4478625 days apartDiscourse: Public chat MessageBus broadcasts are not restricted to chat-eligible users
    30Monitor
  • CVE-2025-46813378 days apartPrivate data leak on login-required Discourse sites
    30Monitor
  • CVE-2026-23743110 days apartDiscourse allows permalinks to restricted resources to leak resource slugs to unauthorized users
    27Monitor
  • CVE-2026-4478425 days apartDiscourse: Non-staff group owners can see email password in plaintext through group history
    26Monitor
  • CVE-2026-3335560 days apartDiscourse filters whisper posts from private-posts feed
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-secondary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records