How to Fix CVE-2026-27981: Improper restriction of excessive authentication attempts in homebox

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

CVE-2026-27981 is a improper restriction of excessive authentication attempts in sysadminsmedia homebox. The fix is to apply the vendor patch noted below.

What is CVE-2026-27981?

HomeBox is a home inventory and organization system. Prior to 0.24.0, the authentication rate limiter (authRateLimiter) tracks failed attempts per client IP. It determines the client IP by reading, 1. X-Real-IP header, 2. First entry of X-Forwarded-For header, and 3. r.RemoteAddr (TCP connection address). These headers were read unconditionally. An attacker connecting directly to Homebox could forge any value in X-Real-IP, effectively getting a fresh rate limit identity per request. There is a TrustProxy option in the configuration (Options.TrustProxy, default false), but this option was never read by any middleware or rate limiter code. Additionally, chi's middleware.RealIP was applied unconditionally in main.go, overwriting r.RemoteAddr with the forged header value before it reaches any handler. This vulnerability is fixed in 0.24.0. The CVSS base score is 7.4 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://github.com/sysadminsmedia/homebox/security/advisories/GHSA-j86g-v96v-jpp3.

Am I affected?

Check the version of homebox you are running and compare it against the Affected row above (homebox < 0.24.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 homebox 2>/dev/null | grep -i ^Version
rpm -q homebox 2>/dev/null
command -v homebox >/dev/null && homebox --version 2>/dev/null

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

How to fix CVE-2026-27981

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

RHEL / CentOS / Rocky / AlmaLinux

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

SUSE / openSUSE

sudo zypper refresh
sudo zypper update homebox
rpm -q homebox

Complete PowerShell remediation script (Windows)

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

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

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

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

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

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

Disable the affected service (Linux)

sudo systemctl stop homebox 2>/dev/null || true
sudo systemctl disable homebox 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 homebox 2>/dev/null | grep -i ^Version
rpm -q homebox 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 "*homebox*" | 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

Related fixes

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

• How to Fix CVE-2026-23761: Critical Vulnerability in Voicemeeter (Standard) — Critical Vulnerability in Voicemeeter (Standard)
• How to Fix CVE-2026-6034: Cross-site scripting in Vehicle Showroom Management System — Cross-site scripting in Vehicle Showroom Management System
• How to Fix CVE-2026-33601: Recursor (Bundle Sibling) , Recursor (Bundle Sibling)
• How to Fix CVE-2026-1519: Critical Vulnerability in BIND 9 , Critical Vulnerability in BIND 9
• How to Fix CVE-2026-24560: Critical Vulnerability in Cloudinary , Critical Vulnerability in Cloudinary

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

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

7.4 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.

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

The vendor advisory is at https://github.com/sysadminsmedia/homebox/security/advisories/GHSA-j86g-v96v-jpp3. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27981.

References

• Official vendor advisory: https://github.com/sysadminsmedia/homebox/security/advisories/GHSA-j86g-v96v-jpp3
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27981
• 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.*