dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2026-1765

MEDIUM · 5.6 CVSS v3.1 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in the `tracker-extract-mp3` component of GNOME localsearch (previously known as tracker-miners). This vulnerability, a heap buffer overflow, occurs when processing specially crafted MP3 files. A remote attacker could exploit this by providing a malicious MP3 file, leading to a Denial of Service (DoS) where the application crashes. It may also potentially expose sensitive information from the system's memory.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A heap buffer overflow vulnerability exists in the `tracker-extract-mp3` component of GNOME tracker-miners (localsearch). The flaw is triggered when processing specially crafted MP3 files, allowing a remote attacker to cause a denial of service via application crash or potentially read sensitive data from heap memory.

MitigationUpdate GNOME tracker-miners to the patched version. Until then, avoid processing untrusted MP3 files with the tracker-extract-mp3 component or disable the MP3 extraction functionality in tracker-miners.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify tracker-miners package is installed
    Check if the tracker-miners package exists on the system. On Debian/Ubuntu: `dpkg -l | grep tracker-miners`. On RHEL/Fedora: `rpm -qa | grep tracker-miners`. On Arch: `pacman -Q tracker-miners`.
    Affected if The package is not installed, then the component is not present and not affected.
  2. Determine installed tracker-miners version
    Run `tracker-miners --version` or use the package manager to query the version (e.g., `dpkg -s tracker-miners` on Debian/Ubuntu, `rpm -qi tracker-miners` on RHEL/Fedora).
    Affected if The installed version falls within any affected version range (compare against released advisory version numbers when available).
  3. Confirm tracker-extract-mp3 binary exists
    Locate the tracker-extract-mp3 binary by running `which tracker-extract-mp3` or searching in common paths like `/usr/libexec/tracker-extract-mp3` or `/usr/bin/tracker-extract-mp3`.
    Affected if The binary does not exist, then the vulnerable component is not present.
  4. Check if MP3 indexing is enabled in tracker-miners
    Inspect tracker-miners configuration. Check for configuration files in `~/.config/tracker/` or `/etc/xdg/tracker-miners/`. Look for entries related to MP3 file type indexing or the extractor settings.
    Affected if MP3 extraction is explicitly disabled in configuration, the vulnerable code path is not exercised.
  5. Verify if tracker-miners service is active and indexing MP3 files
    Check if the tracker-miners service is running (`systemctl status tracker-miners` or `ps aux | grep tracker`). Inspect recently indexed MP3 files using `tracker search --limit 10 mp3` or similar query commands.
    Affected if The service is active and processes MP3 files, the vulnerable code path can be triggered.

A user is affected if tracker-miners with the tracker-extract-mp3 component is installed, running, and configured to index MP3 files, and the installed version matches an affected release.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update GNOME tracker-miners to the patched version. Until then, avoid processing untrusted MP3 files with the tracker-extract-mp3 component or disable the MP3 extraction functionality in tracker-miners.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1765 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1765 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data