Gpac up to 26.03-DEV-rev342-g80071f700-master Xmt File xmt_node_end use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in Gpac. It has been rated as problematic. This vulnerability affects the function xmt_node_end of the component Xmt File Handler. The manipulation leads to use after free.
This vulnerability is documented as CVE-2026-130798. The attack needs to be performed locally. There is not any exploit available.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, has been found in Gpac. This issue affects the function xmt_node_end of the component Xmt File Handler. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
GPAC before 26.07.0 contains a use-after-free vulnerability in the XMT scene loader that leaves dangling MFURL pointers when xmt_node_end() discards nodes. Attackers can convince a user to open a crafted XMT file with MP4Box, causing xmt_resolve_od_links() to access freed heap memory and crash the process.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-130798 since 11/17/2026. The exploitation is known to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 26.07.0 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 0.5.2
- 0.7.1
- 0.7.2
- 0.8
- 0.8.0
- 0.8.0-rev177-g51a8ef874-master
- 0.9.0-development-20191109
- 1.0.1
- 1.1.0
- 1.1.0-DEV-rev1663-g881c6a94a-master
- 1.1.0-DEV-rev1727-g8be34973d-master
- 1.1.0-DEV-rev1759-geb2d1e6dd
- 2.0
- 2.0.0
- 2.1-DEV
- 2.1-DEV-rev87-g053aae8-master
- 2.1-DEV-rev232-gfcaa01ebb-master
- 2.1-DEV-rev368-gfd054169b-master
- 2.1-DEV-rev428-gcb8ae46c8-master
- 2.1-DEV-rev478-g696e6f868-master
- 2.1-DEV-rev490-g68064e101-master
- 2.1-DEV-rev505-gb9577e6ad-master
- 2.1-DEV-rev574-g9d5bb184b
- 2.1-DEV-rev593-g007bf61a0
- 2.1-DEV-rev617-g85ce76efd
- 2.1-DEV-rev644-g5c4df2a67
- 2.1-DEV-rev649-ga8f438d20
- 2.1.0-DEV
- 2.2
- 2.2-rev0-gab012bbfb-master
- 2.2.1
- 2.2.2
- 2.2.2-DEV
- 2.3
- 2.3-DEV
- 2.3-DEV-rev1-g4669ba229-master
- 2.3-DEV-rev35-gbbca86917-master
- 2.3-DEV-rev40-g3602a5ded
- 2.3-DEV-rev381-g817a848f6-master
- 2.3-DEV-rev449-g5948e4f70-master
- 2.3-DEV-rev566-g50c2ab06f-master
- 2.3-DEV-rev573-g201320819-master
- 2.3-DEV-rev588-g7edc40fee-master
- 2.3-DEV-rev602-ged8424300-master
- 2.3-DEV-rev605-gfc9e29089-master
- 2.3-DEV-rev617-g671976fcc-maste
- 2.3-DEV-rev617-g671976fcc-master
- 2.3-DEV-rev636-gfbd7e13aa-master
- 2.3-DEV-rev921-g422b78ecf-master
- 2.3.0-DEV
- 2.4
- 2.4.0
- 2.5
- 2.5-DEV-rev228-g11067ea92-master
- 2.5-DEV-rev1593-gfe88c3545-master
- 3.1
- 4.3
- 4.c
- 26.02.0
- 26.03-DEV
- 26.03-DEV-rev342-g80071f700-master
License
Website
- Product: https://github.com/gpac/gpac/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.6
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Gpac 26.07.0
Timeline
11/17/2026 Advisory disclosed11/17/2026 CVE reserved
11/17/2026 VulDB entry created
11/17/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: VulnCheck
CVE: CVE-2026-130798 (🔒)
GCVE (CVE): GCVE-0-2026-130798
GCVE (VulDB): GCVE-100-438221
Entry
Created: 11/17/2026 21:13Changes: 11/17/2026 21:13 (77)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.