Vulnerabilities & CVEs

2026 Exploit Kits: Office, Windows, Linux Vulnerabilities (Q

Exploit kits are evolving. Q1 2026 brought new ways to hit Microsoft Office, Windows, and Linux systems. Here's what you need to know.

Abstract depiction of interconnected code vulnerabilities and network pathways.

Key Takeaways

  • Exploit kits in Q1 2026 incorporated new exploits for Microsoft Office, Windows, and Linux.
  • Veteran vulnerabilities like CVE-2018-0802 and CVE-2017-11882 remain widely exploited.
  • Newer, complex vulnerabilities targeting system interactions are emerging, including bypasses and RCE flaws.

The coffee machine sputtered, spitting out lukewarm water into a chipped mug. Just another Tuesday.

Exploit kits. They’re like that annoying relative who always shows up uninvited, except instead of bad holiday sweaters, they bring zero-days and a payload. And in Q1 2026, these unwelcome guests got a fresh wardrobe. Threat actors are no longer just dabbling; they’re weaponizing new exploits for Microsoft Office, Windows, and the ever-popular Linux. This isn’t about minor annoyances; it’s about systems getting compromised. Again.

A Tide of Trouble: The Vulnerability Floodgates

Let’s talk numbers. CVEs are piling up faster than unpaid bills. The folks who track these things are seeing a relentless climb in registered vulnerabilities since January 2022. And don’t even get me started on the critical ones – those with a CVSS score over 8.9. While there’s a slight dip this year compared to the absolute chaos of last year’s web framework disclosures, the upward trend is as stubborn as a cheap suit. The usual suspects – React2Shell, mobile exploit frameworks, and the ever-present discovery of secondary bugs during patches – keep the pressure on.

“The current growth is driven by high-profile issues like React2Shell, the release of exploit frameworks for mobile platforms, and the uncovering of secondary vulnerabilities during the remediation of previously discovered ones.”

It’s a cycle. Fix one thing, break three others. We’ll see if Q2 brings any relief, but my money’s on more of the same. They say AI is going to help find bugs. Great. More bugs, faster.

Old Reliable, New Tricks: Exploitation in the Wild

But it’s not just about brand new flaws. The real misery often comes from those veteran vulnerabilities, the ones that have been kicking around for years. Think CVE-2018-0802 and CVE-2017-11882 – those old Equation Editor RCE bugs? Still potent. Or CVE-2017-0199, which let attackers waltz right into Microsoft Office. These aren’t relics; they’re workhorses for lazy attackers.

Then you’ve got the slightly newer, but still seasoned, players like CVE-2023-38831 and CVE-2025-6218, messing with archives and directory traversal. They’re the digital equivalent of a master lockpick. And let’s not forget CVE-2025-8088, a bypass vulnerability that lets files land wherever the attacker pleases. Nasty.

The New Kids on the Block (Who Are Just as Bad)

This quarter’s fresh hell comes from exploits that are more complex, often exploiting the messy interactions between different systems. They’re hard to pin down. We’re talking about CVE-2026-21509 and CVE-2026-21514. These are security feature bypasses. Protected View? Doesn’t matter. A crafted file can still run malicious code without you even knowing. Your user privileges are now their playground. Then there’s CVE-2026-21513, hitting the old Internet Explorer MSHTML engine. It bypasses rules meant to keep you safe from untrusted websites. And the kicker? An LNK file was the vector. An LNK file. Seriously.

These three, specifically, have been chained together in attacks against Windows. It’s an impressive bit of nastiness, but honestly, I suspect the whole chain is too unstable for widespread, long-term use. Expect these individual components to pop up in your next phishing campaign, though. It’s just easier that way.

Look at the numbers. The trend of Windows users encountering exploits, starting from Q1 2025, shows it’s a persistent problem.

These aren’t theoretical threats. They’re entry points. They’re privilege escalators. The only defense? Patching. Constantly. Like your life depends on it. Because, frankly, it might.

Linux’s Own Headache

Linux users aren’t getting off scot-free. Dirty Pipe (CVE-2022-0847) is still a favorite for escalating privileges and hijacking processes. And CVE-2019-13272, a buffer overflow in the setuid_coreutils package, is still a viable route for escalating privileges. The common theme? Escalate. Always escalate.

C2 Frameworks: The Backstage Crew

Popular Command and Control (C2) frameworks are also keeping pace. They’re incorporating new vulnerabilities, often to bypass security controls or maintain persistence. We’re seeing them adapt quickly, integrating these newer CVEs to ensure their malicious infrastructure remains effective. It’s a constant cat-and-mouse game, and right now, the cats are looking pretty agile. This isn’t a static threat landscape; it’s a dynamic, evolving ecosystem of compromise. And these frameworks are the connective tissue.

The Big Picture: Why Does This Even Matter?

This isn’t just about the latest CVEs. It’s about the evolution of attack vectors. Threat actors aren’t just grabbing whatever exploit is lying around; they’re building sophisticated chains, leveraging complex vulnerabilities, and ensuring they have multiple ways in. The rise of AI in vulnerability discovery might seem like a good thing, but it’s a double-edged sword, potentially arming both defenders and attackers with sharper tools. Expect this trend of increasingly complex and interconnected exploits to continue. The days of a single, simple exploit kit are probably numbered. We’re moving into an era of modular, adaptable attack platforms. And that, frankly, is terrifying.

**


🧬 Related Insights

Frequently Asked Questions**

What are exploit kits? Exploit kits are malicious software packages designed to automatically scan for and exploit vulnerabilities in a user’s system and software. They are used by threat actors to deliver malware, steal data, or gain unauthorized access.

Will patching stop these new vulnerabilities? Patching is the most critical defense against known vulnerabilities. However, exploit kits can target zero-day vulnerabilities (those not yet disclosed or patched), making patching alone insufficient. A layered security approach is essential.

Is AI making vulnerabilities worse? AI can be used to discover vulnerabilities more efficiently, which benefits security researchers. However, it can also be used by threat actors to find and exploit vulnerabilities faster, potentially increasing the threat landscape.

Maya Thompson
Written by

Threat intelligence reporter. Tracks CVEs, ransomware groups, and major breach investigations.

Frequently asked questions

What are exploit kits?
Exploit kits are malicious software packages designed to automatically scan for and exploit vulnerabilities in a user's system and software. They are used by threat actors to deliver malware, steal data, or gain unauthorized access.
Will patching stop these new vulnerabilities?
Patching is the most critical defense against known vulnerabilities. However, exploit kits can target zero-day vulnerabilities (those not yet disclosed or patched), making patching alone insufficient. A layered security approach is essential.
Is AI making vulnerabilities worse?
AI can be used to discover vulnerabilities more efficiently, which benefits security researchers. However, it can also be used by threat actors to find and exploit vulnerabilities faster, potentially increasing the threat landscape.

Worth sharing?

Get the best Cybersecurity stories of the week in your inbox — no noise, no spam.

Originally reported by Securelist (Kaspersky)

Stay in the loop

The week's most important stories from Threat Digest, delivered once a week.