What is the CVSS score of CVE-2026-32114?

CVE-2026-32114 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N. EPSS exploitation probability: 0.0%.

Which versions of Discourse are affected by CVE-2026-32114?

Organizations using Discourse should be aware of moderate risk from CVE-2026-32114, a IDOR vulnerability rated CVSS 4.3. Exploitation could compromise the security of affected deployments.. A patch is available.

How to fix or mitigate CVE-2026-32114?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Discourse CVE-2026-32114

EUVD-2026-13526 MEDIUM

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-03-20 security-advisories@github.com

Authentication Bypass Discourse

4.3

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

4.3 MEDIUM

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

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Lifecycle Timeline

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.1.2,2026.2.1

EUVD ID Assigned

Mar 20, 2026 - 08:37 euvd

EUVD-2026-13526

Analysis Generated

Mar 20, 2026 - 08:37 vuln.today

CVE Published

Mar 20, 2026 - 04:16 nvd

MEDIUM 4.3

DescriptionGitHub Advisory

Discourse is an open-source discussion platform. Prior to versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, there is an Insecure Direct Object Reference (IDOR) vulnerability that allows any authenticated user to access metadata about AI personas, features, and LLM models by providing their identifiers. This information includes credit allocations and usage statistics which are not intended to be public. The attack is performed over the network, requires low privileges (any logged-in user), and results in a low impact on confidentiality with no impact on integrity or availability. Versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2 contain a patch. To work around this issue, disable AI plugin or upgrade to a patched version.

AnalysisAI

An Insecure Direct Object Reference (IDOR) vulnerability in Discourse allows any authenticated user to access restricted metadata about AI personas, features, and LLM models by directly referencing their identifiers, exposing sensitive information including credit allocations and usage statistics. The vulnerability affects Discourse versions prior to 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, and requires only low-privilege access (any logged-in user account) over the network. While the CVSS score of 5.3 indicates low confidentiality impact with no integrity or availability impact, this represents a clear information disclosure risk that could enable unauthorized tracking of AI resource consumption and usage patterns.

Technical ContextAI

This vulnerability is rooted in CWE-639 (Authorization Bypass Through User-Controlled Key), a class of authorization flaws where an application fails to properly validate that a user has permission to access objects they reference directly. In Discourse's context, the AI plugin exposes API endpoints that accept identifiers for AI personas, LLM models, and feature configurations without performing adequate authorization checks beyond simple authentication status. The affected technology involves Discourse's Ruby on Rails-based backend and its AI plugin components, which fail to enforce object-level access controls on metadata endpoints. An attacker can enumerate or guess identifiers and retrieve associated metadata without additional privileges beyond a valid user session, bypassing intended access restrictions on credit allocations and usage telemetry data that should be restricted to administrators or specific role holders.

RemediationAI

Upgrade Discourse to version 2026.3.0-latest.1, 2026.2.1, or 2026.1.2 or later, depending on your current version track, as these versions contain the authorization validation patch (see vendor advisory at https://github.com/discourse/discourse/security/advisories/GHSA-3cvr-pm4c-hx96). For deployments unable to patch immediately, disable the AI plugin through the Discourse admin settings panel to eliminate the attack surface entirely. If the AI plugin must remain enabled pending patching, implement network-level access controls to restrict access to Discourse to trusted users and networks, configure authentication to require strong credentials and multi-factor authentication where possible, and monitor API access logs for suspicious enumeration patterns targeting AI metadata endpoints. Patching should be prioritized as the permanent remediation given the ease of exploitation and the sensitive nature of the exposed data.