Denial of service via non-terminating SYLT frame parsing loop in tinytag

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-32889: 0.43% estimated exploitation activity in the next 30 days; percentile 36.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary tinytag 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. Details In tag 2.2.0 (6f1d3060f393743c2ec34d07c0855cceed827244), the reachable call path is: - TinyTag.get in tinytag/tinytag.py#L144-L154 - load in tinytag/tinytag.py#L259-L266 - parsetag and parseid3v2 in tinytag/tinytag.py#L1059-L1092 - parseframe for SYLT / SLT in tinytag/tinytag.py#L1316-L1318 - parsesyncedlyrics and findstringendpos in tinytag/tinytag.py#L1219-L1248 and tinytag/tinytag.py#L1340-L1352 The root cause is that parsesyncedlyrics assumes findstringendpos always returns a position greater than the current offset. That assumption is false when no string terminator is present in the…

Published by the source

19 Mar 2026, 17:25 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:37 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f4rq-2259-hv29

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f4rq-2259-hv29

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32889

Advisory: Denial of service via non-terminating SYLT frame parsing loop in tinytag
IDs: CVE-2026-32889, GHSA-f4rq-2259-hv29
Record: https://patchnext.com/advisories/cve-2026-32889 (revision 2, source checked 26 Oct 2026, 13:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tinytag 2.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI tinytag: affected <= 2.2.0; fixed in 2.2.1

## Suggested inspection (read-only)
- `python -m pip show tinytag`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tinytag.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f4rq-2259-hv29 (OSV record GHSA-f4rq-2259-hv29 lists affected ranges: PyPI tinytag >=0 <2.2.1 (fixed))
- Verified: https://github.com/advisories/GHSA-f4rq-2259-hv29 (GitHub-reviewed advisory GHSA-f4rq-2259-hv29 lists affected ranges: PyPI tinytag >=0 <=2.2.0)

Commands are suggestions: review each one before running it.