PT-2026-44443
Published
2026-05-18
·
Updated
2026-05-18
Description by
CVSS 4.0
7.1
HighMetricsAV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L
Impact
For deployments using MySQL or MariaDB < 11.6.2 (or newer with innodb snapshot isolation=off) reusage of token values might be possible due to faulty transaction isolation inside the database. Exploiting this requires racing this transaction.
Affected are all tokentypes whose values are only supposed to be used once, for example TOTP, HOTP and likely also WebAuthN.
Affected Combinations:
- MySQL (any version)
- MariaDB with innodb snapshot isolation=OFF
- innodb snapshot isolation was introduced in: MariaDB 10.6.18, MariaDB 10.11.8, MariaDB 11.0.6, MariaDB 11.1.5, MariaDB 11.2.4, MariaDB 11.4.2 with default OFF, can be turned ON as a workaround
- for MariaDB >= 11.6.2 the default is ON, which is not affected
- Same rules applies for Galera with underlying MariaDB
Patches
Fixed in version 2.9.1 by locking rows prior to write with SELECT FOR UPDATE.
Workarounds
Set innodb snapshot isolation to ON (default in MariaDB >= 11.6.2, e.g packaged in Debian 13).
Resources
Found an issue in the description? Have something to add? Feel free to write us 👾