Microsoft ASP.NET Core/Visual Studio allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Microsoft ASP.NET Core and Visual Studio. This issue affects some unknown processing. Such manipulation leads to allocation of resources. This vulnerability is documented as CVE-2025-26682. The attack can be executed remotely. There is not any exploit available. It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Microsoft ASP.NET Core and Visual Studio (affected version not known). It has been rated as problematic. Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. CVE summarizes:
Allocation of resources without limits or throttling in ASP.NET Core allows an unauthorized attacker to deny service over a network.
The weakness was released 04/08/2025 as confirmed security update guide (Website). The advisory is shared for download at msrc.microsoft.com. This vulnerability is handled as CVE-2025-26682. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/25/2025). The MITRE ATT&CK project declares the attack technique as T1499.
The vulnerability scanner Nessus provides a plugin with the ID 234051 (Security Update for Microsoft .NET Core (April 2025)), which helps to determine the existence of the flaw in a target environment.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Tenable (234051) and EUVD (EUVD-2025-10197). Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.5
Vendor Vector (Microsoft): 🔍
CNA Base Score: 7.5
CNA Vector (Microsoft): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 234051
Nessus Name: Security Update for Microsoft .NET Core (April 2025)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
04/08/2025 🔍04/08/2025 🔍
04/08/2025 🔍
10/25/2025 🔍
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2025-26682 (🔍)
GCVE (CVE): GCVE-0-2025-26682
GCVE (VulDB): GCVE-100-303956
EUVD: 🔍
Entry
Created: 04/08/2025 19:53Updated: 10/25/2025 08:06
Changes: 04/08/2025 19:53 (33), 04/08/2025 19:57 (35), 04/09/2025 09:56 (2), 05/16/2025 19:16 (1), 10/25/2025 08:06 (13)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.