dbcve.org
MinttyApplication · Mintty Project

CVE-2025-1052

HIGH · 8.8 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 3.7.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Mintty Sixel Image Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Mintty. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of sixel images. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-23382.

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 · high confidence

Mintty is a terminal emulator for Cygwin and MSYS2. This heap-based buffer overflow vulnerability exists in the sixel image parsing functionality. The flaw results from insufficient validation of user-supplied data length before copying into heap-based memory buffers, allowing an attacker to overwrite adjacent heap memory and achieve arbitrary code execution. Exploitation requires the victim to either visit a malicious webpage or open a malicious file containing specially crafted sixel image data.

MitigationApply vendor patches for Mintty when available. Until then, avoid opening untrusted files or visiting untrusted pages that may contain sixel image content, as user interaction is required for exploitation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MinttyApplication
Affected:< 3.7.5

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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. Check installed Mintty version
    Run 'mintty --version' or look at the Mintty application properties/version information
    Affected if The version number is less than 3.7.5 (e.g., 3.7.4, 3.7.0, etc.)
  2. Verify sixel support status
    Inspect Mintty configuration file (typically ~/.minttyrc or the settings dialog) for sixel-related options, or check if 'sixel' appears in the TERM environment variable setting
    Affected if Sixel image display is enabled in Mintty settings or configured via environment variables
  3. Check TERM variable for sixel capability
    Run 'echo $TERM' in the Mintty terminal to see the current terminal type
    Affected if The TERM variable is set to a sixel-capable value (such as 'xterm-256color' with sixel patches or a sixel-specific term) and sixel is being actively used

You are affected if Mintty version is below 3.7.5 AND sixel image display support is enabled or actively used in your environment.

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.

dbcve · scoped
Upgrade available Upgrade to 3.7.5 or later
Fixed in 3.7.5
Interim mitigation

Apply vendor patches for Mintty when available. Until then, avoid opening untrusted files or visiting untrusted pages that may contain sixel image content, as user interaction is required for exploitation.

Recommended fix High confidence

Mintty 3.7.5 or later

  1. Identify the current Mintty version installed
  2. Download Mintty version 3.7.5 or later from the official project repository
  3. Replace the existing Mintty installation with the updated version
  4. Restart any running Mintty instances
  5. Verify the new version is installed correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mintty Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1052 — 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-2025-1052 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