Metasploit Adds 13 Modules, Led by the Fragnesia Linux Kernel LPE (CVE-2026-46300)

Rapid7 shipped 13 new Metasploit Framework modules on August 14, 2026, and for defenders the release reads less like a changelog than a patch-priority list. The headline entry is the Fragnesia Linux kernel local privilege-escalation exploit (CVE-2026-46300), and it arrives alongside remote code execution modules for a stack of widely deployed web software: WordPress core, the Pix for WooCommerce plugin, Ghost CMS, Joomla Content Editor (JCE), Langflow, OpenCATS, Pterodactyl Panel, and SonicWall SMA1000, plus an auxiliary path-traversal module for Ray Dashboard.

The practical point is blunt. Every product named in this release now has a public, ready-to-run exploit module behind it, which lowers the skill and effort needed to attack an unpatched instance. In Rapid7's own wrap-up, the Metasploit team put it plainly: "This wrap-up brings a full-on shell parade. Thirteen shiny new modules landed, starting with a buffet of RCEs." If you run any of these products, this week's task is to confirm you are on a fixed version, prioritizing anything reachable from the internet and the Fragnesia kernel bug.

What Actually Shipped

The "13 modules" number covers three categories, and it helps to separate them. Ten are offensive modules tied to a specific product or CVE. The other three are tooling: a new MALLEABLEC2 option that lets Meterpreter HTTP(S) payloads reshape their traffic, and two Windows-on-ARM (AArch64) reverse-TCP shell payloads. The defender-relevant list is the ten, and one of them is not an RCE at all: the Ray Dashboard module is an auxiliary path-traversal that lists local directory contents, and Rapid7 notes it has no CVE assigned yet (issuance is pending with MITRE). Worth correcting up front, because several early summaries lumped it in as an RCE.

Here is the offensive set, mapped to the CVE and the version detail a defender needs to check patch status. Details are drawn from Rapid7's per-module writeups.

A few entries deserve a second look. The WP2Shell module targets WordPress core, not a plugin, chaining a REST API route-confusion flaw (CVE-2026-63030) with an SQL injection (CVE-2026-60137) into pre-auth RCE against core versions 6.9.0 through 6.9.4 and 7.0.0 through 7.0.1. Given how much of the web runs on WordPress, that is the entry with the widest blast radius. The Langflow module, meanwhile, hits the same open-source agentic-AI platform whose earlier RCE (CVE-2026-9198) CISA added to its Known Exploited Vulnerabilities catalog this month; CVE-2026-33017 is a distinct pre-1.9.0 bug, but the pattern of internet-exposed Langflow instances is now well established. And the SonicWall SMA1000 module exploits CVE-2026-15409, the CVSS 10.0 SSRF that we detailed when the SMA 1000 zero-days first surfaced.

Fragnesia: A Kernel Bug Born From a Patch

Fragnesia (CVE-2026-46300) is the entry that changes the math for Linux operators. Rapid7 describes the module as targeting "a page-cache replacement vulnerability in the Linux kernel's XFRM (IPsec) subsystem," and it runs as a local exploit: an unprivileged user already on the box uses it to escalate to root. Multiple trackers, including TuxCare and Tenable, place it in the ESP-in-TCP path of that subsystem, where a bookkeeping failure lets an attacker corrupt the kernel page cache of read-only files and turn that into root.

The brief that reached our desk flagged an open question: is Fragnesia genuinely distinct from earlier Linux kernel LPEs, or a rebrand of one? The live reporting resolves it. Per Help Net Security, Fragnesia is a new bug in the "Dirty Frag" family that was spawned by the patch for the original Dirty Frag flaw, a regression introduced while fixing its predecessor. So it is its own CVE with its own fix, not a duplicate. That distinction matters operationally: applying the earlier Dirty Frag patch is exactly what could have left a system exposed to this one, so "we already patched that" is not a safe assumption here.

What Defenders Should Verify

Treat the module list as a scoped inventory query, not a reason to panic. The work is verification, and it is finite.

• WordPress core. Confirm core is off the affected 6.9.0 through 6.9.4 and 7.0.0 through 7.0.1 ranges. This is the highest-reach item because it hits core rather than an add-on, and WP2Shell needs no authentication.
• Langflow. Confirm 1.9.0 or later, and check that no instance is exposed to the internet with default or disabled authentication. Langflow has been targeted repeatedly through 2026.
• SonicWall SMA1000. Apply the vendor fix for CVE-2026-15409 and confirm the WorkPlace service is not reachable from untrusted networks.
• Joomla JCE. Any JCE build at or below 2.9.99.4 is in scope for an unauthenticated file-upload RCE. Update the extension and confirm the temp directory is not directly web-accessible.
• Pterodactyl Panel, OpenCATS, Ghost CMS, Pix for WooCommerce. Update each to its patched release. Ghost's module needs valid admin or staff credentials, so it is lower urgency than the unauthenticated entries, but credential reuse makes that a thin line.
• Ray Dashboard. No CVE yet, but the auxiliary module reads local directories through path traversal. Restrict dashboard exposure and watch for a vendor advisory.
• Linux kernel (Fragnesia). Patch CVE-2026-46300 across the fleet, prioritizing multi-tenant and shared-hosting boxes where untrusted local users already have a shell.

My Read

My read: the kernel bug is the sleeper, and shipping it in the same release as eight web RCEs is the part worth sitting with. Internet-facing RCEs draw attention and tend to get patched under pressure. A local privilege-escalation like Fragnesia is the quiet second stage: it is exactly what turns the low-privilege web shell one of these other modules just handed an attacker into full root on the host. The two halves of that chain now live in the same framework, one download apart. If I had to sequence this, I would confirm patch status on the unauthenticated, internet-reachable web apps today (WordPress core and Langflow at the top), then move the Fragnesia kernel patch to the front of the queue on any Linux system where local users are a normal part of the design, Pterodactyl game-hosting nodes and shared hosting especially. That is where a web foothold plus a kernel LPE compounds into a full compromise fastest.

None of this is novel attacker capability in the abstract. What changed on August 14 is availability: reliable, packaged exploitation for a specific, named list of products, which is the moment the exposure math shifts for anyone still running an old build. The parallel is the same one we saw when a public root exploit landed for a one-character Linux kernel flaw: the bug was known, but the public tool is what widened the field of who could use it.

Primary Documents

• Rapid7: Metasploit Wrap-Up, Lot of Summer Shells and Fit HTTP Profiles (Aug 14, 2026)
• Rapid7: Metasploit Framework 6.5 Released
• Help Net Security: Fragnesia (CVE-2026-46300), a New Linux Kernel LPE Spawned by the Dirty Frag Patch
• Tenable: CVE-2026-46300 (Fragnesia), Linux Kernel ESP-in-TCP LPE FAQ