dbcve.org
MariaDBDatabase / datastore

CVE-2026-49261

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 10.6.27 / 10.11.18 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MariaDB server is a community developed fork of MySQL server. Versions 10.6.1 through 10.6.26, 10.11.1 through 10.11.17, 11.4.1 through 11.4.11, 11.8.1 through 11.8.7, and 12.3.1 with `wsrep_notify_cmd` enabled would execute shell commands embedded in the name of the joiner node. This is fixed in 10.6.27, 10.11.18, 11.4.12, 11.8.8, and 12.3.2. As a workaround, anyone who cannot upgrade now should disable `wsrep_notify_cmd`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a command injection vulnerability in MariaDB's Galera cluster wsrep notification mechanism. When `wsrep_notify_cmd` is enabled, the server processes and executes shell commands embedded in the joiner node name without sanitization, allowing unauthenticated remote code execution.

MitigationUpgrade to the fixed versions (10.6.27, 10.11.18, 11.4.12, 11.8.8, or 12.3.2). As an immediate workaround, disable `wsrep_notify_cmd` in the configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MariaDBDatabase / datastore
Affected:>= 10.6.1, < 10.6.27>= 10.11.1, < 10.11.18>= 11.4.1, < 11.4.12>= 11.8.1, < 11.8.8= 12.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check MariaDB server version
    Run `mysql --version` or query `SELECT VERSION();` from a MariaDB client
    Affected if The installed version falls within the affected ranges: 10.6.1 to 10.6.26, 10.11.1 to 10.11.17, 11.4.1 to 11.4.11, 11.8.1 to 11.8.7, or exactly 12.3.1
  2. Verify if wsrep_notify_cmd is configured
    Check the MariaDB configuration file (my.cnf or my.ini) for the wsrep_notify_cmd directive, or run query: `SHOW VARIABLES LIKE 'wsrep_notify_cmd';`
    Affected if A non-empty value is returned, meaning the notification command is enabled
  3. Confirm Galera cluster support is active
    Run query: `SHOW STATUS LIKE 'wsrep_cluster_status';` or check for wsrep-related variables with `SHOW VARIABLES LIKE 'wsrep%';`
    Affected if Galera-related variables exist and the cluster status returns a value, indicating Galera cluster support is in use
  4. Check for wsrep_provider settings
    Run query: `SHOW VARIABLES LIKE 'wsrep_provider';`
    Affected if A wsrep_provider is loaded, confirming the Galera cluster plugin is active

The environment is affected if MariaDB version is within the vulnerable ranges AND wsrep_notify_cmd is configured AND Galera cluster support is enabled, allowing unauthenticated command injection via joiner node names.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.6.27 / 10.11.18 / 11.4.12 or later
Fixed in 10.6.2710.11.1811.4.12
Interim mitigation

Upgrade to the fixed versions (10.6.27, 10.11.18, 11.4.12, 11.8.8, or 12.3.2). As an immediate workaround, disable `wsrep_notify_cmd` in the configuration.

Recommended fix High confidence

Upgrade to 10.6.27, 10.11.18, 11.4.12, 11.8.8, or 12.3.2 depending on your current version branch

  1. 1. Identify the current MariaDB version by running: SELECT VERSION();
  2. 2. Determine which version branch you are currently on (10.6.x, 10.11.x, 11.4.x, 11.8.x, or 12.3.x)
  3. 3. For immediate mitigation before upgrading, disable wsrep_notify_cmd in your MariaDB configuration (my.cnf or my.ini) by removing or commenting out the wsrep_notify_cmd setting, then restart MariaDB
  4. 4. Plan the upgrade to the fixed version for your branch: 10.6.27, 10.11.18, 11.4.12, 11.8.8, or 12.3.2
  5. 5. Before upgrading, back up all databases using mysqldump or mariadb-dump
  6. 6. Review MariaDB upgrade documentation for your specific version transition
  7. 7. Perform the upgrade using your system's package manager or by compiling from source
  8. 8. After upgrade, verify wsrep_notify_cmd is either disabled or that the configuration does not allow untrusted node names
Caveat Major version upgrades may introduce compatibility changes with applications and configuration files; review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MariaDB Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing12.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,020
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49261 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data