CVE-2026-14801

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

Score 3.3 from GitHub Security Advisory published 2026-07-06. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: Elevated riskExposed: 0

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

A security vulnerability has been detected in GPAC 26.03-DEV-rev342-g80071f700-master. The impacted element is the function txtin_probe_duration of the file src/filters/load_text.c of the component TeXML File Handler. Such manipulation of the argument txml_timescale leads to divide by zero. An attack has to be approached locally. The name of the patch is 86a5191f2e750c767253e27ed6cfd6d547afebc2. A patch should be applied to remediate this issue.

CVSS v3
3.3
EG Score
3.3(medium)
EG Risk
31(Track)
EG Risk 31/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
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 6, 2026

References (8)

Vendor Advisories for CVE-2026-14801(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
gpac1.0.1+dfsg1-4 ... 2.2.1+dfsg1-3.1~exp1 (13 versions)——

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 42× 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-08-25 13:48 UTCEPSS rescore
  2. 2026-08-24 20:49 UTCEG score recompute
  3. 2026-08-24 20:49 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 20:20 UTCEG score recompute
  6. 2026-08-21 20:20 UTCGHSA enrichment
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-18 22:30 UTCEG score recompute
  9. 2026-08-18 22:30 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 23:53 UTCEG score recompute
  13. 2026-08-15 23:53 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 02:03 UTCEG score recompute
  17. 2026-08-13 02:03 UTCGHSA enrichment
  18. 2026-08-12 13:50 UTCEPSS rescore
  19. 2026-08-11 13:42 UTCEPSS rescore
  20. 2026-08-10 23:59 UTCEPSS rescore
  21. 2026-08-10 04:14 UTCEG score recompute
  22. 2026-08-10 04:14 UTCGHSA enrichment
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-07 06:24 UTCEG score recompute
Show 43 more
  1. 2026-08-07 06:24 UTCGHSA enrichment
  2. 2026-08-06 13:46 UTCEPSS rescore
  3. 2026-08-05 19:17 UTCEPSS rescore
  4. 2026-08-04 15:09 UTCEPSS rescore
  5. 2026-08-04 08:35 UTCEG score recompute
  6. 2026-08-04 08:35 UTCGHSA enrichment
  7. 2026-08-03 10:35 UTCEPSS rescore
  8. 2026-08-02 02:26 UTCEPSS rescore
  9. 2026-08-01 08:31 UTCEG score recompute
  10. 2026-08-01 08:31 UTCGHSA enrichment
  11. 2026-08-01 04:15 UTCEPSS rescore
  12. 2026-07-30 16:27 UTCEPSS rescore
  13. 2026-07-30 01:30 UTCEPSS rescore
  14. 2026-07-29 10:41 UTCEG score recompute
  15. 2026-07-29 10:41 UTCGHSA enrichment
  16. 2026-07-28 15:36 UTCEPSS rescore
  17. 2026-07-27 14:13 UTCEPSS rescore
  18. 2026-07-26 14:54 UTCEPSS rescore
  19. 2026-07-26 14:54 UTCEPSS rescore
  20. 2026-07-26 12:49 UTCEG score recompute
  21. 2026-07-26 12:49 UTCGHSA enrichment
  22. 2026-07-25 14:17 UTCEPSS rescore
  23. 2026-07-24 14:17 UTCEPSS rescore
  24. 2026-07-23 14:18 UTCEPSS rescore
  25. 2026-07-23 03:05 UTCEG score recompute
  26. 2026-07-22 14:08 UTCEPSS rescore
  27. 2026-07-19 14:30 UTCEPSS rescore
  28. 2026-07-18 10:04 UTCEPSS rescore
  29. 2026-07-16 17:02 UTCEPSS rescore
  30. 2026-07-15 16:57 UTCEPSS rescore
  31. 2026-07-15 00:53 UTCGHSA enrichment
  32. 2026-07-13 22:30 UTCEPSS rescore
  33. 2026-07-13 06:12 UTCEPSS rescore
  34. 2026-07-12 05:46 UTCEPSS rescore
  35. 2026-07-12 03:03 UTCGHSA enrichment
  36. 2026-07-09 19:10 UTCEPSS rescore
  37. 2026-07-09 05:12 UTCGHSA enrichment
  38. 2026-07-08 15:15 UTCEPSS rescore
  39. 2026-07-08 15:15 UTCEPSS rescore
  40. 2026-07-07 13:46 UTCEPSS rescore
  41. 2026-07-06 16:27 UTCEPSS rescore
  42. 2026-07-06 07:23 UTCEG score recompute
  43. 2026-07-06 07:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-14801?
CVE-2026-14801 is a low vulnerability published on July 6, 2026. A security vulnerability has been detected in GPAC 26.03-DEV-rev342-g80071f700-master. The impacted element is the function txtinprobeduration of the file src/filters/loadtext.c of the component TeXML File Handler. Such manipulation of the argument txmltimescale leads to divide by zero. An attack…
When was CVE-2026-14801 disclosed?
CVE-2026-14801 was first published in the National Vulnerability Database on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14801 actively exploited?
CVE-2026-14801 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 94.6% of all scored CVEs.
What is the CVSS score of CVE-2026-14801?
CVE-2026-14801 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-14801?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14801, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14801

Explore →

Is Your Infrastructure Affected by CVE-2026-14801?

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

Start Free Scan →Browse All CVEs