highVulnerability

GHSA-qq2p-4282-cfc5

### 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 https://mariadb.com/resources/blog/isolation-level-violation-testing-and-debugging-in-mariadb/

Properties

ghsa_id
GHSA-qq2p-4282-cfc5
summary
eduMFA: Incorrect InnoDB snapshot isolation possibly allows token reusage
severity
high
cve_id
GHSA-qq2p-4282-cfc5
is_ghsa_only
true
ghsa_published
2026-05-18T15:36:18Z
source_url
https://github.com/advisories/GHSA-qq2p-4282-cfc5
ghsa_updated
2026-05-18T15:36:19Z

Related Entities (4)

REPORTED_BY (1)

[Source]GitHub Advisory Database

VULNERABLE_TO (1)

[Software]pip/edumfa

AFFECTS (1)

[Software]pip/edumfa

HAS_WEAKNESS (1)

[Weakness]Improper Authorization

Explore deeper with Ninja Signal's threat intelligence graph

GHSA-qq2p-4282-cfc5 — Ninja Signal Threat Intelligence | Ninja Signal