Skip to content
Noroxi
NVD / CVE Program· CNA AMZN

CVE-2026-3494: MariaDB Server Audit Plugin Comment Handling Bypass

Noroxi assessment

Priority: Monitor (action score 21/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: azl3 mariadb 10.11.15-1 on Azure Linux 3.0 10.11.16-1; cbl2 mariadb 10.6.24-1 on CBL Mariner 2.0 10.6.25-1.

Low priority for now. Upgrade to azl3 mariadb 10.11.15-1 on Azure Linux 3.0 10.11.16-1; cbl2 mariadb 10.6.24-1 on CBL Mariner 2.0 10.6.25-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.3 · v4.0—Proof of concept Fix available
Published
Mar 3, 2026
Updated
Oct 20, 2026
EPSS
0.3% · 23th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · AMZN
4.3
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-3494

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for mariadb records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
mariadbmariadb
amazonaurora mysql
amazonrelational database service

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • amazon aurora mysqlup to 2.12.5 inclusive
  • amazon aurora mysql3.05.1 and later · up to 3.10.2 inclusive
  • amazon aurora mysql3.01.0 and later · before 3.04.6
  • amazon aurora mysql3.11.0
  • amazon relational database service11.8.3 and later · up to 11.8.5 inclusive
  • amazon relational database service8.0.11 and later · up to 8.0.44 inclusive
  • amazon relational database service8.4.3 and later · up to 8.4.7 inclusive
  • amazon relational database service10.11.4 and later · up to 10.11.15 inclusive
  • amazon relational database service11.4.3 and later · up to 11.4.9 inclusive
  • amazon relational database serviceup to 5.7.44-rds.20251212 inclusive
  • amazon relational database serviceup to 10.6.24 inclusive
  • mariadb mariadb11.5.0 and later · up to 11.8.5 inclusive
  • mariadb mariadb11.0.0 and later · up to 11.4.9 inclusive
  • mariadb mariadb10.7.0 and later · up to 10.11.15 inclusive
  • mariadb mariadbup to 10.6.24 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (AMZN). Independent of NVD's CPE analysis and usually ahead of it.

  • Amazon Aurora MySQL

    • before 2.12.6affected
    • before 3.04.6affected
    • before 3.10.3affected
    • before 3.11.1affected

  • Amazon RDS for MariaDB

    • before 10.6.25affected
    • before 10.11.16affected
    • before 11.4.10affected
    • before 11.8.6affected

  • Amazon RDS for MySQL

    • before 5.7.44-RDS.20260212affected
    • before 8.0.45affected
    • before 8.4.8affected

  • MariaDB Foundation MariaDB Server

    • before 10.6.25affected
    • before 10.11.16affected
    • before 11.4.10affected
    • before 11.8.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.20mariadbfrom 10.7.0 · before 10.11.16-r010.11.16-r0
Alpine:v3.21mariadbfrom 10.7.0 · before 11.4.10-r011.4.10-r0
Alpine:v3.24mariadbfrom 10.7.0 · before 11.8.6-r011.8.6-r0
Debian:12mariadbbefore 1:10.11.18-0+deb12u11:10.11.18-0+deb12u1
Debian:13mariadbbefore 1:11.8.6-0+deb13u11:11.8.6-0+deb13u1
Debian:14mariadbbefore 1:11.8.6-11:11.8.6-1
openSUSE:Leap 16.0mariadbbefore 11.8.8-160000.1.111.8.8-160000.1.1
openSUSE:Tumbleweedmariadbbefore 11.8.7-1.111.8.7-1.1
SUSE:Linux Enterprise Module for Package Hub 15 SP7mariadbbefore 11.8.8-150700.3.15.111.8.8-150700.3.15.1
SUSE:Linux Enterprise Server 16.0mariadbbefore 11.8.8-160000.1.111.8.8-160000.1.1

Same product

mariadb: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-26785MariaDB v10.5 was discovered to contain a remote code execution (RCE) vulnerability via UDF Code in a Shared Object File, followed by a…
    40Plan
  • CVE-2012-5613MySQL 5.5.19 and possibly other versions, and MariaDB 5.5.28a and possibly other versions, when configured to assign the FILE privilege to…
    40Plan
  • CVE-2026-92262MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass.
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-52971Mar 8, 2025 · MariaDB Server 10.10 through 10.11.* and 11.0 through 11.4.* crashes in JOIN::fix_all_splittings_in_plan.
    19Monitor
  • ← EarlierCVE-2025-13699Dec 23, 2025 · MariaDB mariadb-dump Utility Directory Traversal Remote Code Execution Vulnerability
    28Monitor
  • Later →CVE-2026-32710Mar 20, 2026 · Heap-based Buffer Overflow in MariaDB
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 mariadb 10.11.15-1 on Azure Linux 3.010.11.16-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 mariadb 10.6.24-1 on CBL Mariner 2.010.6.25-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:mariadb10.11.16-r0 · Alpine:v3.20Package registry (OSV)
debian:mariadb1:10.11.18-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:mariadb11.8.7-1.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:mariadb11.8.8-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-05-03

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+60 d
  3. TodayNov 11, 2026+253 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-778 · Insufficient Logging

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records