CVE-2026-26265
A public proof of concept exists; no exploitation attested.
- Published2026-02-26
- Fixed in2026.1.1 · 2025.12.2 · 2025.12.0
- WeaknessCWE-639 · CWE-863
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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=<id>` 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.
Timeline
dates in UTC- 2026-02-2616:24CVE publishedNVD
Versions per branch
NVD · OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2026.1 | ≥ 2026.1.0, < 2026.1.1 | 2026.1.1 | NVD · OSV |
| 2025.12 | < 2025.12.2 | 2025.12.2 | OSV |
| 2025.12 | < 2025.12.0 | 2025.12.0 | NVD |
| 2026.2 | = 2026.2.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- discourseAffected
- = < 2025.12.2no fix stated
- = >= 2026.1.0-latest, < 2026.1.1no fix stated
- = >= 2026.2.0-latest, < 2026.2.0no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-02-26
Fix
- Update Discourse to 2026.1.1 · 2025.12.2 · 2025.12.0
Advisories and patches
- github.comVendor Advisory
Detection
read 2026-11-19 10:48 UTC- Nuclei template
- available ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-19
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionnone2026-02-27
- CNACVSS 3.17.5known since 2026-10-23
- CNAweakness (CWE)CWE-863known since 2026-10-23
- NVDweakness (CWE)CWE-639read 2026-10-23
- FIRST EPSSEPSS score1.3 %2026-11-18
- ProjectDiscoverydetectionread 2026-11-19
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- BIT-discourse-2026-26265same flawBitnami · Apache-2.0
- EUVD-2026-8859same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-crxf-p6jm-vpgwsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Published
- 2026-02-26
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
- GitHub Advisory
- GHSA-crxf-p6jm-vpgw
Frequently asked questions
What is CVE-2026-26265?
Is CVE-2026-26265 actively exploited?
What is the CVSS score for CVE-2026-26265?
Running discourse? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-crxf-p6jm-vpgw
- Nuclei templates · MIT
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0