Skip to content

MariaDB

By MariaDB Foundation Bug bounty on Sorona mariadb.org

Accepting reports open-source
Top reward
$1,500
Top severity paid
Critical
Assets in scope
15
Public CVEs
60
Last change
No changes yet

At a glance

What to know before you start testing.

Pays from $1,500
for critical bugs.
Partial safe harbor
Some legal protection; read the terms.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Sorona lists as the payout for each severity.

Severity Reward
Critical $1,500+
High $700+
Medium $300+
Low $100 $100 / 1 month Claude Max
Safe harbor
Partial Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

15 assets you may test, 6 excluded.

Web 1

  • https://mariadb.org

Products and areas 14

  • Every storage engine shipped in the tree, including InnoDB, Aria, MyISAM, MyRocks, ColumnStore, Spider, CONNECT and FederatedX
  • information_schema, performance_schema and the system tables, and what a low-privileged account can read from them
  • LOAD DATA LOCAL INFILE and the client-side file handling a server can request through it
  • Replication end to end: the binary log formats, GTID handling, semi-synchronous replication and the Galera integration
  • The authentication plugins the tree ships, covering mysql_native_password, ed25519, unix_socket, PAM, GSSAPI and the pluggable authentication interface itself
  • The client and server wire protocol, the handshake in front of it and the capability negotiation a client can drive
  • The client tools the project ships, including mysqldump, mariabackup and the command line client
  • The engines and functions that make outbound connections or read the filesystem, in particular CONNECT, FederatedX, Spider and LOAD DATA
  • The Foundation accepts reports through its HackerOne disclosure programme or at [email protected], and states it runs no bug bounty and pays nothing. The declared surface is the server the project releases, with nothing narrower carved out
  • The JSON functions, dynamic columns, and the character set and collation conversion paths
  • The privilege system in full: GRANT evaluation, roles, column and table level privileges, and the definer semantics on views, stored routines, triggers and events
  • The SQL parser and the optimiser, including every rewrite the optimiser performs on a query before it runs
  • TLS configuration, certificate verification and the encryption of both client connections and replication links
  • User-defined functions, the plugin loading path and anything that loads a shared object into the server process
Out of scope (6)
  • A privilege an administrator deliberately granted, such as FILE or SUPER to an account that should not have had it
  • Connectors and client libraries maintained outside the server repository
  • Distribution packaging, init scripts and distro-specific patches rather than upstream MariaDB
  • MariaDB plc's enterprise builds and SkySQL, which are the commercial company's products with their own reporting path
  • MySQL, Percona Server and other forks, each with its own vendor and process
  • Upstream libraries the server links, unless MariaDB's own use of them is what makes the defect reachable

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.

While testing

  • Submit through sorona.xyz.
  • Report through the MariaDB Foundation vulnerability disclosure programme on HackerOne, or by email to the address on the policy page
  • Give the exact statement, the account's grants and the server version.
  • Name the storage engine and the authentication plugin.
  • State whether the finding needs FILE, SUPER or a similarly powerful privilege.
  • Hold detail until the fixed versions are out.

