CVE-2026-59828

Discourse: Hidden post revisions leak through adjacent visible diffs

MEDIUM
5.3
CVSS Score
Published: July 9, 2026 at 10:04 PM UTC
Updated: July 13, 2026 at 03:41 PM UTC
1 product affected across 1 vendorDiscourse

Using discourse by discourse?

Get instant alerts when new vulnerabilities affect discourse - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

Discourse is an open-source discussion platform. Prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5, post revisions that should be hidden from regular users could be leaked through visible diffs on adjacent revisions serialized by PostRevisionSerializer. This issue is fixed in versions 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2026.1.5v < 2026.4.2v < 2026.5.12026.1.0 ≤ v < 2026.1.52026.4.0 ≤ v < 2026.4.22026.5.0 ≤ v < 2026.5.12026.6.0
Affected range stops below 2026.1.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 2026.4.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 2026.5.1, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card