Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/v-jfanca/cve-2026-20833-rc4-kerberos
Configuration AuditingCryptographyIdentity & Access Management (IAM)AuthenticationLearning & EducationCurated Resources
GitHubv-jfanca/cve-2026-20833-rc4-kerberos

cve-2026-20833-rc4-kerberos

Kerberos RC4 deprecation: detection, remediation and guidance (CVE-2026-20833)

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
View Repository
35 months agoNot yet reviewed
Share

CVE-2026-20833 — Kerberos RC4 Hardening

This repository consolidates technical documentation, PowerShell scripts, Power BI dashboards, and official Microsoft references related to the progressive deprecation of RC4 in Kerberos for Active Directory environments, as part of Microsoft's security changes addressing CVE-2026-20833.

The objective is to support organizations with:

  • Security auditing
  • Detection of RC4 usage
  • Remediation planning
  • Operational readiness for the Kerberos RC4 enforcement phases in 2026

[!NOTE] The materials in this repository are intended to assist organizations in identifying legacy Kerberos dependencies and preparing their environments before Microsoft enforcement phases begin.


Why this matters

RC4 is considered cryptographically weak and is being removed as an implicit fallback mechanism in Kerberos authentication.

This is not simply a hardening recommendation — it represents a structural behavior change in the Kerberos Key Distribution Center (KDC).

Organizations that still rely on RC4 may experience authentication failures when the enforcement phases begin.

Microsoft plans to introduce enforcement changes through security updates with key milestones expected in:

  • April 2026 — Initial enforcement phase
  • July 2026 — Stronger enforcement phase

[!WARNING] Environments that still depend on RC4 may experience Kerberos ticket issuance failures once enforcement phases begin.

Understanding and eliminating RC4 dependencies before enforcement begins is critical.


Repository Structure

root@kitploit:~
cve-2026-20833-rc4-kerberos
│
├─ docs/
│   Kerberos technical documentation
│
├─ scripts/
│   PowerShell scripts for Kerberos auditing
│
├─ dashboards/
│   Power BI dashboards for RC4 monitoring
│
└─ images/
    Diagrams and screenshots used in documentation

Technical Documentation

Complete technical documentation explaining:

  • Kerberos protocol behavior
  • RC4 fallback mechanisms
  • Microsoft enforcement timeline
  • Event monitoring strategy
  • Remediation guidance

English version:

Kerberos RC4 Hardening — EN-US

Portuguese version:

Kerberos RC4 Hardening — PT-BR

These documents include:

  • risk explanation
  • detection methodology
  • event analysis
  • remediation scenarios
  • operational guidance for large environments

PowerShell Scripts

Scripts provided in this repository are used to audit Kerberos encryption usage across Domain Controllers.

Official Microsoft reference scripts:

https://github.com/microsoft/Kerberos-Crypto/tree/main/scripts

Improved auditing script provided in this repository:

Get-KerbEncryptionUsage.ps1

Enhancements include:

  • improved readability and structure
  • better CSV export support
  • Power BI–friendly output
  • operational improvements for large environments

Script documentation:

scripts/README.md

[!NOTE] The improved script is based on the official Microsoft detection script and preserves its analytical logic while improving usability for operational environments.


Power BI Dashboard

The repository includes a Power BI dashboard designed to analyze Kerberos encryption usage.

Dashboard documentation:

dashboards/README.md

Dashboard file:

RC4-KerbEncryptionUsage-Dashboards.pbix

The dashboard allows security teams to:

  • identify RC4 usage scenarios
  • distinguish between Ticket and SessionKey encryption
  • identify legacy applications and service accounts
  • monitor RC4 reduction progress over time
  • support security readiness reporting

Kerberos Events Used for Detection

Kerberos auditing relies primarily on the following Security Event Log entries.

Event IDDescription
4768Kerberos authentication ticket request (AS)
4769Kerberos service ticket request (TGS)

Recent Windows updates also introduce diagnostic events for RC4 detection and enforcement.

Event IDDescription
201RC4 detected because the client advertises only RC4
202RC4 detected due to missing AES keys
203RC4 blocked (enforcement phase)
204RC4 blocked due to missing AES keys
205Explicit insecure encryption policy detected
206Client does not advertise AES
207Service configured for AES but account lacks AES keys
208RC4 blocked because service only accepts AES
209Kerberos encryption negotiation failures

[!NOTE] These events are introduced by security updates related to CVE-2026-20833 and are critical for identifying environments that still rely on RC4.


Official Microsoft References

Microsoft documentation and guidance related to Kerberos RC4 deprecation.

Detect and remediate RC4 usage in Kerberos
https://learn.microsoft.com/windows-server/security/kerberos/detect-remediate-rc4-kerberos

Kerberos RC4 KDC changes (KB5073381)
https://support.microsoft.com/en-gb/topic/how-to-manage-kerberos-kdc-usage-of-rc4-for-service-account-ticket-issuance-changes-related-to-cve-2026-20833-1ebcda33-720a-4da8-93c1-b0496e1910dc

Beyond RC4 for Windows authentication
https://www.microsoft.com/en-us/windows-server/blog/2025/12/03/beyond-rc4-for-windows-authentication/

AskDS — What is going on with RC4 in Kerberos?
https://techcommunity.microsoft.com/blog/askds/what-is-going-on-with-rc4-in-kerberos/4489365

AskDS — Preparing for AES enforcement in Kerberos
https://techcommunity.microsoft.com/blog/askds/so-you-think-you%E2%80%99re-ready-for-enforcing-aes-for-kerberos/4080124


Who This Repository Is For

This repository is designed for professionals responsible for identity infrastructure security:

  • Active Directory administrators
  • Security engineers
  • Identity architects
  • Blue team analysts
  • Security auditors
  • Microsoft infrastructure consultants

It provides guidance for environments preparing for the removal of RC4 from Kerberos authentication flows.


Disclaimer

[!CAUTION] This repository is provided for educational and operational guidance only.

Configuration changes such as modifying:

root@kitploit:~
msDS-SupportedEncryptionTypes

or disabling legacy encryption types should always be validated in a lab or staging environment before being applied to production systems.

Incorrect configuration may lead to Kerberos authentication failures or service outages.

Download Tool