CVE-2026-75092
Leapp-repository: leapp-upgrade-el9toel10: leapp-upgrade-el9toel10: scan_mysql runs mysqld --validate-config as root and can load mysql-writable plugins
What happened?
A privilege escalation flaw was found in the scan_mysql actor of leapp-upgrade-el9toel10 (provided by leapp-repository). During RHEL 9 to RHEL 10 upgrades, the actor runs: mysqld --validate-config --log-error-verbosity=2 directly as root in the Leapp actor context, bypassing the packaged MySQL systemd unit that normally starts the daemon as User=mysql.
A process compromised as the mysql OS identity can write a version-2 persisted configuration (mysqld-auto.cnf) and a malicious shared object into /var/lib/mysql (a directory owned by mysql). That persisted map can set plugin_dir to /var/lib/mysql and early_plugin_load (or related loader options such as plugin_load / plugin_load_add) so MySQL loads the attacker-controlled object during configuration validation. Plugin loading can reach dlopen() before MySQL’s runtime-user check and before plugin-symbol validation.
When an administrator subsequently runs the documented Leapp preupgrade or upgrade workflow, attacker-controlled code can execute as UID 0 with a full capability set in an unconfined SELinux domain (unconfined_t). The attack does not require write access to the default system plugin path under /usr; redirecting plugin_dir via mysql-owned persisted state is sufficient. Ordinary SQL privileges alone (including highly privileged SQL accounts) are not a sufficient startpoint — OS-level execution as the mysql service identity is required, plus later administrator invocation of Leapp.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| leapp-repositoryRed Hat | unaffected: 0:0.24.0-1.el9_8.1 to < * | See vendor advisory |
| leapp-repositoryRed Hat | unaffected: 0:0.22.0-1.el9_6.2 to < * | See vendor advisory |
| leapp-repositoryRed Hat | Default status: unaffected | See vendor advisory |
| leapp-repository-openstackRed Hat | Default status: unaffected | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-75092
- https://access.redhat.com/errata/RHSA-2026:67608
- https://access.redhat.com/errata/RHSA-2026:67609
- https://access.redhat.com/security/cve/CVE-2026-75092
- https://bugzilla.redhat.com/show_bug.cgi?id=2517499
- https://github.com/oamg/leapp-repository
- https://github.com/oamg/leapp-repository/commit/3e4cafffc8de1600a66519b326a407f37b665356
- https://github.com/oamg/leapp-repository/pull/1343