CVE-2026-104266: tinytag: Infinite loop when parsing certain M4A files containing invalid atoms
Impact An M4A file containing a sub-atom with a size of zero in the ---- atom makes the parser enter an infinite loop, resulting in a denial-of-service for programs reading such files with tinytag. Patches The issue has been fixed in tinytag 2.3.0, by reusing the primary atom parsing code path that contains appropriate size checks. Workarounds No workarounds exist. Users must upgrade to tinytag 2.3.0.
Published Oct 15, 2026
Affected packages
tinytag
- Ecosystem
- PyPI
- Affected
- >= 2.0.0, < 2.3.0
- Fixed in
- 2.3.0
- Check
pip show tinytag
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
An M4A file containing a sub-atom with a size of zero in the ---- atom makes the parser enter an infinite loop, resulting in a denial-of-service for programs reading such files with tinytag.
Patches
The issue has been fixed in tinytag 2.3.0, by reusing the primary atom parsing code path that contains appropriate size checks.
Workarounds
No workarounds exist. Users must upgrade to tinytag 2.3.0.
Credited to seankohjs, mathiascode.
References
- https://github.com/tinytag/tinytag/security/advisories/GHSA-24cc-9352-h2pg
- https://nvd.nist.gov/vuln/detail/CVE-2026-104266
- https://github.com/tinytag/tinytag/pull/326
- https://github.com/tinytag/tinytag/commit/9ada221ba44990cb02cd9002d992186e037b515e
- https://github.com/tinytag/tinytag/releases/tag/2.3.0
- https://github.com/advisories/GHSA-24cc-9352-h2pg
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
