CVE-2025-62611

CVE-2025-62611 is a high-severity vulnerability with a CVSS 4.0 base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-73.

Key facts

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.

Frequently asked questions

What is CVE-2025-62611?
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.
How severe is CVE-2025-62611?
CVE-2025-62611 has a CVSS 4.0 base score of 8.2, rated high severity.
Is CVE-2025-62611 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-62611?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-62611 have an EU (EUVD) identifier?
Yes. CVE-2025-62611 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-35594.
When was CVE-2025-62611 published?
CVE-2025-62611 was published on 2025-10-22 and last updated on 2026-06-17.

References

Other CWE-73 vulnerabilities

Browse all CWE-73 vulnerabilities →