ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-11233

Starting from Rust 1.87.0 and before Rust 1.89.0, the tier 3 Cygwin target ( ) didn't correctly handle path separators, causing the standard library's Path API to ignore path compo

Published Oct 1, 2025 · catalog updated Oct 1, 2025 · Rust Project

Last checked Oct 26, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-11233. EPSS is 0.52%. Act only if a listed version of Rust Project is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium6.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.52%
Remediation
Version ranges on file
Affected products
vendor Rust Project std 1.87.0 <1.89.0

Starting from Rust 1.87.0 and before Rust 1.89.0, the tier 3 Cygwin target ( ) didn't correctly handle path separators, causing the standard library's Path API to ignore path components separated by backslashes. Due to this, programs compiled for Cygwin that validate paths could misbehave, potentially allowing path traversal attacks or malicious filesystem operations. Rust 1.89.0 fixes the issue by handling both Win32 and Unix style paths in the standard library for the Cygwin target. While we assess the severity of this vulnerability as "medium", please note that the tier 3 Cygwin compilation

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Rust Project std 1.87.0 <1.89.01.87.0 <1.89.0

How to fix CVE-2025-11233

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-11233. EPSS is 0.52%. Act only if a listed version of Rust Project is installed.

Which versions are affected?

Compare what you have installed with Rust Project std 1.87.0 <1.89.0 1.87.0 <1.89.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.52%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 1, 2025 · EUVD

    Detected

    Starting from Rust 1.87.0 and before Rust 1.89.0, the tier 3 Cygwin target ( ) didn't correctly handle path separators, causing the standard library's Path API to ignore path components separated by backslashes. Due to this, programs compiled for Cygwin that validate paths could misbehave, potentially allowing path traversal attacks or malicious filesystem operations. Rust 1.89.0 fixes the issue b

  2. Oct 1, 2025 · EUVD

    Updated

    Starting from Rust 1.87.0 and before Rust 1.89.0, the tier 3 Cygwin target ( ) didn't correctly handle path separators, causing the standard library's Path API to ignore path components separated by backslashes. Due to this, programs compiled for Cygwin that validate paths could misbehave, potentially allowing path traversal attacks or malicious filesystem operations. Rust 1.89.0 fixes the issue b

Sources

  • CVE.orgVulnerability recordCVE-2025-11233

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-11233

    30-day exploitation probability 0.52%

    first.org
  • EUVDVulnerability recordEUVD-2025-33229

    Starting from Rust 1.87.0 and before Rust 1.89.0, the tier 3 Cygwin target ( ) didn't correctly handle path separators, causing the standard library's Path API to ignore path components separated by backslashes. Due to this, programs compiled for Cygwin that validate paths could

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 26, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSOct 26, 2026
  • CVE.orgOct 23, 2026
  • EUVDOct 23, 2026