Vulnerability in tinytag (CVE-2026-32889)
Summary
Vulnerability in tinytag (CVE-2026-32889). Risk of unauthorized operations or information disclosure. Exploitable via tinytag. Mitigation: upgrade to 2.2.1 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32889 has been found in tinytag.
Attackers can target a specific entry point like tinytag over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade tinytag to 2.2.1 or later.
If unsure, ask your IT team or search "tinytag CVE-2026-32889" on the vendor's site.
CVE-2026-32889 (tinytag) — CWE-835 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: tinytag / SYLT / TinyTag.get / _load
Patched: 2.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-835) exists in tinytag. Attackers reach the vulnerable code path via tinytag without authentication.
Check the vendor advisory for the affected versions of tinytag. Attack surface: tinytag / SYLT / TinyTag.get / _load.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.2.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tinytag' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tinytag' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tinytagを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tinytag to 2.2.1ステージング環境で 2.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- patch github.com