Incorrect Serialization of User Names in Discourse Group Posts

Publication date: 2026-06-12

Last updated on: 2026-06-15

Assigner: GitHub, Inc.

Description

Discourse is an open-source discussion platform. From versions 2026.1.0-latest to before 2026.1.4, 2026.3.0-latest to before 2026.3.1, and 2026.4.0-latest to before 2026.4.1, GroupPostSerializer declared include_user_long_name? as the predicate for its :name attribute, but AMS looks for include_name?. The misnamed predicate was never called, so object.user.name was always serialized regardless of SiteSetting.enable_names. This issue has been patched in versions 2026.1.4, 2026.3.1, 2026.4.1, and 2026.5.0-latest.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-12

Last Modified

2026-06-15

Generated

2026-07-03

AI Q&A

2026-06-13

EPSS Evaluated

2026-07-01

NVD

CVE-2026-44782

Affected Vendors & Products

Vendor	Product	Version / Range
discourse	discourse	From 2026.1.0 (inc) to 2026.1.4 (exc)
discourse	discourse	From 2026.3.0 (inc) to 2026.3.1 (exc)
discourse	discourse	From 2026.4.0 (inc) to 2026.4.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-200	The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Discourse open-source discussion platform in certain versions before 2026.1.4, 2026.3.1, and 2026.4.1. The issue is due to a misnamed predicate method in the GroupPostSerializer component. Specifically, the serializer declared include_user_long_name? as the predicate for its :name attribute, but the Authorization Management System (AMS) expects include_name?. Because the correct predicate was never called, the user's full name (object.user.name) was always serialized regardless of the SiteSetting.enable_names configuration.

Impact Analysis

The impact of this vulnerability is that user full names are always included in serialized data, even when the site setting to enable names is disabled. This could lead to unintended disclosure of user full names, potentially exposing personal information that users or administrators intended to keep private.

Mitigation Strategies

To mitigate this vulnerability, update your Discourse installation to one of the patched versions: 2026.1.4, 2026.3.1, 2026.4.1, or 2026.5.0-latest.1.

Hi! I’m here to help you understand CVE-2026-44782. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70