Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.76% for the current model date.
BlackTreeCVE IntelligenceMicrosoft · .NET 10.0
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Alpine findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | dotnet8-runtime | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.0.31-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.23v3.23 · community | dotnet9-runtime | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 9.0.20-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | dotnet8-runtime | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 8.0.31-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
| Alpine v3.22v3.22 · community | dotnet9-runtime | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 9.0.20-r0 | Alpine Security Database ↗Source updated 11 Sep 2026 |
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| NuGetMicrosoft.DiaSymReader.Native | ECOSYSTEM: introduced 17.10.0-beta1.24272.1; fixed 18.9.0-beta1.26405.2 | 18.9.0-beta1.26405.2 | OSV record ↗aggregator derived · 14 Sep 2026 |
| nugetMicrosoft.DiaSymReader.Native | >= 17.10.0-beta1.24272.1, <= 18.9.0-beta1.26405.1 | 18.9.0-beta1.26405.2 | GitHub advisory ↗upstream repository advisory · 9 Sep 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products as affected by this CVE.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch availableHeap-based buffer overflow in Visual Studio allows an unauthorized attacker to execute code over a network.
Heap-based buffer overflow in Visual Studio allows an unauthorized attacker to execute code over a network.
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().
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
Heap-based buffer overflow in Visual Studio allows an unauthorized attacker to execute code over a network.
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().
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-122: Heap-based Buffer Overflow. 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().
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 8 Sept 2026 · Last source change 1 Oct 2026, 23:00 UTC · CWE-122 · Heap-based Buffer Overflow
Core structured fields are present and their contributing authorities are shown above.