CVE-2025-55248 | .NET, .NET Framework, and Visual Studio Information Disclosure Vulnerability

Inadequate encryption strength in .NET, .NET Framework, Visual Studio allows an authorized attacker to disclose information over a network.

Published: 2025-10-14 Last update: 2025-10-23 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-55248 is rated Low Risk (36.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.68%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-55248

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.68% +0.66%
2 2026-03-12 0.05% 0.02% -0.03%
3 2026-02-13 — 0.05% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-55248

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 3.6 [email protected]
5.7 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.1 3.6 [email protected]

Weakness enumeration for CVE-2025-55248

GitHub Security Advisory for CVE-2025-55248

GHSA-gwq6-fmvp-qp68 · Severity: medium · Ecosystem: nuget — Microsoft Security Advisory CVE-2025-55248: .NET Information Disclosure Vulnerability

OS Trackers for CVE-2025-55248

vendor priority summary link
alpine — CVE-2025-55248: 2 source package rows (dotnet8-runtime, dotnet9-runtime); 4 state rows across 2 repos (3.22-community, edge-community); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2025-55248
redhat high — https://access.redhat.com/security/cve/CVE-2025-55248
ubuntu medium CVE-2025-55248 medium priority: Ubuntu including 5 source packages (dotnet10, dotnet6, dotnet7, dotnet8, dotnet9), 45 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 29, needs-triage 6, released 6, ignored 2, deferred 1, not-affected 1. https://ubuntu.com/security/CVE-2025-55248

Affected software / configurations for CVE-2025-55248

Vendor Product Version Raw CPE
microsoft .net_framework 4.6.2 cpe:2.3:a:microsoft:.net_framework:4.6.2:*:*:*:*:*:*:*
microsoft .net_framework 4.7 cpe:2.3:a:microsoft:.net_framework:4.7:*:*:*:*:*:*:*
microsoft .net_framework 4.7.1 cpe:2.3:a:microsoft:.net_framework:4.7.1:*:*:*:*:*:*:*
microsoft .net_framework 4.7.2 cpe:2.3:a:microsoft:.net_framework:4.7.2:*:*:*:*:*:*:*
microsoft .net_framework 3.5.1 cpe:2.3:a:microsoft:.net_framework:3.5.1:*:*:*:*:*:*:*
microsoft .net_framework 3.5 cpe:2.3:a:microsoft:.net_framework:3.5:-:*:*:*:*:*:*
microsoft .net_framework 4.8.1 cpe:2.3:a:microsoft:.net_framework:4.8.1:*:*:*:*:*:*:*
microsoft .net_framework 4.8 cpe:2.3:a:microsoft:.net_framework:4.8:*:*:*:*:*:*:*
microsoft .net_framework 3.0 cpe:2.3:a:microsoft:.net_framework:3.0:sp2:*:*:*:*:*:*
microsoft .net >= 8.0.0, < 8.0.21 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
microsoft .net >= 9.0.0, < 9.0.10 cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.10.0, < 17.10.20 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.12.0, < 17.12.13 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*
microsoft visual_studio_2022 >= 17.14.0, < 17.14.17 cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*

References for CVE-2025-55248

cvelogic Threat Intelligence