Approved changes feed: RSS · Atom
cpe:2.3:a:tinytag:tinytag:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Tinytag (596335fd-c8f0-5ae1-9adc-a5e2629bcdf4) |
|---|---|
| Product | Tinytag (5e137567-d03a-52fd-a0f6-aa15a1a0a306) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/tinytag/tinytag |
purl2cpe | 2026-07-28 16:41:09.423102 |
pkg:pypi/tinytag |
purl2cpe | 2026-06-01 10:16:07.002445 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-104266 |
vulnerable | 2026-11-03 10:16:19.300696 |
tinytag: Infinite loop when parsing certain M4A files containing invalid atoms
MEDIUM (6.5)
tinytag is a Python library for reading audio file metadata. From 2.0.0 until 2.3.0, an M4A file containing a sub-atom with a size of zero inside a ---- atom can cause the metadata parser to stop advancing through the input. The custom-field atom traversal repeatedly processes the malformed location, causing an infinite loop and denying service to a program that reads the crafted file. This issue is fixed in version 2.3.0.
Published: 2026-10-15T17:13:26.636Z
Updated: 2026-10-21T01:00:05.989Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-32889 |
vulnerable | 2026-06-08 07:57:18.302138 |
tinytag: Denial of Service via non-terminating SYLT frame parsing loop
MEDIUM (6.5)
tinytag is a Python library for reading audio file metadata. Version 2.2.0 allows an attacker who can supply MP3 files for parsing to trigger a non-terminating loop while the library parses an ID3v2 SYLT (synchronized lyrics) frame. In server-side deployments that automatically parse attacker-supplied files, a single 498-byte MP3 can cause the parsing operation to stop making progress and remain busy until the worker or process is terminated. The root cause is that _parse_synced_lyrics assumes _find_string_end_pos always returns a position greater than the current offset. That assumption is false when no string terminator is present in the remaining frame content. This issue has been fixed in version 2.2.1.
Published: 2026-03-20T02:23:25.079Z
Updated: 2026-03-21T02:59:12.338Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.