CVE-2026-71613

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Buffer Overflow vulnerability in GPAC c2dee3aff638cd96f9617ac5b17dc2868cd90ef3 allows an attacker to execute arbitrary code via the j2kdec_process() function. Fixed in 9a253a07fd3f6b48022bba74302bf39388dda859.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
51(Track*)
EG Risk 51/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 10, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit.
github_commit Patch Available

commit 9a253a07fd3f (gpac/gpac)

Patch available: gpac/gpac v26.07.0 (contains commit 9a253a07fd3f)

https://github.com/gpac/gpac/commit/9a253a07fd3f6b48022bba74302bf39388dda859
generic🟡 PoC Available

[Security] Heap Buffer Overflow in j2kdec_process (dec_j2k.c) via stale JP2 dimensions · Issue #3613 · gpac/gpac · GitHub

https://github.com/gpac/gpac/issues/3613

Vendor Advisories for CVE-2026-71613(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-25 11:54 UTCGHSA enrichment
  2. 2026-09-24 23:12 UTCEG score recompute
  3. 2026-09-24 23:12 UTCGHSA enrichment
  4. 2026-09-24 10:30 UTCGHSA enrichment
  5. 2026-09-23 21:49 UTCEG score recompute
  6. 2026-09-23 21:49 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 09:08 UTCGHSA enrichment
  9. 2026-09-22 20:26 UTCEG score recompute
  10. 2026-09-22 20:26 UTCGHSA enrichment
  11. 2026-09-22 07:44 UTCEG score recompute
  12. 2026-09-22 07:44 UTCGHSA enrichment
  13. 2026-09-21 21:09 UTCEPSS rescore
  14. 2026-09-21 19:03 UTCGHSA enrichment
  15. 2026-09-21 06:22 UTCEG score recompute
  16. 2026-09-21 06:22 UTCGHSA enrichment
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-20 17:41 UTCGHSA enrichment
  19. 2026-09-20 05:00 UTCGHSA enrichment
  20. 2026-09-19 16:16 UTCEG score recompute
  21. 2026-09-19 16:16 UTCGHSA enrichment
  22. 2026-09-19 03:34 UTCEG score recompute
  23. 2026-09-19 03:34 UTCGHSA enrichment
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-18 14:53 UTCGHSA enrichment
Show 35 more
  1. 2026-09-18 02:11 UTCEG score recompute
  2. 2026-09-18 02:11 UTCGHSA enrichment
  3. 2026-09-17 13:30 UTCGHSA enrichment
  4. 2026-09-17 00:46 UTCEG score recompute
  5. 2026-09-17 00:46 UTCGHSA enrichment
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 12:04 UTCEG score recompute
  8. 2026-09-16 12:04 UTCGHSA enrichment
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 23:22 UTCGHSA enrichment
  11. 2026-09-15 10:38 UTCEG score recompute
  12. 2026-09-15 10:38 UTCGHSA enrichment
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 21:55 UTCGHSA enrichment
  15. 2026-09-14 09:12 UTCGHSA enrichment
  16. 2026-09-13 20:31 UTCEG score recompute
  17. 2026-09-13 20:31 UTCGHSA enrichment
  18. 2026-09-13 07:49 UTCGHSA enrichment
  19. 2026-09-12 19:09 UTCEG score recompute
  20. 2026-09-12 19:09 UTCGHSA enrichment
  21. 2026-09-12 15:02 UTCEPSS rescore
  22. 2026-09-12 06:27 UTCGHSA enrichment
  23. 2026-09-11 17:46 UTCEG score recompute
  24. 2026-09-11 17:46 UTCGHSA enrichment
  25. 2026-09-11 14:53 UTCEPSS rescore
  26. 2026-09-11 05:04 UTCEG score recompute
  27. 2026-09-11 05:04 UTCGHSA enrichment
  28. 2026-09-10 16:23 UTCEG score recompute
  29. 2026-09-10 16:23 UTCGHSA enrichment
  30. 2026-09-10 15:20 UTCEG score recompute▲ 7.80
  31. 2026-09-10 15:20 UTCGHSA enrichment
  32. 2026-09-10 15:20 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  33. 2026-09-09 20:29 UTCNVD update
  34. 2026-09-09 20:00 UTCEG score recompute
  35. 2026-09-09 19:59 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71613?
CVE-2026-71613 is a high vulnerability published on September 9, 2026. Buffer Overflow vulnerability in GPAC c2dee3aff638cd96f9617ac5b17dc2868cd90ef3 allows an attacker to execute arbitrary code via the j2kdec_process() function. Fixed in 9a253a07fd3f6b48022bba74302bf39388dda859.
When was CVE-2026-71613 disclosed?
CVE-2026-71613 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71613 actively exploited?
CVE-2026-71613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.2% of all scored CVEs.
What is the CVSS score of CVE-2026-71613?
CVE-2026-71613 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-71613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71613, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-71613

Explore →

Is Your Infrastructure Affected by CVE-2026-71613?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs