CVE-2026-2245
Out-of-Bounds Read in CCExtractor MPEG-TS Parser (Local Exploit
Publication date: 2026-02-09
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ccextractor | ccextractor | to 183 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in CCExtractor up to version 183, specifically in the functions parse_PAT and parse_PMT within the MPEG-TS File Parser component. It allows an attacker to cause an out-of-bounds read by manipulating these functions.
The attack can only be performed from a local environment, meaning the attacker needs local access to exploit this issue.
A patch has been released to fix this vulnerability, and it is recommended to apply it.
How can this vulnerability impact me? :
The vulnerability leads to an out-of-bounds read, which can cause the application to behave unexpectedly or crash.
Since the attack requires local access, the impact is limited to users or attackers who already have some level of access to the system.
The CVSS scores indicate a low severity impact, with no confidentiality, integrity loss, but some availability impact.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The best practice to mitigate this vulnerability is to apply the patch named fd7271bae238ccb3ae8a71304ea64f0886324925.
Since the attack can only be performed from a local environment, limiting local access to trusted users can also help reduce risk.