CVE-2026-20833

CVE-2026-20833 is a medium-severity vulnerability in Microsoft Windows Server 2008 with a CVSS 3.x base score of 5.5. 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-327.

Key facts

Description

Use of a broken or risky cryptographic algorithm in Windows Kerberos allows an authorized attacker to disclose information locally.

Frequently asked questions

What is CVE-2026-20833?
Use of a broken or risky cryptographic algorithm in Windows Kerberos allows an authorized attacker to disclose information locally.
How severe is CVE-2026-20833?
CVE-2026-20833 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-20833 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (28th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-20833?
CVE-2026-20833 primarily affects Microsoft Windows Server 2008. In total, 10 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2026-20833?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-20833 have an EU (EUVD) identifier?
Yes. CVE-2026-20833 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-2153.
When was CVE-2026-20833 published?
CVE-2026-20833 was published on 2026-01-13 and last updated on 2026-06-17.

References

Affected products (10)

More vulnerabilities in Microsoft Windows Server 2008

All CVEs affecting Microsoft Windows Server 2008 →

Other CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities

Browse all CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) vulnerabilities →