MP4v2 through 2.1.0 contains a NULL pointer dereference vulnerability in MP4RtpHintTrack::GetPayload() in src/rtphint.cpp that passes an unchecked rtpmap value to strchr(). Attackers can supply a crafted MP4 file whose RTP hint track has a corrupted hinf atom to crash mp4info or applications calling MP4GetHintTrackRtpPayload().
CVE-2026-132753
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2026-11-19. A secondary CVSS source baseline 5.5; sources differ by 0.0.
Also known asEUVD-2026-129363 (ENISA EUVD) · GHSA-f83v-9wxp-m4mv (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 5.5
- EG Score
- 5.5MEDIUMhigh confidence
- EG Risk
- 41EG Risk 41/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity55% × 45%Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it. - EPSS PROB
- 0.2%
- EPSS %ILE
- 5th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule, then apply it.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 18, 2026
Last Modified
November 19, 2026
Advisory Details (6)
Auto-updated Nov 18, 2026MP4v2 through 2.1.0 NULL Pointer Dereference via MP4RtpHintTrack::GetPayload | Advisories | VulnCheck
https://www.vulncheck.com/advisories/mp4v2-through-2.1.0-null-pointer-dereference-via-mp4rtphinttrack-getpayloadpocs/res/mp4v2/3/src_rtphint_cpp_325 at main · sigdevel/pocs · GitHub
https://github.com/sigdevel/pocs/blob/main/res/mp4v2/3/src_rtphint_cpp_325mp4v2/src/rtphint.cpp at 8fb6e7ad592cc6da9d97ce027e7cc2d9bc503aeb · TechSmith/mp4v2 · GitHub
https://github.com/TechSmith/mp4v2/blob/8fb6e7ad592cc6da9d97ce027e7cc2d9bc503aeb/src/rtphint.cpp#L320-L326commit dfa725e3fd09 (TechSmith/mp4v2)
Fix landed in TechSmith/mp4v2 commit dfa725e3fd09 — awaiting tagged release
https://github.com/TechSmith/mp4v2/commit/dfa725e3fd099b085628f3c9d3033a5ca3461015Guard against null rtpmap value in MP4RtpHintTrack::GetPayload
Fix merged in TechSmith/mp4v2 PR #96 on 2026-11-17 — awaiting tagged release
https://github.com/TechSmith/mp4v2/pull/96src/rtphint.cpp:325 NULL Pointer Dereference in MP4RtpHintTrack::GetPayload · Issue #89 · TechSmith/mp4v2 · GitHub
https://github.com/TechSmith/mp4v2/issues/89Vendor Advisories for CVE-2026-132753(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 8× in last 7d / 8× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.2% · 5th percentile
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-11-19 22:58 UTCEchelonGraph re-scored
- 2026-11-19 22:58 UTCGHSA enrichmentGHSA-f83v-9wxp-m4mv · GitHub severity MODERATE · GitHub CVSS 5.5
- 2026-11-19 19:31 UTCEchelonGraph re-scored
- 2026-11-19 19:31 UTCGHSA enrichmentGHSA-f83v-9wxp-m4mv · GitHub severity MODERATE · GitHub CVSS 5.5
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-11-19 00:46 UTCEchelonGraph re-scored
- 2026-11-19 00:46 UTCGHSA enrichmentGHSA-f83v-9wxp-m4mv · GitHub severity MODERATE · GitHub CVSS 5.5
- 2026-11-19 00:28 UTCEchelonGraph re-scored
- 2026-11-19 00:03 UTCENISA EUVD ID recordedEUVD-2026-129363 · Source: ENISA EUVD
- 2026-11-18 23:23 UTCEchelonGraph re-scoredFirst assessed: 5.5 MEDIUM
- 2026-11-18 23:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-132753?
When was CVE-2026-132753 made public?
Is CVE-2026-132753 actively exploited?
What is the CVSS score of CVE-2026-132753?
How do I remediate CVE-2026-132753?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-132753
Is Your Infrastructure Affected by CVE-2026-132753?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.