● Medium · CVSS 5.3

How to Fix CVE-2026-3049: Open redirect in horilla

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

5.3 (Medium). Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`.

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

The vendor advisory is at [https://vuldb.com/?id.347407](https://vuldb.com/?id.347407). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3049.

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

CVE-2026-3049 is a open redirect in horilla-opensource horilla. The fix is to upgrade to horilla 1.0.3.

⚡ At a glance


Severity	5.3 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	horilla 1.0.0; horilla 1.0.1; horilla 1.0.2
Fixed in	horilla 1.0.3
Type (CWE)	CWE-601: Open Redirect

What is CVE-2026-3049?

A vulnerability was detected in horilla-opensource horilla up to 1.0.2. This issue affects the function get of the file horilla_generics/global_search.py of the component Query Parameter Handler. The manipulation of the argument prev_url results in open redirect. The attack can be executed remotely. The exploit is now public and may be used. Upgrading to version 1.0.3 is capable of addressing this issue. The patch is identified as 730b5a44ff060916780c44a4bdbc8ced70a2cd27. The affected component should be upgraded. The CVSS base score is 5.3 (Medium). The official advisory is at https://vuldb.com/?id.347407.

Am I affected?

Check the version of horilla you are running and compare it against the Affected row above (horilla 1.0.0; horilla 1.0.1; horilla 1.0.2). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


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


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

How to fix CVE-2026-3049

Upgrade horilla to a patched build: horilla 1.0.3. 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 horilla
dpkg -s horilla | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update horilla
rpm -q horilla

Node.js / npm


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

Complete PowerShell remediation script (Windows)


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

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

    Write-Host "[3/4] Apply the upgrade to horilla 1.0.3"
    winget upgrade --name "horilla" --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 "horilla"
    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-3049 affecting horilla
# Detect -> backup -> upgrade -> verify -> log.

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

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

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

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

Disable the affected service (Linux)


sudo systemctl stop horilla 2>/dev/null || true
sudo systemctl disable horilla 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 horilla 2>/dev/null | grep -i ^Version
rpm -q horilla 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 "*horilla*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above horilla 1.0.3. 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-24622: Critical Vulnerability in Suggestion Toolkit — Critical Vulnerability in Suggestion Toolkit
How to Fix CVE-2026-5826: Simple IT Discussion Forum (Bundle Sibling) — Simple IT Discussion Forum (Bundle Sibling)
How to Fix CVE-2026-33657: Cwe-80: improper neutralization of script-related html in espocrm , Cwe-80: improper neutralization of script-related html in espocrm
How to Fix CVE-2026-45229: Critical Vulnerability in quark-auto-save , Critical Vulnerability in quark-auto-save
How to Fix CVE-2026-22707: Unrestricted File Upload in strapi , Unrestricted File Upload in strapi

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

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

5.3 (Medium). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P.

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

The vendor advisory is at https://vuldb.com/?id.347407. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3049.

References

Official vendor advisory: https://vuldb.com/?id.347407
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3049
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://vuldb.com/?ctiid.347407
Additional reference: https://vuldb.com/?submit.757296
Additional reference: https://github.com/Stolichnayer/Horilla-CRM-Open-Redirect

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