Vulnerability in tinytag (CVE-2026-104266)
Summary
Vulnerability in tinytag (CVE-2026-104266). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.3.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) 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-104266 has been found in tinytag.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade tinytag to 2.3.0 or later.
If unsure, ask your IT team or search "tinytag CVE-2026-104266" on the vendor's site.
CVE-2026-104266 (tinytag) — CWE-835 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.3.0 — apply immediately
Workaround: No workarounds exist.
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.
Check the vendor advisory for the affected versions of tinytag.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2.3.0.
Workaround: No workarounds exist.
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 temporary workaround mitigate
No workarounds exist.パッチが適用されるまでの応急処置として、No workarounds exist. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade tinytag to 2.3.0ステージング環境で 2.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。