GPAC MP4Box up to 26.07.0 Node Destruction gf_node_try_destroy use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.20+ |
Summary
A vulnerability was found in GPAC MP4Box up to 26.07.0 and classified as problematic. Impacted is the function gf_node_try_destroy of the component Node Destruction. The manipulation results in use after free.
This vulnerability is cataloged as CVE-2026-132765. The attack must be initiated from a local position. There is no exploit available.
Details
A vulnerability classified as problematic has been found in GPAC MP4Box up to 26.07.0. Affected is the function gf_node_try_destroy of the component Node Destruction. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
GPAC MP4Box through 26.07.0 contains a use-after-free vulnerability in gf_node_try_destroy because Conditional node commands keep raw pointers to target nodes freed by gf_sg_reset(). Attackers can supply a crafted XMT scene processed with -info or -add to trigger heap use-after-free, crashing the process and corrupting heap memory.
The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-132765 since 11/18/2026. The exploitability is told to be easy. The attack needs to be approached locally. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 11/19/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
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.7
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/18/2026 CVE reserved11/18/2026 VulDB entry created
11/19/2026 Advisory disclosed
11/19/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CNA: VulnCheck
CVE: CVE-2026-132765 (🔒)
GCVE (CVE): GCVE-0-2026-132765
GCVE (VulDB): GCVE-100-439884
Entry
Created: 11/19/2026 00:39Changes: 11/19/2026 00:39 (76)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.