{"answers":{"affected":"3 open source packages ship an affected version, including aiomysql.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62611 exists.","fix":"Upgrade aiomysql to 0.3.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-62611 and fix it if it is affected.\n\nWhat it is: 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62611 exists.\n\nAffected packages and fixed versions:\n- aiomysql (PyPI): affected all versions; fixed in 0.3.0\n- aiomysql (PyPI): affected all versions; fixed in 0.3.0\n- aiomysql (PyPI): affected all versions; fixed in 0.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62611/ (Markdown: https://insights.sbomify.com/CVE-2025-62611/index.md)","id":"CVE-2025-62611","markdown":"https://insights.sbomify.com/CVE-2025-62611/index.md","name":"CVE-2025-62611","record":{"aliases":["CLEANSTART-2026-MF63070","DEBIAN-CVE-2025-62611","GHSA-r397-ff8c-wv2g","MINI-q8gv-59c7-x444","OESA-2025-2616","OESA-2025-2617","OESA-2025-2618","OESA-2025-2619","OESA-2025-2675","PYSEC-2026-1110","ROOT-APP-PYPI-CVE-2025-62611","UBUNTU-CVE-2025-62611"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python MySQL library","requires_auth":"none","summary":"A malicious MySQL server can force the aiomysql client to send arbitrary local files, allowing attackers to read sensitive data from the client system.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"aiomysql allows arbitrary access to client files through vulnerability of a malicious MySQL server","id":"CVE-2025-62611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"FastGPT File Reading Node SSRF Vulnerability","id":"CVE-2025-62612"},"packages":[{"ecosystem":"PyPI","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"aiomysql","purl":null,"source":"GHSA-r397-ff8c-wv2g"},{"ecosystem":"PyPI","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"aiomysql","purl":"pkg:pypi/aiomysql","source":"GHSA-r397-ff8c-wv2g"},{"ecosystem":"PyPI","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"aiomysql","purl":"pkg:pypi/aiomysql","source":"PYSEC-2026-1110"}],"prev":{"headline":"Hono Improperly Authorizes JWT Audience Validation","id":"CVE-2025-62610"},"products":["aiomysql"],"published":"2025-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-22","vendors":["aio-libs"]},"summary":"A malicious MySQL server can force the aiomysql client to send arbitrary local files, allowing attackers to read sensitive data from the client system.","url":"https://insights.sbomify.com/CVE-2025-62611/"}