Out-of-Bounds Read in Gpac (CVE-2026-79522)
Summary
Vulnerability in Gpac (CVE-2026-79522). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2fd5a06ab226767900fd86edb5a1e8b or later.
Original description
The description as published by the source.
An out-of-bounds read in the gf_dm_get_chunk_data function (src/utils/downloader.c) of GPAC v26.07.0 allows attackers to cause a Denial of Service (DoS) via sending a crafted HTTP request. Fixed in 2fd5a06ab226767900fd86edb5a1e8bfc1010640.
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-79522 has been found in Gpac.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade Gpac to 2fd5a06ab226767900fd86edb5a1e8b or later.
If unsure, ask your IT team or search "Gpac CVE-2026-79522" on the vendor's site.
CVE-2026-79522 (Gpac) — CWE-125 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2fd5a06ab226767900fd86edb5a1e8b — 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.
Out-of-bounds read (CWE-125) exists in Gpac.
Check the vendor advisory for the affected versions of Gpac.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 2fd5a06ab226767900fd86edb5a1e8b.
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 'Gpac' . 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 'Gpac' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Gpacを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Gpac to 2fd5a06ab226767900fd86edb5a1e8bステージング環境で 2fd5a06ab226767900fd86edb5a1e8b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com