CVE-2025-62611 aiomysql allows arbitrary access to client files through vulnerability of a malicious MySQL server
A malicious MySQL server can force the aiomysql client to send arbitrary local files, allowing attackers to read sensitive data from the client system.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-62611?
CVE-2025-62611 is a high-severity path traversal vulnerability in aio-libs aiomysql, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
aiomysql is a library for accessing a MySQL database from the asyncio. Prior to version 0.3.0, the client-side settings are not checked before sending local files to MySQL server, which allows obtaining arbitrary files from the client using a rogue server. It is possible to create a rogue MySQL server that emulates authorization, ignores client flags and requests arbitrary files from the client by sending a LOAD_LOCAL instruction packet. This issue has been patched in version 0.3.0.
Weakness: CWE-73
Which versions are affected by CVE-2025-62611?
3 open source packages ship an affected version, including aiomysql.
| Package | Affected | Fixed in |
|---|---|---|
aiomysql PyPI | All versions | 0.3.0 |
aiomysql PyPI | All versions | 0.3.0 |
aiomysql PyPI | All versions | 0.3.0 |
How do I fix CVE-2025-62611?
Upgrade aiomysql to 0.3.0 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2025-62611 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62611 exists.
Sources
Also known as CLEANSTART-2026-MF63070, DEBIAN-CVE-2025-62611, GHSA-r397-ff8c-wv2g, MINI-q8gv-59c7-x444, OESA-2025-2616, OESA-2025-2617 and 6 more.