Not accepted

  • A privilege an administrator deliberately granted, such as FILE or SUPER to an account that should not have had it
  • Distribution packaging, init scripts and distro-specific patches rather than upstream MariaDB
  • Connectors and client libraries maintained outside the server repository

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 23 minutes ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2026-97380 High 8.8 16 Oct 2026
CVE-2026-92262 Critical 9.9 16 Oct 2026
CVE-2026-85985 Medium 5.4 16 Oct 2026
CVE-2026-86047 High 7.7 16 Oct 2026
CVE-2026-85745 Medium 4.3 16 Oct 2026
CVE-2026-85746 Critical 9.9 16 Oct 2026
CVE-2026-85748 Critical 9.9 16 Oct 2026
CVE-2026-107821 High 8.0 9 Oct 2026
CVE-2026-107822 Medium 6.4 9 Oct 2026
CVE-2026-107823 High 7.2 9 Oct 2026
CVE-2026-107816 Medium 6.4 9 Oct 2026
CVE-2026-107817 Medium 4.4 9 Oct 2026
CVE-2026-107818 High 8.4 9 Oct 2026
CVE-2026-107815 High 8.5 9 Oct 2026
CVE-2026-107814 High 8.4 9 Oct 2026
CVE-2026-48163 High 8.0 12 Jun 2026
CVE-2026-48165 High 8.0 12 Jun 2026
CVE-2026-44168 High 8.0 12 Jun 2026
CVE-2026-44169 Medium 4.3 12 Jun 2026
CVE-2026-44170 Medium 6.3 12 Jun 2026
CVE-2026-44171 Medium 6.3 12 Jun 2026
CVE-2026-44172 Medium 6.9 12 Jun 2026
CVE-2026-44173 Medium 5.0 12 Jun 2026
CVE-2026-49261 Critical 10.0 11 Jun 2026
CVE-2026-35549 Medium 6.5 3 Apr 2026
CVE-2026-32710 High 8.5 20 Mar 2026
CVE-2026-3494 Medium 5.3 3 Mar 2026
CVE-2025-56404 High 7.5 10 Sep 2025
CVE-2023-26785 Critical 9.8 17 Oct 2024
CVE-2023-39593 Medium 5.6 17 Oct 2024
CVE-2024-27766 Medium 5.7 17 Oct 2024
CVE-2023-22084 Medium 4.9 17 Oct 2023
CVE-2023-5157 High 7.5 27 Sep 2023
CVE-2023-40354 Medium 6.5 14 Aug 2023
CVE-2022-47015 Medium 6.5 20 Jan 2023
CVE-2022-21595 Medium 4.4 18 Oct 2022
CVE-2022-38791 Medium 5.5 27 Aug 2022
CVE-2022-32091 High 7.5 1 Jul 2022
CVE-2022-32081 High 7.5 1 Jul 2022
CVE-2022-32082 High 7.5 1 Jul 2022
CVE-2022-32083 High 7.5 1 Jul 2022
CVE-2022-32084 High 7.5 1 Jul 2022
CVE-2022-32085 High 7.5 1 Jul 2022
CVE-2022-32086 High 7.5 1 Jul 2022
CVE-2022-32087 High 7.5 1 Jul 2022
CVE-2022-32088 High 7.5 1 Jul 2022
CVE-2022-32089 High 7.5 1 Jul 2022
CVE-2022-31621 Medium 5.5 25 May 2022
CVE-2022-31622 Medium 5.5 25 May 2022
CVE-2022-31623 Medium 5.5 25 May 2022
CVE-2022-31624 Medium 5.5 25 May 2022
CVE-2022-21451 Medium 4.4 19 Apr 2022
CVE-2022-21427 Medium 4.9 19 Apr 2022
CVE-2022-27448 High 7.5 14 Apr 2022
CVE-2022-27449 High 7.5 14 Apr 2022
CVE-2022-27451 High 7.5 14 Apr 2022
CVE-2022-27452 High 7.5 14 Apr 2022
CVE-2022-27455 High 7.5 14 Apr 2022
CVE-2022-27456 High 7.5 14 Apr 2022
CVE-2022-27457 High 7.5 14 Apr 2022

