How severe is CVE-2026-69519?

CVE-2026-69519 has a CVSS 3.x base score of 8.6, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-69519 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-69519?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-69519 published?

CVE-2026-69519 was published on 2026-08-20 and last updated on 2026-08-21.

CVE-2026-69519

CVE-2026-69519 is a high-severity vulnerability with a CVSS 3.x base score of 8.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-204.

Key facts

Severity: High (CVSS 3.x base score 8.6)
EPSS exploit prediction: 1% (45th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-204
Published: 2026-08-20
Last modified: 2026-08-21

Description

Observable response discrepancy in Azure Stack HCI allows an unauthorized attacker to disclose information over a network.

Frequently asked questions

What is CVE-2026-69519?: Observable response discrepancy in Azure Stack HCI allows an unauthorized attacker to disclose information over a network.
How severe is CVE-2026-69519?: CVE-2026-69519 has a CVSS 3.x base score of 8.6, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-69519 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (45th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-69519?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-69519 published?: CVE-2026-69519 was published on 2026-08-20 and last updated on 2026-08-21.

References

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69519

Other CWE-204 vulnerabilities

CVE-2018-25350 — Critical (CVSS 9.8): userSpice 4.3.24 contains a username enumeration vulnerability that allows unauthenticated attackers to discover valid…
CVE-2026-15747 — Critical (CVSS 9.1): Mojolicious versions from 4.59 before 9.48 for Perl expose a stable representation of the session CSRF token to a…
CVE-2025-5485 — High (CVSS 8.6): User names used to access the web management interface are limited to the device identifier, which is a numerical…
CVE-2026-27462 — High (CVSS 7.5): Combodo iTop is a web based IT service management tool. Prior to 3.2.3, iTop returns different responses for…
CVE-2026-33419 — High (CVSS 7.5): MinIO is a high-performance object storage system. Prior to RELEASE.2026-03-17T21-25-16Z, MinIO AIStor's STS (Security…
CVE-2025-12455 — High (CVSS 7.5): Observable response discrepancy vulnerability in OpenText™ Vertica allows Password Brute Forcing. The…

Browse all CWE-204 vulnerabilities →