CVE-2026-75092

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-09-15. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-78326 (ENISA EUVD) · GHSA-p54p-wj4h-hhp9 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2026

Last Modified

November 5, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
Patch available. Sources: redhat, github_commit, github_pr.
GitHub pull request Patch Available

el9to10: actors: mysql

Patch available: oamg/leapp-repository v0.22.0 (PR #1343 merged 2025-02-12)

https://github.com/oamg/leapp-repository/pull/1343
GitHub commit Patch Available

commit 3e4cafffc8de (oamg/leapp-repository)

Patch available: oamg/leapp-repository v0.22.0 (contains commit 3e4cafffc8de)

https://github.com/oamg/leapp-repository/commit/3e4cafffc8de1600a66519b326a407f37b665356
Web page

GitHub - oamg/leapp-repository: Leapp repositories containing actors for the Leapp framework (https://github.com/oamg/leapp). Currently provides leapp repositories for in-place upgrades of RHEL systems. · GitHub

https://github.com/oamg/leapp-repository
Red Hat

2517499 – (CVE-2026-75092) 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

https://bugzilla.redhat.com/show_bug.cgi?id=2517499
Red HatMentions a patch (unverified)

CVE-2026-75092 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-75092

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatleapp-repository-0:0.24.0-1.el9_8.12026-09-15redhat
redhatleapp-repository-0:0.22.0-1.el9_6.22026-09-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 210 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-11-12 10:53 UTCEchelonGraph re-scored
  4. 2026-11-12 10:53 UTCVendor advisory
  5. 2026-11-12 10:52 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-11-05 00:27 UTCEchelonGraph re-scored
  14. 2026-11-05 00:27 UTCVendor advisory
  15. 2026-11-05 00:27 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  16. 2026-11-04 23:34 UTCEchelonGraph re-scored
  17. 2026-11-04 23:34 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  18. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-30 06:23 UTCEchelonGraph re-scored
  25. 2026-10-30 06:23 UTCVendor advisory
Show 75 more
  1. 2026-10-30 06:23 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  2. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  5. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-10-25 14:03 UTCEchelonGraph re-scored
  8. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-22 20:00 UTCEchelonGraph re-scored
  11. 2026-10-22 20:00 UTCVendor advisory
  12. 2026-10-22 19:59 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-18 03:13 UTCEchelonGraph re-scored
  18. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-15 09:32 UTCEchelonGraph re-scored
  22. 2026-10-15 09:32 UTCVendor advisory
  23. 2026-10-15 09:32 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-10-13 07:22 UTCEchelonGraph re-scored
  27. 2026-10-13 07:22 UTCVendor advisory
  28. 2026-10-13 07:22 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  29. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-10-12 15:39 UTCEchelonGraph re-scored
  31. 2026-10-11 20:55 UTCVendor advisory
  32. 2026-10-11 20:55 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  33. 2026-10-11 19:25 UTCEchelonGraph re-scored
  34. 2026-10-11 16:40 UTCEchelonGraph re-scored
  35. 2026-10-11 14:00 UTCEchelonGraph re-scored
  36. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-10-11 07:18 UTCEchelonGraph re-scored
  38. 2026-10-11 07:18 UTCVendor advisory
  39. 2026-10-11 07:18 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  40. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-10-10 18:11 UTCVendor advisory
  42. 2026-10-10 18:11 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  43. 2026-10-10 05:03 UTCEchelonGraph re-scored
  44. 2026-10-10 05:03 UTCVendor advisory
  45. 2026-10-10 05:03 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  46. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  47. 2026-10-09 15:57 UTCVendor advisory
  48. 2026-10-09 15:56 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  49. 2026-10-08 22:42 UTCEchelonGraph re-scored
  50. 2026-10-08 22:42 UTCVendor advisory
  51. 2026-10-08 22:42 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  52. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-10-08 08:05 UTCEchelonGraph re-scored
  54. 2026-10-08 08:05 UTCVendor advisory
  55. 2026-10-08 08:05 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  56. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-10-07 18:59 UTCVendor advisory
  58. 2026-10-07 18:59 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  59. 2026-10-07 05:41 UTCVendor advisory
  60. 2026-10-07 05:41 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  61. 2026-10-06 16:34 UTCEchelonGraph re-scored
  62. 2026-10-06 16:34 UTCVendor advisory
  63. 2026-10-06 16:34 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  64. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  65. 2026-10-06 03:26 UTCEchelonGraph re-scored
  66. 2026-10-06 03:26 UTCVendor advisory
  67. 2026-10-06 03:26 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  68. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  69. 2026-10-05 14:16 UTCVendor advisory
  70. 2026-10-05 14:16 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  71. 2026-10-05 01:09 UTCEchelonGraph re-scored
  72. 2026-10-05 01:09 UTCVendor advisory
  73. 2026-10-05 01:09 UTCGHSA enrichmentGHSA-p54p-wj4h-hhp9 · GitHub severity HIGH · GitHub CVSS 7.3
  74. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  75. 2026-10-04 11:41 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-75092?
CVE-2026-75092 is a high-severity vulnerability; its CVE record was published on September 15, 2026. 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…
When was CVE-2026-75092 made public?
CVE-2026-75092 was made public on September 15, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on September 15, 2026. EchelonGraph's copy of the record carries a last-modified date of November 5, 2026; the record at its source may have been updated since.
Is CVE-2026-75092 actively exploited?
CVE-2026-75092 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75092?
CVE-2026-75092 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-75092?
A fix for CVE-2026-75092 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-75092 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-75092

Explore →

Is Your Infrastructure Affected by CVE-2026-75092?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.