CVE-2025-21171VulnerabilityPublished 14 Jan 2025Updated 11 Oct 2026

SUSE · bugfix update for dotnet9.0

Affects SUSESource GCVE Database

Authoritative record:CVE-2025-21171· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in 9.9 : patch SUSE soon.

Data as of 26 Oct 2026, 07:57 UTC

CVSS base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.9, 9.6, 8.11 +1

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade SUSE to 9.9, 9.6, 8.11 or 7.5.2.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=8.0 <8.11 >=9.0 <9.6 >=9.6 <9.9 >=7.5.0 <7.5.2	Fixed in 8.11 9.6 9.9 7.5.2

AI-suggested

A patch is available and users should apply the updated .NET 9.0 SDK (9.0.102) and Runtime (9.0.1) packages provided by Red Hat as detailed in their advisory (https://access.redhat.com/errata/RHBA-2025:0305). Applying these updates promptly will mitigate the risk posed by this vulnerability.

Description

CVE-2025-21171 is a high-severity remote code execution vulnerability in multiple versions of the .NET 9.0 framework implementation used by PowerShell and related runtimes. The flaw allows remote attackers to execute arbitrary code. Red Hat has released updated .NET SDK and Runtime packages that fix this vulnerability. Users of affected versions are advised to apply these updates promptly to mitigate risk.

Impact

Successful exploitation of this vulnerability could allow remote attackers to execute arbitrary code on affected systems, potentially leading to full system compromise. This poses a significant security risk to systems running vulnerable versions of the .NET 9.0 framework, especially those running PowerShell or related services.

Summary

CVE-2025-21171 is a remote code execution vulnerability affecting multiple versions of the .NET 9.0 SDK and Runtime, including those used by PowerShell. The vulnerability allows an attacker to execute arbitrary code remotely. Red Hat's advisory details updated packages for Red Hat Enterprise Linux 9 that address this issue by updating the .NET 9.0 SDK to version 9.0.102 and the Runtime to 9.0.1. The affected versions include ranges from 7.5.0 up to but not including 9.9 across various subversions and packages such as aspnetcore-runtime and targeting packs. No known exploits in the wild have been reported at this time.

CWE-122Heap-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #16
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Pre-design: Use a language or compiler that performs automatic bounds checking.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-641Improper Restriction of Names for Files and Other Resources (opens in a new tab)
Base weaknessLikelihood of exploit: Low
The product constructs the name of a file or other resource using input from an upstream component, but it does not restrict or incorrectly restricts the resulting name.
Architecture and Design
Do not allow users to control names of resources used on the server side.
Architecture and Design
Perform allowlist input validation at entry points and also before consuming the resources. Reject bad file names rather than trying to cleanse them.
Architecture and Design
Make sure that technologies consuming the resources are not vulnerable (e.g. buffer overflow, format string, etc.) in a way that would allow code execution if the name of the resource is malformed.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.4 (opens in a new tab)
V1.5.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-379Creation of Temporary File in Directory with Insecure Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.
Requirements
Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
Implementation
Try to store sensitive tempfiles in a directory which is not world readable -- i.e., per-user directories.
Implementation
Avoid using vulnerable temp file functions.
OWASP Cheat Sheets
Authorization (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-126Buffer Over-read (opens in a new tab)
Variant weakness
The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:40 UTC

WeaknessesCWE-122, CWE-641, CWE-379 +1

Technical details

References

Community reviews

Related threats