● Medium · CVSS 4.3

How to Fix CVE-2026-3494: Cwe-778 (insufficient logging) in MariaDB Server

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

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

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

The vendor advisory is at [https://aws.amazon.com/security/security-bulletins/2026-006-AWS/](https://aws.amazon.com/security/security-bulletins/2026-006-AWS/). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3494.

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

CVE-2026-3494 is a cwe-778 (insufficient logging) in MariaDB Foundation MariaDB Server. The fix is to upgrade to Aurora MySQL 2.12.6; Aurora MySQL 3.04.6; Aurora MySQL 3.10.3; Aurora MySQL 3.11.1; MariaDB Server 10.11.16; MariaDB Server 10.6.25.

⚡ At a glance


Severity	4.3 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	See vendor advisory
Fixed in	Aurora MySQL 2.12.6; Aurora MySQL 3.04.6; Aurora MySQL 3.10.3; Aurora MySQL 3.11.1; MariaDB Server 10.11.16; MariaDB Server 10.6.25
Type (CWE)	CWE-778 (Insufficient Logging)

What is CVE-2026-3494?

In MariaDB server version through 11.8.5, when server audit plugin is enabled with server_audit_events variable configured with QUERY_DCL, QUERY_DDL, or QUERY_DML filtering, if an authenticated database user invokes a SQL statement prefixed with double-hyphen (—) or hash (#) style comments, the statement is not logged. The CVSS base score is 4.3 (Medium). The official advisory is at https://aws.amazon.com/security/security-bulletins/2026-006-AWS/.

Am I affected?

Check the version of MariaDB Server you are running and compare it against the Affected row above (See vendor advisory). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


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


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

How to fix CVE-2026-3494

Upgrade MariaDB Server to a patched build: Aurora MySQL 2.12.6; Aurora MySQL 3.04.6; Aurora MySQL 3.10.3; Aurora MySQL 3.11.1; MariaDB Server 10.11.16; MariaDB Server 10.6.25. 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 mariadb-server
dpkg -s mariadb-server | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


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

SUSE / openSUSE


sudo zypper refresh
sudo zypper update mariadb-server
rpm -q mariadb-server

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-3494 affecting MariaDB Server
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

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

    Write-Host "[3/4] Apply the upgrade to Aurora MySQL 2.12.6; Aurora MySQL 3.04.6; Aurora MySQL 3.10.3; Aurora MySQL 3.11.1; MariaDB Server 10.11.16; MariaDB Server 10.6.25"
    winget upgrade --name "MariaDB Server" --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 "MariaDB Server"
    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-3494 affecting MariaDB Server
# Detect -> backup -> upgrade -> verify -> log.

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

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

echo "[3/4] Apply the upgrade (target: Aurora MySQL 2.12.6; Aurora MySQL 3.04.6; Aurora MySQL 3.10.3; Aurora MySQL 3.11.1; MariaDB Server 10.11.16; MariaDB Server 10.6.25)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y mariadb-server
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y mariadb-server
elif command -v yum >/dev/null; then
    yum update -y mariadb-server
elif command -v zypper >/dev/null; then
    zypper --non-interactive update mariadb-server
fi

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

Disable the affected service (Linux)


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

Expected: the reported version is at or above Aurora MySQL 2.12.6; Aurora MySQL 3.04.6; Aurora MySQL 3.10.3; Aurora MySQL 3.11.1; MariaDB Server 10.11.16; MariaDB Server 10.6.25. 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-1086: CWE-352 Cross-Site Request Forgery (CSRF) — CWE-352 Cross-Site Request Forgery (CSRF)
How to Fix CVE-2026-22448: Path Traversal in PitchPrint , Path Traversal in PitchPrint
How to Fix CVE-2026-25878: Authentication Bypass in FroshPlatformAdminer , Authentication Bypass in FroshPlatformAdminer
How to Fix CVE-2026-6692: Unrestricted Upload of File with Dangerous Type in Slider Revolution , Unrestricted Upload of File with Dangerous Type in Slider Revolution
How to Fix CVE-2026-29772: Command Injection in astro , Command Injection in astro

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

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

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

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

The vendor advisory is at https://aws.amazon.com/security/security-bulletins/2026-006-AWS/. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-3494.

References

Official vendor advisory: https://aws.amazon.com/security/security-bulletins/2026-006-AWS/
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3494
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://github.com/MariaDB/server/commit/635559a2ad68a5a6d1a354e8209c58323dba0261
Additional reference: https://github.com/aws/audit-plugin-for-mysql/commit/01e25a5cb1073f131eea774c06c8a056b1e4b2ff

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