← Back
OSV-2026-910
Vulnerability in gpac (OSV-2026-910)
Summary
vulnerability in gpac (OSV-2026-910). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1308b19e63ca1fb9990803bb74136f77e6c9ddee, 7ee24256a42bc8f4e117907ae77df6a095befb2c` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **OSV-2026-910** has been found in gpac.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade gpac to **1308b19e63ca1fb9990803bb74136f77e6c9ddee, 7ee24256a42bc8f4e117907ae77df6a095befb2c** or later.
If unsure, ask your IT team or search "gpac OSV-2026-910" on the vendor's site.
OSV-2026-910 (gpac) —
Patched: `1308b19e63ca1fb9990803bb74136f77e6c9ddee, 7ee24256a42bc8f4e117907ae77df6a095befb2c` — 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.
❓ What is the problem
**A vulnerability** (unclassified) exists in gpac.
📍 Affected scope
gpac — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1308b19e63ca1fb9990803bb74136f77e6c9ddee, 7ee24256a42bc8f4e117907ae77df6a095befb2c**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade gpac to 1308b19e63ca1fb9990803bb74136f77e6c9ddee, 7ee24256a42bc8f4e117907ae77df6a095befb2cステージング環境で 1308b19e63ca1fb9990803bb74136f77e6c9ddee, 7ee24256a42bc8f4e117907ae77df6a095befb2c に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
OSS-Fuzz
gpac
[{"repo":"https:\/\/github.com\/gpac\/gpac","type":"GIT","events":[{"introduced":"72f295f19da4e45b40ce36bab9a79e35b05d45e1"},{"fixed":"1308b19e63ca1fb9990803bb74136f77e6c9ddee"},{"fixed":"7ee24256a42bc8f4e117907ae77df6a095befb2c"}]}]