CVE-2025-30699

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Stored Procedure). Supported versions that are affected are 8.0.0-8.0.41, 8.4.0-8.4.4 and 9.0.0-9.2.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

Published: 2025-04-15 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-30699 is rated Low Risk (23.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-30699

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-26 0.32% 0.04% -0.28%
2 2026-02-09 0.08% 0.32% +0.24%
3 2025-12-30 — 0.08% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-30699

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.9 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.2 3.6 [email protected]

Weakness enumeration for CVE-2025-30699

OS Trackers for CVE-2025-30699

vendor priority summary link
debian not yet assigned CVE-2025-30699 not yet assigned priority: Debian including 1 source packages (mysql-8.0), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-30699
redhat medium — https://access.redhat.com/security/cve/CVE-2025-30699
ubuntu medium CVE-2025-30699 medium priority: Ubuntu including 11 source packages (mariadb, mariadb-10.0, …), 84 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 54, not-affected 11, released 8, needs-triage 6, ignored 5. https://ubuntu.com/security/CVE-2025-30699

Affected software / configurations for CVE-2025-30699

Vendor Product Version Raw CPE
oracle mysql_server >= 8.0.0, <= 8.0.41 cpe:2.3:a:oracle:mysql_server:*:*:*:*:*:*:*:*
oracle mysql_server >= 8.4.0, <= 8.4.4 cpe:2.3:a:oracle:mysql_server:*:*:*:*:*:*:*:*
oracle mysql_server >= 9.0.0, <= 9.2.0 cpe:2.3:a:oracle:mysql_server:*:*:*:*:*:*:*:*

References for CVE-2025-30699

cvelogic Threat Intelligence