Advisory record · GHSA-r397-ff8c-wv2g

aiomysql allows arbitrary access to client files through vulnerability of a malicious MySQL server

CVSS 8.2 HighEPSS 0.0039 · 33rd percentile

Published by the GitHub Advisory Database at 22 Oct 2025, 16:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aiomysqlPyPI<0.3.00.3.0
Identifiers
GHSA-r397-ff8c-wv2g · CVE-2025-62611 · PYSEC-2026-1110
Weakness (CWE)
CWE-73
Published
22 Oct 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

aiomysql versions before 0.3.0 do not check client-side settings before sending local files to a MySQL server. An attacker running a rogue MySQL server that the client connects to can request arbitrary files from the client, which can then be read. Upgrade to aiomysql 0.3.0 or later. Avoid connecting to untrusted MySQL servers.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 4.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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0039, the 33rd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.