● Medium · CVSS 4.3

How to Fix CVE-2026-27839: Authorization bypass through user-controlled key in wger

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

4.3 (Medium). Vector: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`.

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

The vendor advisory is at [https://github.com/wger-project/wger/security/advisories/GHSA-g8gc-6c4h-jg86](https://github.com/wger-project/wger/security/advisories/GHSA-g8gc-6c4h-jg86). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27839.

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

CVE-2026-27839 is a authorization bypass through user-controlled key in wger-project wger. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	4.3 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	wger <= 2.4
Fixed in	See vendor advisory
Type (CWE)	CWE-639: Authorization Bypass Through User-Controlled Key

What is CVE-2026-27839?

wger is a free, open-source workout and fitness manager. In versions up to and including 2.4, three nutritional_values action endpoints fetch objects via Model.objects.get(pk=pk) — a raw ORM call that bypasses the user-scoped queryset. Any authenticated user can read another user's private nutrition plan data, including caloric intake and full macro breakdown, by supplying an arbitrary PK. Commit 29876a1954fe959e4b58ef070170e81703dab60e contains a fix for the issue. The CVSS base score is 4.3 (Medium). The official advisory is at https://github.com/wger-project/wger/security/advisories/GHSA-g8gc-6c4h-jg86.

Am I affected?

Check the version of wger you are running and compare it against the Affected row above (wger <= 2.4). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


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


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

How to fix CVE-2026-27839

Upgrade wger 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 wger
dpkg -s wger | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update wger
rpm -q wger

Complete PowerShell remediation script (Windows)


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

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27839-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 "*wger*" -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\wger-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\wger" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "wger" --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 "wger"
    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-27839 affecting wger
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27839-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 wger 2>/dev/null | grep -i ^Version || echo "wger not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q wger || echo "wger not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27839-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/wger /etc/wger.d /etc/wger.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 wger
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y wger
elif command -v yum >/dev/null; then
    yum update -y wger
elif command -v zypper >/dev/null; then
    zypper --non-interactive update wger
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s wger 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q wger
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-27839" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27839"

Disable the affected service (Linux)


sudo systemctl stop wger 2>/dev/null || true
sudo systemctl disable wger 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 wger 2>/dev/null | grep -i ^Version
rpm -q wger 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 "*wger*" | 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-26157: Arbitrary File Read in Red Hat Hardened Images — Arbitrary File Read in Red Hat Hardened Images
How to Fix CVE-2026-23780: SQL injection in An , SQL injection in An
How to Fix CVE-2026-27940: CWE-122: Heap-based Buffer Overflow in llama.cpp , CWE-122: Heap-based Buffer Overflow in llama.cpp
How to Fix CVE-2026-44292: Critical Vulnerability in protobuf.js , Critical Vulnerability in protobuf.js
How to Fix CVE-2026-4710: Critical Vulnerability in Firefox , Critical Vulnerability in Firefox

Is CVE-2026-27839 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-27839?

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-27839?

4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.

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

The vendor advisory is at https://github.com/wger-project/wger/security/advisories/GHSA-g8gc-6c4h-jg86. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27839.

References

Official vendor advisory: https://github.com/wger-project/wger/security/advisories/GHSA-g8gc-6c4h-jg86
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27839
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://github.com/wger-project/wger/commit/29876a1954fe959e4b58ef070170e81703dab60e

*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.*