{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-26973","id":"CVE-2026-26973","title":"Discourse doesn't scope reviewable notes to user-visible reviewables","description":"Discourse is an open source discussion platform. Versions prior to 2025.12.2, 2026.1.1, and 2026.2.0 have an IDOR (Insecure Direct Object Reference) in `ReviewableNotesController`. When `enable_category_group_moderation` is enabled, a user belonging to a  category moderation group can create or delete their own notes on **any** reviewable in the system, including reviewables in categories they do ","descriptionLong":"Discourse is an open source discussion platform. Versions prior to 2025.12.2, 2026.1.1, and 2026.2.0 have an IDOR (Insecure Direct Object Reference) in `ReviewableNotesController`. When `enable_category_group_moderation` is enabled, a user belonging to a  category moderation group can create or delete their own notes on **any** reviewable in the system, including reviewables in categories they do not moderate. The controller used an unscoped `Reviewable.find` and the `ensure_can_see` guard only checked whether the user could access the review queue in general, not whether they could access the specific reviewable. Only instances with `enable_category_group_moderation` enabled are affected. Staff users (admins/moderators) are not impacted as they already have access to all reviewables. The issue is patched in versions 2025.12.2, 2026.1.1, and 2026.2.0 by scoping the reviewable lookup through `Reviewable.viewable_by(current_user)`. As a workaround, disable the `enable_category_group_moderation` site setting. This removes the attack surface as only staff users will have access to the review queue.","published":"2026-02-26T19:19:18.139Z","updated":"2026-10-28T02:31:07.236111300Z","reserved":"2026-02-16T22:20:28.612Z","status":"Analyzed","rejected":false,"assigner":"GitHub_M","metric":{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"GitHub_M"},"metrics":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"GitHub_M"},{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"github.com"},{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","rating":"medium","source":"OSV"}],"rating":"medium","products":["discourse"],"affectedProducts":[{"vendor":"discourse","product":"discourse","defaultStatus":null,"versions":[{"version":"< 2025.12.2","status":"affected"},{"version":">= 2026.1.0-latest, < 2026.1.1","status":"affected"},{"version":">= 2026.2.0-latest, < 2026.2.0","status":"affected"}],"platforms":[]}],"packages":[],"cwes":["CWE-863","CWE-639"],"aliases":["BIT-discourse-2026-26973","GHSA-c587-qx78-vhmx"],"references":[{"url":"https://github.com/discourse/discourse/security/advisories/GHSA-c587-qx78-vhmx","tags":["x_refsource_CONFIRM","Vendor Advisory","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/26xxx/CVE-2026-26973.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-26973","tags":["advisory"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"},"epss":0.00177,"epssPercentile":0.07316,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-26973","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-26973","ok":true,"note":"Analyzed"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-26973","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-26973","ok":true,"note":"scored 2026-11-19"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}