CVE-2026-2245
📋 TL;DR
An out-of-bounds read vulnerability exists in CCExtractor's MPEG-TS file parser affecting versions up to 183. This allows local attackers to read memory beyond allocated buffers, potentially exposing sensitive information. Only users running CCExtractor on affected versions are impacted.
💻 Affected Systems
- CCExtractor
⚠️ Manual Verification Required
This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.
Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).
🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.
- Review the CVE details at NVD
- Check vendor security advisories for your specific version
- Test if the vulnerability is exploitable in your environment
- Consider updating to the latest version as a precaution
⚠️ Risk & Real-World Impact
Worst Case
Information disclosure of sensitive memory contents, potentially including credentials or other application data
Likely Case
Application crash or denial of service due to invalid memory access
If Mitigated
No impact if patched or proper access controls prevent local exploitation
🎯 Exploit Status
Exploit requires local access and ability to feed malicious MPEG-TS files to CCExtractor
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Commit fd7271bae238ccb3ae8a71304ea64f0886324925 and later
Vendor Advisory: https://github.com/CCExtractor/ccextractor/issues/2053
Restart Required: Yes
Instructions:
1. Update CCExtractor to version after commit fd7271bae238ccb3ae8a71304ea64f0886324925
2. Rebuild from source if using compiled version
3. Restart any CCExtractor processes
🔧 Temporary Workarounds
Restrict file processing
allLimit CCExtractor to trusted MPEG-TS files only
Access control
linuxRestrict local user access to CCExtractor binary and input files
chmod 750 /path/to/ccextractor
chown root:trustedgroup /path/to/ccextractor
🧯 If You Can't Patch
- Disable or remove CCExtractor from production systems
- Implement strict file validation before passing to CCExtractor
🔍 How to Verify
Check if Vulnerable:
Check CCExtractor version with 'ccextractor --version' and verify if version is 183 or earlierCheck Version:
ccextractor --versionVerify Fix Applied:
Verify commit hash includes fd7271bae238ccb3ae8a71304ea64f0886324925 or version is newer than 183📡 Detection & Monitoring
Log Indicators:
- Segmentation fault errors
- Memory access violation logs
- Unexpected application crashes
Network Indicators:
- None - local exploitation only
SIEM Query:
process.name:"ccextractor" AND (event.action:"segmentation_fault" OR event.action:"crash")🔗 References
- https://github.com/CCExtractor/ccextractor/
- https://github.com/CCExtractor/ccextractor/commit/fd7271bae238ccb3ae8a71304ea64f0886324925
- https://github.com/CCExtractor/ccextractor/issues/2053
- https://github.com/CCExtractor/ccextractor/pull/2057
- https://github.com/oneafter/0123/blob/main/cc1/repro
- https://vuldb.com/?ctiid.344991
- https://vuldb.com/?id.344991
- https://vuldb.com/?submit.753159
- https://vuldb.com/?submit.753160
