Security readout for executives and security teams
Plain-English summary
A locally authenticated attacker with limited privileges could exploit weak cryptography in Windows Kerberos to expose sensitive information. The issue affects listed Windows Server releases from 2008 through 2025, including several Server Core installations. It does not enable remote, unauthenticated compromise according to the supplied CVSS vector.
Executive priority
Schedule remediation through the normal security-update cycle, accelerating systems central to authentication or permitting less-trusted local users. The confidentiality impact is significant, but required local authentication and the absence of supported active exploitation reduce immediate emergency urgency.
Technical view
CVE-2026-20833 is a CWE-327 cryptographic weakness in Windows Kerberos. Its CVSS 3.1 score is 5.5: local access, low complexity, low privileges, no user interaction, and high confidentiality impact. The supplied assessment identifies no integrity or availability impact.
Likely exposure
Exposure is limited to the listed Windows Server versions and editions. Risk is greatest where untrusted or compromised low-privilege users can authenticate locally. The bundle does not establish that other Windows products or versions are affected.
Exploitation context
The supplied sources do not support active exploitation. The CVE is not identified as CISA KEV, and the CVSS temporal metric marks exploit maturity as unproven. Successful exploitation requires local access and low privileges; no user interaction is required.
Researcher notes
The public bundle describes information disclosure caused by risky cryptography but provides no disclosed data type, vulnerable code path, attack prerequisites beyond CVSS, or proof-of-concept details. Confirm update applicability and deeper technical behavior through Microsoft’s advisory; do not infer affected client products.
Mitigation direction
- Inventory systems running the listed Windows Server versions and Server Core editions.
- Consult Microsoft’s CVE advisory for the applicable security update for each affected system.
- Prioritize affected authentication infrastructure and systems allowing broad local authenticated access.
- Restrict unnecessary local access while updates are evaluated and deployed.
Validation and detection
- Confirm each server’s Windows edition, version, and build against the supplied affected-product list.
- Verify the applicable Microsoft security update is installed using approved patch-management records.
- Review which users and services can authenticate locally to affected servers.
- Rescan updated systems with current vulnerability-detection content and investigate remaining findings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-20833 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C1.83.6microsoftVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Windows Kerberos Information Disclosure VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.