Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
checkmk_broccoli2shell — Checkmk extension that audits Linux hosts for Brotli decoders (libbrotlidec, Node.js, Python, .NET) affected by CVE-2026-111497, checking versions, backports and stale processes. | Kitploit
Tools/GitLabGitLab/checkmk1/checkmk_broccoli2shell
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingIncident Response
GitLabcheckmk1/checkmk_broccoli2shell

checkmk_broccoli2shell

Checkmk extension that audits Linux hosts for Brotli decoders (libbrotlidec, Node.js, Python, .NET) affected by CVE-2026-111497, checking versions, backports and stale processes.

Share
View Repository
315 days agoNot yet reviewed

checkmk_broccoli2shell

A Checkmk extension that shows, for every Brotli decoder on a Linux host, whether it is affected by Broccoli2Shell - CVE-2026-111497, an out-of-bounds write in Google's C Brotli decoder that can lead to remote code execution when a program decompresses Brotli data from an untrusted source (an HTTP response, a request body, an archive). It was disclosed on 2026-10-21/22 and fixed in Brotli 1.0.10, 1.1.1 and 1.2.1, Node.js 22.23.4, 24.22.1 and 26.12.1, the Python packages Brotli 1.2.1 and brotlicffi 1.2.1.0, and .NET 8.0.33, 9.0.22 and 10.0.14.

Also known as Node2Shell (the most common name, since Node.js disclosed it, e.g. at Akamai, Red Hat and CISA), Brotli2Shell (Tenable) and HTTP2Shell. The name Broccoli2Shell goes back to a joke by the researcher Juliano Rizzo - "Node2Shell is a terrible name. I call it Broccoli" - a play on Brotli, and spread from there.

It ships a small POSIX shell agent plug-in that only collects facts (the system library libbrotlidec, Node.js binaries, Python Brotli and brotlicffi installations, .NET runtimes, their versions, package changelogs, what they are linked against, which processes have them loaded and which still run a replaced one). Whether that means "fixed" or "vulnerable" is decided by the check plug-in on the Checkmk server, so new information - another fixed release - only needs an updated .mkp, not a new script on every host.

Optionally, per host, the same plug-in also checks the running Docker and Podman containers from inside - with docker exec, as the container's own user, by default every six hours, leaving out containers whose names match your regular expressions - and lists their findings in one service per host, judged exactly like the host's own decoders. The Checkmk agent does not need to be installed in the containers.

Why not just compare version numbers: distributions backport the fix without changing the upstream version, and they build Node.js against the system library instead of the copy Node.js bundles. Debian 12 ships libbrotli 1.0.9 and Node.js 18.20.4 (end of life upstream, no fix) - both fixed, because the updated libbrotli1 package is the decoder that Node.js runs. The extension therefore reads the changelog of the package that owns each decoder, and follows Node.js and Python extensions to the library they are linked against. Minimal container images often drop /usr/share/doc, so there is no changelog to read; for the system library the check then falls back to the package versions known to carry the fix (Debian 12/13, Ubuntu 24.04, RHEL/AlmaLinux 8/9, and later updates of the same release).

Requirements

  • Checkmk >= 2.4.0 (using the current cmk_addons.plugins plugin API).
  • Monitored hosts: Linux with the Checkmk agent running as root (the plug-in reads the binaries and /proc/<pid>/maps of all processes). Plain POSIX sh with GNU or busybox tools; package changelogs are read with dpkg, rpm or apk. Tested on the Debian family, the Red Hat family, Amazon Linux and Alpine, see below.
  • Containers: the docker or podman command on the host; inside a container only a POSIX sh and the usual tools of the image. No Checkmk agent in the container.
  • Agent bakery deployment requires a commercial Checkmk edition (Pro, Ultimate, or Ultimate with multi-tenancy). On the Community edition, copy the agent plug-in to the hosts by hand, see Manual agent plug-in deployment. The check plug-ins, rules and services work identically either way.

Tested with

Checkmk imageDateResult
checkmk/check-mk-cloud:2.4.0p392026-11-02OK (1.2.5: build, cmk-validate-plugins, smoke test)
checkmk/check-mk-ultimate:2.5.0p182026-11-02OK (1.2.5: build, cmk-validate-plugins, smoke test)
checkmk/check-mk-ultimate:3.0.0-2026.11.02 (daily)2026-11-02OK (1.2.5: build, cmk-validate-plugins, smoke test)

