Quick answers
- Is CVE-2026-1766 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-1766 being exploited in the wild.
- How severe is CVE-2026-1766?
- Medium severity, with a CVSS score of 5.6, published 16 June 2026.
- Which products and versions are affected?
- Gnome Localsearch unspecified.
- Is there a fix for CVE-2026-1766?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-1766 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-1766?
- Check whether you run Gnome Localsearch at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap buffer overflow (OOB Read) exists in the 'get_id3v23_tags' function within 'src/extractor/tracker-extract-mp3.c'. The vulnerability is triggered when processing ID3v2.3 COMM (Comment) tags. The extractor incorrectly calculates buffer offsets without verifying if the offset exceeds the frame size ('csize'), leading to an integer underflow when calculating the length passed to 'id3v2_text_to_utf8'. This results in 'g_convert' performing an out-of-bounds read. An attacker can exploit this by providing a malformed MP3 file, causing a SIGSEGV (Denial of Service) or leaking heap memory.
Affected products
- GNOME localsearch (tracker-miners) unspecified
Timeline
- 2026-02-02: disclosed: Initial report in Red Hat Bugzilla
- 2026-06-16: advisory: CVE published to NVD