● Medium · CVSS 6.9

How to Fix CVE-2026-27461: Sql injection in pimcore

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

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

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

The vendor advisory is at [https://github.com/pimcore/pimcore/security/advisories/GHSA-vxg3-v4p6-f3fp](https://github.com/pimcore/pimcore/security/advisories/GHSA-vxg3-v4p6-f3fp). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27461.

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

CVE-2026-27461 is a SQL injection in pimcore pimcore. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	6.9 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	pimcore <= 11.5.14.1; pimcore >= 12.0.0, < 12.3.3
Fixed in	See vendor advisory
Type (CWE)	CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

What is CVE-2026-27461?

Pimcore is an Open Source Data & Experience Management Platform. In versions up to and including 11.5.14.1 and 12.3.2, the filter query parameter in the dependency listing endpoints is JSON-decoded and the value field is concatenated directly into RLIKE clauses without sanitization or parameterized queries. Exploiting this issue requires admin authentication. An attacker with admin panel access can extract the full database including password hashes of other admin users. Version 12.3.3 contains a patch. The CVSS base score is 6.9 (Medium). The official advisory is at https://github.com/pimcore/pimcore/security/advisories/GHSA-vxg3-v4p6-f3fp.

Am I affected?

Check the version of pimcore you are running and compare it against the Affected row above (pimcore <= 11.5.14.1; pimcore >= 12.0.0, < 12.3.3). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


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


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

How to fix CVE-2026-27461

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

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update pimcore
rpm -q pimcore

Complete PowerShell remediation script (Windows)


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

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

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

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

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

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

Disable the affected service (Linux)


sudo systemctl stop pimcore 2>/dev/null || true
sudo systemctl disable pimcore 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 pimcore 2>/dev/null | grep -i ^Version
rpm -q pimcore 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 "*pimcore*" | 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-2766: Use-after-free in Firefox — Use-after-free in Firefox
How to Fix CVE-2026-39308: PraisonAI (Bundle Sibling) — PraisonAI (Bundle Sibling)
How to Fix CVE-2026-30777: Authentication bypass using an alternate path or channel in EC-CUBE 4.1 series , Authentication bypass using an alternate path or channel in EC-CUBE 4.1 series
How to Fix CVE-2026-2926: Stack buffer overflow in DWR-M960 , Stack buffer overflow in DWR-M960
How to Fix CVE-2026-33515: Path Traversal in squid , Path Traversal in squid

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

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

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

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

The vendor advisory is at https://github.com/pimcore/pimcore/security/advisories/GHSA-vxg3-v4p6-f3fp. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27461.

References

Official vendor advisory: https://github.com/pimcore/pimcore/security/advisories/GHSA-vxg3-v4p6-f3fp
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27461
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://github.com/pimcore/pimcore/pull/18991
Additional reference: https://github.com/pimcore/pimcore/commit/1c3925fbec4895abeb21e5c244a83679c4e4a6f4
Additional reference: https://github.com/pimcore/pimcore/releases/tag/v12.3.3

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