CVE-2025-62611VulnerabilityPublished 22 Oct 2025

CVE-2025-62611: aio-libs aiomysql · External Control of File Name or Path

Affects aio-libs aiomysqlSource CVE Database V5

Not known to be exploited · CVSS 8.2 High : upgrade to 0.3.0 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.3.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade aio-libs aiomysql to 0.3.0.

Affected software

Product	Affected	Fixed in
PyPIaiomysql`pkg:pypi/aiomysql`Other threats	Affected <0.3.0	Fixed in 0.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade all instances of aiomysql to version 0.3.0 or later, where the vulnerability is patched. 2. Implement strict network segmentation and firewall rules to restrict client connections only to trusted MySQL servers, preventing rogue server interactions. 3. Employ application-layer validation and monitoring to detect unusual LOAD_LOCAL commands or unexpected file transfers. 4. Review and minimize the use of LOAD_LOCAL capability in MySQL client configurations where possible. 5. Conduct security audits of asynchronous Python applications to identify usage of vulnerable aiomysql versions. 6. Educate developers and DevOps teams about the risks of connecting to untrusted database servers and enforce secure coding practices. 7. Monitor threat intelligence feeds for any emerging exploits targeting this vulnerability to respond promptly.

Description

CVE-2025-62611 is a high-severity vulnerability in the aio-libs aiomysql library versions prior to 0.3.0. The flaw allows a rogue MySQL server to exploit the client by requesting arbitrary local files via the LOAD_LOCAL instruction, bypassing client-side checks. This can lead to unauthorized disclosure of sensitive client files without requiring authentication or user interaction. The vulnerability arises from improper validation of client settings before sending local files to the server. Although no known exploits are currently reported in the wild, the issue has been patched in aiomysql version 0.3.0. European organizations using vulnerable versions of aiomysql in their asynchronous Python applications that connect to MySQL databases are at risk.

Impact

The primary impact of this vulnerability is the unauthorized disclosure of sensitive files from client systems to a rogue MySQL server. For European organizations, this could lead to exposure of confidential business data, intellectual property, or personally identifiable information (PII), potentially violating GDPR and other data protection regulations. The vulnerability could be exploited by attackers who control or impersonate MySQL servers, including in supply chain attacks or compromised internal database servers. This risk is heightened in sectors with extensive use of Python asynchronous frameworks and MySQL backends, such as finance, healthcare, and technology. The breach of confidentiality could result in reputational damage, regulatory fines, and operational disruptions. Since exploitation does not require authentication or user interaction, the attack surface is broad, especially in environments where clients connect to multiple or external MySQL servers. Availability and integrity impacts are minimal, but the confidentiality breach alone justifies urgent remediation.

CWE-73External Control of File Name or Path (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows user input to control or influence paths or file names that are used in filesystem operations.
Architecture and Design
When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt".
Architecture and Design · Operation
Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.2 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
Leverage Alternate Encoding (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
URL Encoding (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2025, 20:01 UTC

WeaknessesCWE-73

Technical details

References

Community reviews

Related threats