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
vulnerpocalypse-containment — Open-source vulnerability analysis, CVE tracking, patch verification, and temporary security containment tools | Kitploit
Tools/GitHubGitHub/clearhandreview/vulnerpocalypse-containment
Defensive ToolsVulnerability ScannersVulnerability AnalysisConfiguration AuditingInformation GatheringMisconfigurationIncident ResponseCurated Resources

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
GitHubclearhandreview/vulnerpocalypse-containment

vulnerpocalypse-containment

Open-source vulnerability analysis, CVE tracking, patch verification, and temporary security containment tools

View Repository
11611h 59m agoNot yet reviewed
Share

Vulnerpocalypse Containment — cross-platform security-update evidence toolkit

Offline tests

Maintained catalog, not a universal zero-day patcher. This project tracks publicly disclosed security fixes linked to Anthropic/Claude research and separately sourced October 2026 vendor advisories. It contains an attributed original Linux upstream patch for CVE-2026-98432, vendor update references for proprietary or signed products, a cross-platform read-only version-floor checker, and an optional Linux-only temporary runtime control with explicit rollback.

No arbitrary kernel or binary modification, no automatic patch downloads, no exploitation tests, and no claim that every OS or every Anthropic finding is covered. Optional, explicitly approved Linux runtime MPTCP containment is the only executable change introduced by this toolkit. If no verified vendor fix or supported release exists, the correct result is unknown / manual review, never “patched.”

Start here — choose your operating system

For the simplest instructions, open Easy install. Pick your device and follow its numbered steps. You do not need to install Python on a phone. On computers, Python 3.11–3.15 is needed only to run this repository's optional offline checking tools.

DeviceQuickest safe stepOptional containment
WindowsSettings → Windows Update → Check for updates → RestartHTTP.sys HTTP/3 exposure review for administrators; not a binary patch
MacSystem Settings → General → Software UpdateSafari JavaScript restriction; not a full WebKit fix
iPhone / iPadSettings → General → Software UpdateAvoid untrusted browsing pending Apple update
Android / PixelSettings → System → Software updates; check Google Play system updates tooAvoid untrusted USB hosts; not a device lock-screen fix
LinuxUse your distro's signed security updates, then rebootOptional supervised, reversible MPTCP feature switch (Linux only)
ChromeChrome → Help → About Chrome → RelaunchLimit V8 optimization or stop using outdated Chrome
Other / unsupportedUse the original device vendor's published security updateNo universal cross-OS binary patch exists

Guide from a laptop/desktop (no root/admin rights needed):

python scripts/quickstart.py guide --os linux
python scripts/quickstart.py guide --os windows
python scripts/quickstart.py guide --os macos
python scripts/quickstart.py guide --os android

Each guide provides: before you change anything → simple steps → how to verify the temporary control → how to replace it with the vendor fix. If a profile cannot be justified, the command returns no verified profile.

One executable temporary control: Linux MPTCP runtime disable. It modifies the current namespace only after a separate, explicit administrator command, creates limited rollback state, and does NOT patch the kernel or persist across reboot. See Emergency containment. All other temporary actions are manual guidance, not unsigned binaries.

How to know a real patch is applied and working

Do not treat a successful install command as proof. Record these separately:

  1. The official vendor advisory names the CVE and your exact OS/device.
  2. A signed update was installed; the device or affected service was restarted.
  3. The running product or kernel package is at a vendor-confirmed fixed release.
  4. A benign normal-use check succeeds, such as visiting a trusted page or testing authorized network connections; verify service logs.
  5. Only then, review removing the temporary containment and check function again.

docs/VALIDATION.md has exact commands and an evidence worksheet. For some products (including Android's unmapped chain and vendor-backported kernels), the result must remain unknown / manual review without vendor proof.

Assisted vendor handoff, for products with a published, comparable version floor (example uses an existing MSRC advisory):

python scripts/vendor_handoff.py CVE-2026-33096 --os windows --version 10.0.22631.6936 --vendor-advisory-reviewed --active-version-confirmed --smoke-test-passed

The flags are operator attestations, not automated detection. The strongest result is READY_FOR_CHANGE_REVIEW, never an automatic rollback or claim of exploit resistance. OS versions without a verified release floor are held for manual vendor confirmation.

What about vulnerabilities with no vendor patch?

No code patch is made up for an undisclosed flaw. Most entries in Anthropic's disclosure dashboard do not expose enough technical data to write or validate a legitimate fix. A kernel/device "universal hotfix" cannot safely be synthesized from a CVE name or a hashed disclosure. Use a source-backed, reversible containment where available; otherwise isolate or stop using the affected service.

The data/containments.json catalog contains ten conditional, limited exposure-reduction guides. These do not establish CVE remediation. A new automatic patch is accepted only after source code, reproducible vulnerability, supported versions, regression tests, rollback and review have been established. See Contribution rules.

Distribution, language, and device discovery

The optional read-only platform inventory identifies distribution families (including Debian/Ubuntu, Fedora/RHEL, SUSE, Arch, Alpine, Void, Gentoo, NixOS and Fedora Atomic), architecture, limited firmware context, and the presence of common programming-language toolchains. It does not execute toolchains or package managers, install patches, or certify firmware.

python3 scripts/platform_inventory.py --json
python3 scripts/catalog.py inventory

When a distribution is unknown or reports only a parent through ID_LIKE, the tool declines to recommend a parent distribution's update command. Android, WSL, containers, Linux servers, embedded hardware and cloud-hosted services have different vendor update authorities. Read the Linux, language and hardware coverage guide for exact capabilities, unsupported targets and safe vendor handoffs.

Current scope — reviewed October 30, 2026

The curated data/advisories.json contains 27 individually identified CVEs across 16 advisory records. The source for each record is linked inside the catalog. The original Chrome group contains CVEs attributed to Anthropic/Claude; the October 30 MediaStream CVE is a separate vendor disclosure. This is not an exhaustive CVE or disclosure ledger.

Download Tool