Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 1.03% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-62898High confidence
Microsoft QUIC Information Disclosure Vulnerability
Microsoft · .NET 10.0
7.5HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft .NET 10.0 and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
4 package statesRelease-specific package status
Alpine findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Repository candidate not checked
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 |
Open-source package ranges18 source-attributed ranges
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.NETCore.App.Runtime.win-arm64 | ECOSYSTEM: introduced 10.0.0; fixed 10.0.11 | 10.0.11 | OSV record ↗aggregator derived · 17 Aug 2026 |
| NuGetMicrosoft.NETCore.App.Runtime.win-arm64 | ECOSYSTEM: introduced 9.0.0; fixed 9.0.19 | 9.0.19 | OSV record ↗aggregator derived · 17 Aug 2026 |
| NuGetMicrosoft.NETCore.App.Runtime.win-arm64 | ECOSYSTEM: introduced 8.0.0; fixed 8.0.30 | 8.0.30 | OSV record ↗aggregator derived · 17 Aug 2026 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x64 | ECOSYSTEM: introduced 10.0.0; fixed 10.0.11 | 10.0.11 | OSV record ↗aggregator derived · 17 Aug 2026 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x64 | ECOSYSTEM: introduced 9.0.0; fixed 9.0.19 | 9.0.19 | OSV record ↗aggregator derived · 17 Aug 2026 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x64 | ECOSYSTEM: introduced 8.0.0; fixed 8.0.30 | 8.0.30 | OSV record ↗aggregator derived · 17 Aug 2026 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x86 | ECOSYSTEM: introduced 10.0.0; fixed 10.0.11 | 10.0.11 | OSV record ↗aggregator derived · 17 Aug 2026 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x86 | ECOSYSTEM: introduced 9.0.0; fixed 9.0.19 | 9.0.19 | OSV record ↗aggregator derived · 17 Aug 2026 |
| NuGetMicrosoft.NETCore.App.Runtime.win-x86 | ECOSYSTEM: introduced 8.0.0; fixed 8.0.30 | 8.0.30 | OSV record ↗aggregator derived · 17 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-arm64 | >= 10.0.0, <= 10.0.10 | 10.0.11 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-arm64 | >= 9.0.0, <= 9.0.18 | 9.0.19 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-arm64 | >= 8.0.0, <= 8.0.29 | 8.0.30 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-x64 | >= 10.0.0, <= 10.0.10 | 10.0.11 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-x64 | >= 9.0.0, <= 9.0.18 | 9.0.19 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-x64 | >= 8.0.0, <= 8.0.29 | 8.0.30 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-x86 | >= 10.0.0, <= 10.0.10 | 10.0.11 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-x86 | >= 9.0.0, <= 9.0.18 | 9.0.19 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
| nugetMicrosoft.NETCore.App.Runtime.win-x86 | >= 8.0.0, <= 8.0.29 | 8.0.30 | GitHub advisory ↗upstream repository advisory · 11 Aug 2026 |
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
Use after free in Microsoft QUIC allows an unauthorized attacker to disclose information over a network.
What
Use after free in Microsoft QUIC allows an unauthorized attacker to disclose information over a network.
Why
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Use after free in Microsoft QUIC allows an unauthorized attacker to disclose information over a network.
Why
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-416 ↗
CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 11 Aug 2026 · Last source change 29 Sept 2026, 20:22 UTC · CWE-416 · Use After Free
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-56773
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.0 < 10.0.11; 8.0.0 < 8.0.30; 9.0.0 < 9.0.19; 17.14.0 < 17.14.38; 18.0 < 18.8.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- .NET 10.0: 10.0.0 < 10.0.11; .NET 8.0: 8.0.0 < 8.0.30; .NET 9.0: 9.0.0 < 9.0.19; Microsoft Visual Studio 2022 version 17.14: 17.14.0 < 17.14.38; Microsoft Visual Studio 2026 version 18.8: 18.0 < 18.8.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Vendor guidanceAuthoritative vendor guidance changed: added patch: msrc.microsoft.com/CVE-2026-62898; added remediation: msrc.microsoft.com/CVE-2026-62898.secure@microsoft.com ↗
- Before
- no authoritative guidance recorded
- After
- patch: msrc.microsoft.com/CVE-2026-62898 · remediation: msrc.microsoft.com/CVE-2026-62898
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 10.0.0 < 10.0.11; 8.0.0 < 8.0.30; 9.0.0 < 9.0.19; 17.14.0 < 17.14.38; 18.0 < 18.8.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 10.0.0 < 10.0.11; 8.0.0 < 8.0.30; 9.0.0 < 9.0.19; 17.14.0 < 17.14.38; 18.0 < 18.8.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.secure@microsoft.com ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.