Original policy

Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability Latest advisories Loading the feed Overview MariaDB ships as the default mysql package in Debian, Red Hat and most other distributions, which puts it under a very large share of self-hosted web applications and managed cloud databases. It holds the application's users and its business records, so a defect in privilege checking or in the authentication plugins is a full read of that. The MariaDB Foundation runs a HackerOne vulnerability disclosure programme that offers thanks and reputation points and states it gives no compensation, and the Vector Bounty is a feature contest rather than a security reward. sorona.xyz pays you directly on qualified, reproduced findings. In scope The Foundation accepts reports through its HackerOne disclosure programme or at [email protected] , and states it runs no bug bounty and pays nothing. The declared surface is the server the project releases, with nothing narrower carved out The SQL parser and the optimiser, including every rewrite the optimiser performs on a query before it runs The privilege system in full: GRANT evaluation, roles, column and table level privileges, and the definer semantics on views, stored routines, triggers and events The authentication plugins the tree ships, covering mysql_native_password, ed25519, unix_socket, PAM, GSSAPI and the pluggable authentication interface itself The client and server wire protocol, the handshake in front of it and the capability negotiation a client can drive Every storage engine shipped in the tree, including InnoDB, Aria, MyISAM, MyRocks, ColumnStore, Spider, CONNECT and FederatedX Replication end to end: the binary log formats, GTID handling, semi-synchronous replication and the Galera integration The engines and functions that make outbound connections or read the filesystem, in particular CONNECT, FederatedX, Spider and LOAD DATA LOAD DATA LOCAL INFILE and the client-side file handling a server can request through it User-defined functions, the plugin loading path and anything that loads a shared object into the server process TLS configuration, certificate verification and the encryption of both client connections and replication links The JSON functions, dynamic columns, and the character set and collation conversion paths information_schema , performance_schema and the system tables, and what a low-privileged account can read from them The client tools the project ships, including mysqldump, mariabackup and the command line client Out of scope MariaDB plc's enterprise builds and SkySQL, which are the commercial company's products with their own reporting path MySQL, Percona Server and other forks, each with its own vendor and process Distribution packaging, init scripts and distro-specific patches rather than upstream MariaDB A privilege an administrator deliberately granted, such as FILE or SUPER to an account that should not have had it Connectors and client libraries maintained outside the server repository Upstream libraries the server links, unless MariaDB's own use of them is what makes the defect reachable Most-valued findings Privilege escalation through the grant system, above all definer-context execution in views, stored routines, triggers and events, where code runs as an account the caller does not hold Authentication bypass in any plugin or in the handshake, since the plugin is what decides identity before any privilege check happens Memory corruption reachable from the wire protocol before authentication completes, which needs nothing but network access to the port Parser and optimiser defects that crash or corrupt the server from a query an ordinary user is permitted to run LOAD DATA LOCAL INFILE handling, where a server the client did not expect requests a file from the client's own filesystem Outbound connection engines, CONNECT, FederatedX and Spider, reaching internal network services from a table definition a user can create Storage engine defects in InnoDB page, undo or redo log handling reachable from a restore, a replica feed or a crash recovery Replication paths where a replica accepts events from a source it should not trust, or where binary log content executes with more privilege than the originating statement had Information disclosure through information_schema , performance_schema or error messages that reveal data across an account boundary The research names CVE-2021-26086 as having gone through this programme without describing it. Treat the published record as thin rather than as evidence the surface is clean Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Report through the MariaDB Foundation vulnerability disclosure programme on HackerOne, or by email to [email protected] The Foundation states that it does not have a bug bounty program and gives no compensation. HackerOne thanks, reputation points and occasional swag are the whole reward The Vector Bounty is a feature-development contest for LLM framework integrations. It is not a security reward and filing a vulnerability against it is a category error Give the exact statement, the account's grants and the server version. Privilege findings here almost always turn on the grants held rather than on an unusual build Name the storage engine and the authentication plugin. The tree ships several of each and a defect in one rarely exists in the others State whether the finding needs FILE, SUPER or a similarly powerful privilege. A grant that already permits reading the filesystem is a deliberate administrative decision Disclosure Coordinated with the MariaDB Foundation security team through HackerOne or the security address, with a CVE issued and the fix shipped in the maintenance releases across supported series. MariaDB coordinates with distributions that carry it as the default database, so the practical embargo runs to those releases rather than to a fixed day count. Hold detail until the fixed versions are out. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability