CVE-2025-59284 is an information disclosure vulnerability in Windows NTLM caused by exposure of sensitive information to an unauthorized actor. The issue allows unauthorized local spoofing by enabling an attacker to access NTLM-related sensitive information that should not be exposed. Specific vulnerable functions, code paths, and affected Windows versions are not available from the provided information.
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.
This repository is a minimal proof-of-concept for CVE-2025-59284 targeting libarchive. It contains only two files: a short README with usage instructions and one Python script, poc.py, which is the sole exploit implementation. The script does not exploit a service directly; instead, it generates a malicious TAR archive intended to be consumed later by a vulnerable application or workflow using libarchive. The exploit capability is archive crafting. Specifically, poc.py manually builds a 512-byte TAR header, sets the TAR typeflag to '1' to indicate a hardlink entry, places a user-controlled value in the filename field, and places a user-controlled target path in the linkname field. It then computes a valid TAR checksum and writes the header plus the required two zero blocks to produce a syntactically valid TAR file. The README example shows the intended abuse case: embedding a UNC path such as \\IP\Share\test.pdf as the hardlink target, suggesting the PoC is meant to coerce a vulnerable libarchive consumer into resolving or interacting with a remote SMB share. Repository structure is extremely small and straightforward: README.md documents the CVE claim and command-line usage, while poc.py is a standalone Python entry point. There is no framework integration, no shellcode, no post-exploitation logic, and no detection functionality. The code is best classified as a POC rather than an operational exploit because it only creates the malicious archive artifact and leaves triggering and any downstream impact to the vulnerable target environment.
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.
9 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.