Crash and heap disclosure via unchecked comment offset
Published Jun 16, 2026 · Updated Jun 16, 2026
Heap buffer over-read in tracker-extract-mp3 on Red Hat Enterprise Linux allows local users to crash the extractor via a malformed MP3 file. The get_id3v23_tags function computes a COMM text offset without ensuring it remains below the frame size, so csize subtraction underflows and g_convert reads beyond the heap buffer. Processing the crafted file requires user interaction; the public proof of concept demonstrates a SIGSEGV crash, while heap disclosure remains unshown.
Summary
What happened
Heap buffer over-read in tracker-extract-mp3 on Red Hat Enterprise Linux allows local users to crash the extractor via a malformed MP3 file. The get_id3v23_tags function computes a COMM text offset without ensuring it remains below the frame size, so csize subtraction underflows and g_convert reads beyond the heap buffer. Processing the crafted file requires user interaction; the public proof of concept demonstrates a SIGSEGV crash, while heap disclosure remains unshown.
The record
- CVE
- CVE-2026-1766
- Published
- Jun 16, 2026
- Updated
- Jun 16, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 10
- Classifications
- CWE-805, T1204.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 16, 2026CVE publishedPublication date reported by the CVE source.
- Jun 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- reproduction_comm.mp3 crash proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo