Vulnerability in membrane_mp4_plugin (CVE-2026-53423)
Summary
Vulnerability in membrane_mp4_plugin (CVE-2026-53423). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.36.7 or later.
Original description
The description as published by the source.
Summary
membrane_mp4_plugin interns every 4-byte MP4 box name as a BEAM atom while parsing container headers, with no validation against an allow-list. Any code path that calls Membrane.MP4.Container.parse/1 (or the bang variant) on attacker-controlled MP4 bytes can be made to exhaust the BEAM atom table, which is uncapped at the source but bounded by the runtime ceiling (around 1,048,576 atoms) and never garbage-collected. Once the ceiling is hit, the entire BEAM node aborts.
Details
The MP4 container parser walks the input stream box-by-box. For each box, Membrane.MP4.Container.Header.parse/1 in lib/membrane_mp4/container/header.ex extracts the 4-byte name field and delegates to the private helper parse_box_name/1, which trims trailing spaces and passes the bytes through String.to_atom/1. Because String.to_atom/1 creates a new atom unconditionally, every distinct attacker-chosen 4-byte sequence becomes a permanent allocation in the global atom table. Atoms are not subject to garbage collection, so unique names accumulate for the lifetime of the node.
The fix replaces the unsafe interning with String.to_existing_atom/1 and treats unknown names as the :unknown atom downstream (with related plumbing in parse_helper.ex, serialize_helper.ex, and the ISOM/CMAF demuxer engines so the new error variant flows through cleanly).
PoC
- Generate an MP4-shaped payload of roughly 1.1 million minimal box headers, each 8 bytes long (4-byte size of 8,…
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-53423 has been found in membrane_mp4_plugin.
Risk of unauthorized operations or information disclosure.
What to do: upgrade membrane_mp4_plugin to 0.36.7 or later.
If unsure, ask your IT team or search "membrane_mp4_plugin CVE-2026-53423" on the vendor's site.
CVE-2026-53423 (membrane_mp4_plugin) — CWE-770
Patched: 0.36.7 — 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-770) exists in membrane_mp4_plugin.
Check the vendor advisory for the affected versions of membrane_mp4_plugin.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.36.7.
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 'membrane_mp4_plugin' . 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 'membrane_mp4_plugin' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
membrane_mp4_pluginを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade membrane_mp4_plugin to 0.36.7ステージング環境で 0.36.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package hex.pm
- package github.com
- web cna.erlef.org
- web github.com
- web github.com
- web osv.dev
- web github.com