Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2025-1055: Missing authorization in K7 Security Anti-Malware driver permits privileged process termination

Published Jun 10, 2025 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS5.6Medium · v3.1
EPSS0.24%15th percentile
CISA KEVNoNot listed
In the wildReported13 exploitation records in Mallory
IdentifiersCVE-2025-1055CWE-862 · Missing Authorization

CVE-2025-1055 is a missing-authorization vulnerability in the K7RKScan kernel driver included with K7 Security Anti-Malware versions before 23.0.0.10. Its IOCTL handler allows a local low-privilege user to submit crafted requests that terminate processes running with administrative or SYSTEM privileges, except processes inherently protected by the operating system. Exploitation can disrupt critical services and disable endpoint security software. Longlegs and DragonForce ransomware operators have abused the vulnerable signed driver in bring-your-own-vulnerable-driver attacks.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises availability by allowing unauthorized termination of privileged applications and services. Terminating antivirus or EDR processes can impair protection and visibility, facilitating subsequent ransomware deployment. The demonstrated capability is privileged process termination; arbitrary kernel code execution or unrestricted SYSTEM-level execution is not established.

Mitigation

If you can’t patch tonight, do this now.

Use application-control or driver-blocking policies to prevent vulnerable K7RKScan driver versions from loading, including copies introduced independently of the installed K7 product. Restrict driver installation and loading to authorized administrators. Monitor unexpected kernel-driver loads and coordinated termination of security processes as potential BYOVD activity.

Remediation

Patch, then assume compromise.

Upgrade K7 Security Anti-Malware to version 23.0.0.10 or later. Verify that the vulnerable driver is no longer loaded or available for reuse; updating the installed product alone does not prevent an attacker from introducing an older vulnerable driver.

Public exploits

Exploits

2 exploits validated by Mallory's analysis.

View more in app →
BYOVDThis repository is a collection of operational Proof-of-Concept (PoC) exploits demonstrating the Bring Your Own Vulnerable Driver (BYOVD) technique to kill protected processes on Windows systems. Each subdirectory targets a specific vulnerable driver, with a Rust-based executable that loads the driver as a service, opens a device handle, and sends a crafted IOCTL to terminate a process by name or PID. The exploits require the vulnerable driver file to be present in the same directory as the executable and are designed for local execution with administrative privileges. The repository covers multiple drivers, including those from Baidu Antivirus (BdApiUtil64.sys, CVE-2024-51324), K7 Ultimate Security (K7RKScan.sys, CVE-2025-52915, CVE-2025-1055), ThreatFire System Monitor (sysmon.sys), Tg Soft (viragt64.sys), and Topaz Antifraud (wsftprm.sys, CVE-2023-52271). The main entry points are the Rust 'main.rs' files in each subdirectory. The exploits are not detection scripts but provide real process termination capability, which can be used to disable AV/EDR or other security software. The code is well-structured, modular, and leverages Windows service and device APIs to interact with the drivers. The attack vector is local, requiring administrative access to load the driver. The endpoints include the driver files and their respective device interfaces (e.g., \\.\BdApiUtil, \\.\ksapi64_dev, etc.). This collection is intended for research and educational purposes to demonstrate the risks of unprotected or vulnerable kernel drivers on Windows platforms.BlackSnufkin · Disclosed Dec 5, 2023 · rust · localPoCCVE-2025-1055-pocThis repository is a proof-of-concept (PoC) exploit for CVE-2025-1055 and CVE-2025-52915, targeting the K7RKScan.sys Windows kernel driver (version 1516). The exploit consists of a C program (exploit.c) and a README.md with usage instructions. The exploit works by opening a handle to the vulnerable driver (\\.\DosK7RKScnDrv) and repeatedly sending the PID of the Windows Defender process (MsMpEng.exe) via the 0x222018 IOCTL, causing the driver to terminate the process. The README provides instructions for installing the driver and running the exploit. The attack vector is local, requiring the attacker to have the ability to load the vulnerable driver and execute the exploit on the target system. The main fingerprintable endpoints are the device path for the driver, the path to the driver file, and the target process name.diego-tella · Disclosed Sep 4, 2025 · c · localPoC
FAQ

Frequently asked questions

Is CVE-2025-1055 exploited in the wild?
Yes. As of Nov 6, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2025-1055?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-1055, the earliest disclosed Dec 5, 2023.
Is there a patch for CVE-2025-1055?
Upgrade K7 Security Anti-Malware to version 23.0.0.10 or later. Verify that the vulnerable driver is no longer loaded or available for reuse; updating the installed product alone does not prevent an attacker from introducing an older vulnerable driver.
How severe is CVE-2025-1055?
CVE-2025-1055 has a CVSS v3.1 score of 5.6 (Medium) and an EPSS score of 0.24% (15th percentile) as of Nov 6, 2026.
Activity feed

Recent activity

21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
malware newsNews · Nov 6, 2026October 2026 CVE Landscape - Malware Analysis - Malware Analysis, News and IndicatorsA K7 Security Anti-Malware vulnerability reported as actively exploited in October 2026.Read more ↗recordedfutureNews · Nov 6, 2026October 2026 CVE LandscapeA K7 Anti-Malware vulnerability exploited by Longlegs through the signed K7RKScan driver to terminate protected security processes. The content explicitly separates this activity from the SharePoint exploitation campaign.Read more ↗polyswarmNews · Oct 9, 2026China Linked Warlock Ransomware Campaign Targets Critical InfrastructureA vulnerability associated with the signed K7RKScan driver that Longlegs abuses in bring-your-own-vulnerable-driver attacks to terminate protected security processes before deploying ransomware. Its use was observed in other recent Longlegs attacks, not confirmed in the detailed critical infrastructure intrusion.Read more ↗mkd cirtNews · Oct 5, 2026Warlock ги искористува ранливостите во SharePoint за оневозможување на безбедносните алатки и инсталирање ransomware | MKD-CIRT | Национален центар за одговор на компјутерски инцидентиA vulnerability in the K7RKScan.sys driver abused during Warlock's ransomware attacks to disable security software through BYOVD. The content also links prior abuse of the vulnerable driver to DragonForce, but does not describe the underlying technical flaw.Read more ↗
+10 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence19Every report linking this CVE to a named adversary.
Associated malware17Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.