The container scan (scripts/test_container_scan.sh, incl. a BusyBox without applet links) passed on 2026-11-02.

The agent plug-in was run against the distributions' own packages and the official images on 2026-10-28 (scripts/test_agent_plugin.sh), with a node and a python process that had the decoder loaded. Afterwards the library, the node binary and the Python extension modules were replaced on disk, and the restart detection reported the running processes. The container mode was run on a Docker host on 2026-10-30 (scripts/test_container_scan.sh) against containers with vulnerable and fixed decoders, as root and as an unprivileged user, without a shell, hostile and hanging. On 2026-10-31 again, with piggyback hosts (combined): one per checked container, none for excluded, shell-less or hanging ones. Podman was not tested: its ps and exec take the same arguments, but no Podman host was at hand.

Distributions

DistributionDecodersPlug-in result
Debian 12libbrotli 1.0.9-2+deb12u1, Node.js 18.20.4 (linked), python3-brotlifixed by backport (changelog), Node.js through the library
Debian 13libbrotli 1.1.0-2+deb13u1, Node.js 20.19.2 (linked), python3-brotli, python3-brotlicffi (linked)fixed by backport, Node.js and brotlicffi through the library
Ubuntu 24.04libbrotli 1.1.0-2ubuntu0.1, Node.js 18.19.1 (linked), python3-brotli, dotnet-runtime-8.0 8.0.32fixed by backport - .NET vulnerable (8.0.33 not yet in the archive)
AlmaLinux 8.10libbrotli 1.0.6-5.el8_10, Node.js 10.24.0 (own decoder), python3-brotlilibrary and Brotli fixed by backport - Node.js 10 vulnerable (end of life, own decoder)
AlmaLinux 9.8libbrotli 1.0.9-10.el9_8.1, Node.js 16.20.2 (linked), python3-brotli, dotnet-runtime-8.0 8.0.32fixed by backport - .NET vulnerable
AlmaLinux 10.2libbrotli 1.1.0-8.el10_2.1, Node.js 22.23.2 (linked), python3-brotlifixed by backport
Fedora 44libbrotli 1.2.1, Node.js 22.23.1 (linked), python3-brotli 1.2.1fixed by version
Amazon Linux 2023libbrotli 1.1.0-1.amzn2023.0.1, Node.js 18.20.8 (linked)vulnerable - no fixed package yet, Node.js through the library
Alpine 3.22brotli-libs 1.1.1, Node.js 22.23.4 (linked), py3-brotli 1.1.1fixed by version

Official images and PyPI

ImageDecodersPlug-in result
node:24.22.0-slimNode.js 24.22.0 (own decoder)vulnerable
node:24.22.1-slimNode.js 24.22.1 (own decoder)fixed by version
node:20-alpineNode.js 20.20.2 (own decoder)vulnerable - end of life, no fix
node:24.22.0-slim, binary moved to /home/dev/.nvm/... (owned by a user)Node.js 24.22.0vulnerable - version read from the binary, not run
python:3.12-slim + pip install Brotli==1.2.0 brotlicffi==1.2.0.0, venv with Brotli 1.1.0 in /srv/app/venvBrotli, brotlicffi (own decoders)vulnerable (the venv found through its running process)
python:3.12-slim + current PyPIBrotli 1.2.1, brotlicffi 1.2.1.0fixed by version
mcr.microsoft.com/dotnet/runtime:8.0.32 / :8.0.NET 8.0.32 / 8.0.33vulnerable / fixed by version

The Checkmk site itself (2.5.0p17) ships no Brotli package in its Python. The plug-in has not yet run on a production host outside containers - in particular not with SELinux enforcing (RHEL family); the agent normally runs unconfined there.

Installation

  1. Download the .mkp from a release (or build it yourself, see Development).

  2. Setup > Maintenance > Extension packages > Upload package, or on the command line inside the site:

    mkp add broccoli2shell-<version>.mkp
    mkp enable broccoli2shell <version>
    
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    891
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    547
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    369
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    366
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    309
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    282

Explore all tools

Browse our collection of tools

View all tools →