io.github.26zl/cybersec-toolkit
OCI · GHCR.IO/26ZL/CYBERSEC-TOOLKIT
Authorization-gated MCP server to discover and run 670+ security tools for CTF, pentest, and DFIR.
Available components
Last scanned (19 hours ago)
Scores higher than 0% of OCI servers
Category Security
Recent critical change
CVE-2026-114616 affects this package (31 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to 26zl/cybersec-toolkit). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- CVE-2026-114616 affects this package: high ▼ critical
- CVE-2026-114615 affects this package: high ▼ critical
- 30 Oct 26 0
- CVE-2026-111497 affects this package: high ▼ critical
- 28 Oct 26 0
- CVE-2026-96760 affects this package: high ▼ critical
- 21 Oct 26 −20
- GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
- Score status: scored → failed ▼ critical
- Known CVEs: CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. critical
- CVE-2026-95210 no longer affects this package ▲ security
- CVE-2026-88647 no longer affects this package ▲ security
- 15 Oct 26 20
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed oci/ghcr.io/26zl/cybersec-toolkit@1.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | 26zl/cybersec-toolkit |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/26zl/cybersec-toolkit/.github/workflows/publish-image.yml@refs/tags/v1.4.0 |
| Rekor log index | 3268332796 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:6a96c18ccbafdb922cebd95b854ed15279c47eb9927b3ae09374098ae737ae06 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 124 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-6v38-4h7w-rj9h | CVE-2026-96760 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-7vr2-2fgp-9w7p | CVE-2026-114615 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-8m4g-j4wp-wgcg | CVE-2026-114616 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-c5mf-xmp2-59rc | CVE-2026-114617 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N | yes |
| GHSA-c73q-w75p-j82v | CVE-2026-116672 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-fch4-3c6x-j4gc | CVE-2026-114618 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-q686-2qmg-hqc7 | CVE-2026-114619 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N | yes |
| GHSA-x4rv-c3wx-4cr8 | CVE-2026-114620 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N | yes |
| PYSEC-2026-4355 | CVE-2026-114615 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| PYSEC-2026-4356 | CVE-2026-114616 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N | yes |
| PYSEC-2026-4357 | CVE-2026-114617 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N | yes |
| PYSEC-2026-4358 | CVE-2026-114618 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| PYSEC-2026-4359 | CVE-2026-114619 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N | yes |
| PYSEC-2026-4360 | CVE-2026-114620 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N | yes |
| UBUNTU-CVE-2026-76642 | CVE-2026-76642 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| UBUNTU-CVE-2026-78408 | CVE-2026-78408 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:H/A:H | no |
| UBUNTU-CVE-2026-78409 | CVE-2026-78409 | high | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| UBUNTU-CVE-2026-78410 | CVE-2026-78410 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| USN-8944-1 | none | yes | ||
| GHSA-6q48-6c7w-9gw2 | critical | yes | ||
| PYSEC-2026-4320 | none | yes | ||
| RUSTSEC-2026-0385 | none | yes | ||
| UBUNTU-CVE-2026-102473 | CVE-2026-102473 | medium | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-102474 | CVE-2026-102474 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | no |
| RUSTSEC-2026-0221 | none | yes | ||
| GHSA-7xgj-8392-5q4r | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes | |
| UBUNTU-CVE-2024-52005 | CVE-2024-52005 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H | no |
| UBUNTU-CVE-2026-105712 | CVE-2026-105712 | low | CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L | no |
| UBUNTU-CVE-2026-118131 | CVE-2026-118131 | none | no | |
| RUSTSEC-2026-0258 | none | yes | ||
| GHSA-9pg5-8c7x-5hfx | CVE-2026-119284 | medium | yes | |
| UBUNTU-CVE-2026-54369 | CVE-2026-54369 | high | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N | no |
| UBUNTU-CVE-2026-54370 | CVE-2026-54370 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | no |
| UBUNTU-CVE-2026-111497 | CVE-2026-111497 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| USN-8956-1 | CVE-2026-111497 | none | yes | |
| UBUNTU-CVE-2026-18374 | CVE-2026-18374 | medium | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L | no |
| UBUNTU-CVE-2026-84243 | CVE-2026-84243 | high | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H | no |
| UBUNTU-CVE-2026-8674 | CVE-2026-8674 | medium | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-86805 | CVE-2026-86805 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L | no |
| UBUNTU-CVE-2026-89092 | CVE-2026-89092 | medium | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L | no |
| UBUNTU-CVE-2026-95818 | CVE-2026-95818 | low | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N | no |
| UBUNTU-CVE-2026-97399 | CVE-2026-97399 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | no |
| UBUNTU-CVE-2025-66382 | CVE-2025-66382 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-102633 | CVE-2026-102633 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-113351 | CVE-2026-113351 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-115506 | CVE-2026-115506 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-117610 | CVE-2026-117610 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| UBUNTU-CVE-2026-118370 | CVE-2026-118370 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H | no |
| UBUNTU-CVE-2026-77214 | CVE-2026-77214 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L | no |
| UBUNTU-CVE-2026-93990 | CVE-2026-93990 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | no |
Showing 50 of 124 vulnerabilities.
Background: What a vulnerability scan can and cannot prove →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the io.github.26zl/cybersec-toolkit MCP server?
io.github.26zl/cybersec-toolkit runs locally as a container image, launched with docker run --rm -i -e CYBERSEC_MCP_ALLOW_EXTERNAL -e CYBERSEC_MCP_ALLOW_SCRIPTS ghcr.io/26zl/cybersec-toolkit:1.4.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/26zl/cybersec-toolkit
claude mcp add 26zl-cybersec-toolkit -- docker run --rm -i -e CYBERSEC_MCP_ALLOW_EXTERNAL -e CYBERSEC_MCP_ALLOW_SCRIPTS ghcr.io/26zl/cybersec-toolkit:1.4.0
This image reads CYBERSEC_MCP_ALLOW_EXTERNAL and CYBERSEC_MCP_ALLOW_SCRIPTS. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the io.github.26zl/cybersec-toolkit MCP server?
io.github.26zl/cybersec-toolkit is an MCP server listed in the public MCP registry as io.github.26zl/cybersec-toolkit. Authorization-gated MCP server to discover and run 670+ security tools for CTF, pentest, and DFIR. This page covers its container image (ghcr.io/26zl/cybersec-toolkit).
Is the io.github.26zl/cybersec-toolkit MCP server still maintained?
io.github.26zl/cybersec-toolkit is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.26zl/cybersec-toolkit MCP server under?
io.github.26zl/cybersec-toolkit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.