Skip to content
Vulnerability Intelligence

CVE-2026-26265

High

Discourse has IDOR vulnerability in the directory items endpoint

Published Feb 26, 2026 · Updated Oct 6, 2026 · Also known as BIT-discourse-2026-26265, GHSA-crxf-p6jm-vpgw

Key Facts

Patch in the next maintenance window
  • CVE-2026-26265 is a high-severity vulnerability (CVSS 7.5 v3.1) affecting Discourse.
  • It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
  • EPSS estimates a 1.5% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Discourse 2025.12.2, Discourse 2026.1.1, Discourse 2025.12.0.
  • Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

CVSS v3.1

7.5

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

EPSS (30-day exploit likelihood)

1.5%

Higher than 73.5% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

None known

Get the full CVE-2026-26265 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, an IDOR vulnerability in the directory items endpoint allows any user, including anonymous users, to retrieve private user field values for all users in the directory. The user_field_ids parameter in DirectoryItemsController#index accepts arbitrary user field IDs without authorization checks, bypassing the visibility restrictions (show_on_profile / show_on_user_card) that are enforced elsewhere (e.g., UserCardSerializer via Guardian#allowed_user_field_ids). An attacker can request GET /directory_items.json?period=all&user_field_ids= with any private field ID and receive that field's value for every user in the directory response. This enables bulk exfiltration of private user data such as phone numbers, addresses, or other sensitive custom fields that admins have explicitly configured as non-public. The issue is patched in versions 2025.12.2, 2026.1.1, and 2026.2.0 by filtering user_field_ids against UserField.public_fields for non-staff users before building the custom field map. As a workaround, site administrators can remove sensitive data from private user fields, or disable the user directory via the enable_user_directory site setting.

Affected Products

4 affected entries in total
ProductAffected versionsFixed in
DiscourseDiscourse2026.2.0, >= < 2025.12.22025.12.0

Patched Releases

Discourse

2025.12.2, 2026.1.1, 2025.12.0

Timeline

  1. Publicly disclosed

    Feb 26, 2026

  2. Last updated

    Oct 6, 2026

Weakness Type

  • CWE-639 Authorization Bypass Through User-Controlled Key
  • CWE-863 Incorrect Authorization

References

FAQ

Common Questions.

Is CVE-2026-26265 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.

Request A Demo