● Low · CVSS 1.3

How to Fix CVE-2026-27150: Missing authorization in discourse

Q: What is the CVSS score for CVE-2026-27150?

1.3 (Low). Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U`.

Q: Where is the official advisory for CVE-2026-27150?

The vendor advisory is at [https://github.com/discourse/discourse/security/advisories/GHSA-rw95-54qr-qrw8](https://github.com/discourse/discourse/security/advisories/GHSA-rw95-54qr-qrw8). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27150.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27150 is a missing authorization in discourse discourse. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	1.3 (Low)
Actively exploited?	No public listing in CISA KEV
Affected	discourse < 2025.12.2; discourse >= 2026.1.0-latest, < 2026.1.1; discourse >= 2026.2.0-latest, < 2026.2.0
Fixed in	See vendor advisory
Type (CWE)	CWE-862: Missing Authorization

What is CVE-2026-27150?

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, missing validate_before_create authorization in Data Explorer's QueryGroupBookmarkable allows any logged-in user to create bookmarks for query groups they don't have access to, enabling metadata disclosure via bookmark reminder notifications. Versions 2025.12.2, 2026.1.1, and 2026.2.0 fix this issue and also make sure validate_before_create throws NotImplementedError in BaseBookmarkable if not implemented, to prevent similar issues in the future. No known workarounds are available. The CVSS base score is 1.3 (Low). The official advisory is at https://github.com/discourse/discourse/security/advisories/GHSA-rw95-54qr-qrw8.

Am I affected?

Check the version of discourse you are running and compare it against the Affected row above (discourse < 2025.12.2; discourse >= 2026.1.0-latest, < 2026.1.1; discourse >= 2026.2.0-latest, < 2026.2.0). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s discourse 2>/dev/null | grep -i ^Version
rpm -q discourse 2>/dev/null
command -v discourse >/dev/null && discourse --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*discourse*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "discourse" 2>$null

How to fix CVE-2026-27150

Upgrade discourse to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade discourse
dpkg -s discourse | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh discourse -y
# or for older releases:
sudo yum update discourse -y
rpm -q discourse

SUSE / openSUSE


sudo zypper refresh
sudo zypper update discourse
rpm -q discourse

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-27150 affecting discourse
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27150-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*discourse*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\discourse-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\discourse" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "discourse" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "discourse"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-27150 affecting discourse
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27150-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s discourse 2>/dev/null | grep -i ^Version || echo "discourse not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q discourse || echo "discourse not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27150-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/discourse /etc/discourse.d /etc/discourse.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y discourse
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y discourse
elif command -v yum >/dev/null; then
    yum update -y discourse
elif command -v zypper >/dev/null; then
    zypper --non-interactive update discourse
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s discourse 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q discourse
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-27150" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27150"

Disable the affected service (Linux)


sudo systemctl stop discourse 2>/dev/null || true
sudo systemctl disable discourse 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s discourse 2>/dev/null | grep -i ^Version
rpm -q discourse 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*discourse*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-21716: Critical Vulnerability in node — Critical Vulnerability in node
How to Fix CVE-2026-6199: Stack buffer overflow in F456 — Stack buffer overflow in F456
How to Fix CVE-2026-30579: Critical Vulnerability in n/a , Critical Vulnerability in n/a
How to Fix CVE-2026-1298: Critical Vulnerability in Easy Replace Image , Critical Vulnerability in Easy Replace Image
How to Fix CVE-2026-45010: Critical Vulnerability in phpmyfaq , Critical Vulnerability in phpmyfaq

Is CVE-2026-27150 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27150?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-27150?

1.3 (Low). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U.

Where is the official advisory for CVE-2026-27150?

The vendor advisory is at https://github.com/discourse/discourse/security/advisories/GHSA-rw95-54qr-qrw8. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27150.

References

Official vendor advisory: https://github.com/discourse/discourse/security/advisories/GHSA-rw95-54qr-qrw8
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27150
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*