Loading vulnerability…
CVE-2025-53136 is an information disclosure vulnerability in the Windows NT OS Kernel. The flaw allows exposure of sensitive information to an unauthorized actor when exploited by an authorized local attacker. Based on the available information, the issue resides in kernel-level functionality within Windows and results in unintended disclosure of protected information rather than direct code execution. Specific vulnerable functions, affected code paths, and precise triggering conditions are not currently available.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a small Windows local proof-of-concept for a claimed NT kernel information disclosure via a race condition (README labels it CVE-2025-53136, and links to MSRC CVE-2024-43511 plus a third-party writeup). Structure: - README.md: brief description and external references. - build.bat: builds main.c with MSVC cl.exe. - main.c: the PoC. Exploit logic (main.c): - Opens a handle to the current process token with TOKEN_QUERY (OpenProcessToken). - Allocates a single shared 0x1000-byte buffer via VirtualAlloc with PAGE_READWRITE | PAGE_NOCACHE. - Spawns 2*N threads where N = number of processors: - TokenThread: repeatedly calls NtQueryInformationToken(hToken, TokenAccessInformation, shared_buffer, 0x1000, &cbNeeded) while trimming the process working set (EmptyWorkingSet) to increase timing variability. - RacingThread: repeatedly trims working set and reads an 8-byte value at offset +96 from the shared buffer, treating it as a pointer to _SID_AND_ATTRIBUTES. If the value falls in a canonical kernel address range (> 0x0000800000000000), it assumes a kernel pointer leak occurred. - On success, it prints a derived "_TOKEN address" as (leaked_value - 0x490), implying a hardcoded structure offset from the leaked field to the base of the kernel _TOKEN object. - Runs up to 60 seconds (WaitForMultipleObjects on the racing threads) and then terminates threads. Capabilities and intent: - Provides a kernel pointer leak / KASLR bypass primitive by racing token access information queries and reading inconsistent/partially-updated data from a shared user buffer. - No network activity, no shellcode, no privilege escalation chain included; output is a single leaked address printed to stdout. Notable implementation details: - Uses undocumented/NT API NtQueryInformationToken (declared manually) with TokenAccessInformation. - Uses CPU affinity and high thread priority to increase race reliability. - Hardcoded offsets: reads at +0x60 (96) and subtracts 0x490 to estimate _TOKEN base; these are version-dependent and may not be reliable across Windows builds.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
35 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.