CVE-2026-44782
June 12, 2026, 9:16 p.m.
4.3
Medium
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.
Product(s) Impacted
| Vendor | Product | Versions |
|---|---|---|
| Discourse |
|
|
Weaknesses
Common security weaknesses mapped to this vulnerability.
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
*CPE(s)
Affected systems and software identified for this CVE.
| Type | Vendor | Product | Version | Update | Edition | Language | Software Edition | Target Software | Target Hardware | Other Information |
|---|---|---|---|---|---|---|---|---|---|---|
| a | discourse | discourse | 2026.1.0-2026.1.4 | / | / | / | / | / | / | / |
| a | discourse | discourse | 2026.3.0-2026.3.1 | / | / | / | / | / | / | / |
| a | discourse | discourse | 2026.4.0-2026.4.1 | / | / | / | / | / | / | / |
| a | discourse | discourse | 2026.1.4 | / | / | / | / | / | / | / |
| a | discourse | discourse | 2026.3.1 | / | / | / | / | / | / | / |
| a | discourse | discourse | 2026.4.1 | / | / | / | / | / | / | / |
| a | discourse | discourse | 2026.5.0-latest.1 | / | / | / | / | / | / | / |
Tags
CVSS Score
CVSS Data - 3.1
- Attack Vector: NETWORK
- Attack Complexity: LOW
- Privileges Required: LOW
- Scope: UNCHANGED
- Confidentiality Impact: LOW
- Integrity Impact: NONE
- Availability Impact: NONE
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Timeline
Published: June 12, 2026, 9:16 p.m.
Last Modified: June 12, 2026, 9:16 p.m.
Last Modified: June 12, 2026, 9:16 p.m.
Status : Received
CVE has been recently published to the CVE List and has been received by the NVD.
More infoSource
*Disclaimer: Some vulnerabilities do not have an associated CPE. To enhance the data, we use AI to infer CPEs based on CVE details. This is an automated process and might not always be accurate.