Offensive Security released Kali Linux 2026.1 on 24 March 2026, the first Kali release of the year. It adds eight tools to the repositories, moves to Linux kernel 6.18, refreshes the theme and adds a BackTrack mode to kali-undercover. For developers who use Kali for app-security testing, the new tools worth trying are SSTImap, XSStrike, WPProbe and an MCP server for Metasploit.
What happened
The 2026.1 changelog lists 25 new packages, 9 removed and 183 updated, with the kernel bumped to 6.18. The eight headline tools added to the network repositories are:
- AdaptixC2: an extensible post-exploitation and adversary-emulation framework.
- Atomic-Operator: runs Atomic Red Team tests across operating systems.
- Fluxion: a security-auditing and social-engineering research tool.
- GEF: an enhanced GDB interface for exploit development and debugging.
- MetasploitMCP: an MCP server that exposes Metasploit to MCP-capable AI clients.
- SSTImap: automatic server-side template injection detection with an interactive interface.
- WPProbe: fast WordPress plugin enumeration.
- XSStrike: an advanced cross-site scripting scanner.
The yearly theme refresh covers the boot menu, installer, login screen, desktop and wallpapers, and Kali Purple gets a 2026 desktop too. To mark 20 years since BackTrack, Kali's predecessor, kali-undercover --backtrack switches the desktop to a BackTrack 5 look. Run it again to switch back. NetHunter received app fixes, a new Android 16 kernel for the Redmi Note 8, a Nexmon patch for the Samsung S10 series, and a first working injection patch for Qualcomm QCACLD-3.0 Wi-Fi.
Who is affected
- Existing Kali users on the rolling branch, who get everything through a normal upgrade.
- SDR users: Kali lists a known issue where the
kali-tools-sdrmetapackage conflicts with the GNU Radio ecosystem, andgr-air-modesandgqrx-sdrare broken in this release. - AppSec and QA engineers who use Kali images in CI or VMs for dynamic testing.
What it means for developers and engineering teams
Several of the new tools map directly onto common web-app bugs. SSTImap probes for template injection in engines such as Jinja2, Twig and Freemarker, the class of bug where user input ends up inside a template and becomes code execution. XSStrike goes beyond simple payload lists by analysing how and where your app reflects input. WPProbe enumerates plugins quickly, and on WordPress sites outdated plugins are where most real compromises start. Running these against your own staging environment before an attacker runs them against production is a cheap win.
MetasploitMCP is the more notable signal. It lets an AI assistant drive Metasploit through the Model Context Protocol, and Kali's own blog has covered pairing Kali with LLM clients. That can speed up authorised testing, but it also means an AI agent with tool access can launch real exploits. Treat MCP servers like that as privileged tooling: scope the targets, log every call and never connect them to an agent that also reads untrusted content.
What to do now
- Upgrade an existing install:
sudo apt update && sudo apt -y full-upgrade cp -vrbi /etc/skel/. ~/ [ -f /var/run/reboot-required ] && sudo reboot -f - Verify the release:
grep VERSION /etc/os-releaseshould show2026.1anduname -ra 6.18.x kernel. - Install the tools you need:
sudo apt install sstimap xsstrike wpprobe gef(package names as listed in Kali's tool index). - Add SSTI and XSS checks to staging tests. Point SSTImap and XSStrike only at environments you own or are authorised to test.
- Hold off on SDR upgrades if you depend on
gqrx-sdrorgr-air-modesuntil Kali ships the promised fix. - Govern MCP tooling. If you try MetasploitMCP, run it in an isolated lab network and require human approval for exploit execution.
Related on TechLogHub
- XSS: the bug class XSStrike hunts
- MCP vs REST API: how the Model Context Protocol exposes tools to AI clients
- MCP stdio vs Streamable HTTP: transport choices for MCP servers like MetasploitMCP