⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.4

How to Fix CVE-2026-28279: Os command injection in osctrl

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

CVE-2026-28279 is a OS command injection in jmpsec osctrl. The fix is to apply the vendor patch noted below.

⚡ At a glance
Severity7.4 (High)
Actively exploited?No public listing in CISA KEV
Affectedosctrl < 0.5.0
Fixed inSee vendor advisory
Type (CWE)CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

What is CVE-2026-28279?

osctrl is an osquery management solution. Prior to version 0.5.0, an OS command injection vulnerability exists in the osctrl-admin environment configuration. An authenticated administrator can inject arbitrary shell commands via the hostname parameter when creating or editing environments. These commands are embedded into enrollment one-liner scripts generated using Go's text/template package (which does not perform shell escaping) and execute on every endpoint that enrolls using the compromised environment. An attacker with administrator access can achieve remote code execution on every endpoint that enrolls using the compromised environment. Commands execute as root/SYSTEM (the privilege level used for osquery enrollment) before osquery is installed, leaving no agent-level audit trail. This enables backdoor installation, credential exfiltration, and full endpoint compromise. This is fixed in osctrl v0.5.0. As a workaround, restrict osctrl administrator access to trusted personnel, review existing environment configurations for suspicious hostnames, and/or monitor enrollment scripts for unexpected commands. 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/jmpsec/osctrl/security/advisories/GHSA-rchw-322g-f7rm.

Am I affected?

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


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

How to fix CVE-2026-28279

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

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update osctrl
rpm -q osctrl

Node.js / npm


# Update the affected package in your project
npm install osctrl@latest
npm ls osctrl
npm audit fix

Complete PowerShell remediation script (Windows)


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

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

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

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

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

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

Disable the affected service (Linux)


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

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

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

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

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

The vendor advisory is at https://github.com/jmpsec/osctrl/security/advisories/GHSA-rchw-322g-f7rm. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-28279.

References

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