Exploração pública
Catálogo de exploits
Todo exploit público que catalogamos, num índice só. Busque por CVE, nome do exploit ou tecnologia — e veja, ao lado, o que a falha realmente vale: severidade, probabilidade de exploração e se já está sob ataque.
88.052exploits catalogados
40.803CVEs com exploração pública
24.696testados em laboratório
TodosReferência 26.494Exploit-DB 24.489GitHub PoC 18.347VulnCheck XDB 10.605Nuclei 4.578Metasploit 3.539✓ só verificadosrecentespopularesrisco
87.510 exploits
GitHub PoC★ 1
debjit604/PHP2Shell-CVE-2026-109618-CVE-2026-109619
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC
Standalone defensive checker project for CVE-2026-102826: simple-git configuration include command injection. One exploit per repository; implementation pending.
simple-git allows command execution through unblocked Git configuration includes
41RISCO
abrir ↗GitHub PoC
100% Defensive Scanner for CVE-2026-110264 GitLab Arbitrary File Write (PHP2Shell) - No exploit code, only version & patch detection for security teams and learners.
Integer Overflow or Wraparound in GitLab
48RISCO
abrir ↗GitHub PoC
Fixed PHP versions and distro packages for PHP2Shell (CVE-2026-109618, CVE-2026-109619) as JSON. CC0. Data behind php2shell.fyi.
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC★ 102
Scanner for PHP2Shell (CVE-2026-109618/109619): URL blackbox, local device and SSH.
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC★ 1
Zero-dependency Python PoC & Docker Compose reproduction for CVE-2026-109619 via PHP RFC1867 upload progress and opcache.preload. (133 characters)
RCE via stale global state
100RISCO
abrir ↗Exploit-DB✓ VexDay Proof
PHP2Shell (CVE-2026-109618) - PHP core versions after v5.4 - RCE
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC★ 1
absholi7ly/Deep-Technical-Report-CVE-2026-109618-CVE-2026-109619-PHP2Shell
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC★ 3
PHP2Shell — PHP session upload-progress RCE & memory disclosure research (CVE-2026-109618 / CVE-2026-109619): exploits, Docker lab, scanner and tooling. Authorized testing only.
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC★ 6
PHP2Shell - CVE-2026-109618/109619 session.upload_progress UAF PoC - multi-target RCE chain - created by 0verDo$ed
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC★ 1
CVE-2026-114509-POC [Educational Purpose Only]
Laravel TokenGuard authentication bypass through non-string API credentials
63RISCO
abrir ↗GitHub PoC
Guide opérationnel, outils d’audit et procédure de remédiation pour CVE-2026-109618 et CVE-2026-109619.
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC
Check websites and servers for PHP2Shell (CVE-2026-109618, CVE-2026-109619), verify the fix is running, and hunt for compromise.
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC
Detect PHP2Shell (CVE-2026-109618, CVE-2026-109619) PHP RCE exploitation attempts by inspecting POST request bodies with nginx mirror
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC
UNTESTED unofficial PHP images (EOL versions) with php2shell (CVE-2026-109618/109619) mitigation backports - one tag per version/SAPI
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC
Safe, passive, read-only detector for the PHP2Shell CVEs (CVE-2026-109618 / CVE-2026-109619). Reads only self-disclosed PHP version info via a single polite GET and classifies against the affected range. Never exploits.
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC
A script to help triage wordpress installs for the recent PHP Critical CVE-2026-109618 and CVE-2026-109619 vulnerabilities.. Read-only security triage and evidence collection for Plesk-hosted WordPress servers.
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC
PHP2Shell (CVE-2026-109618/109619) vendor and Linux distro status - AI-generated, verify before acting
RCE via OOM corruption
100RISCO
abrir ↗GitHub PoC★ 3
Scanner, interim mitigation and hunting tool for php2shell (CVE-2026-109618 / CVE-2026-109619). No exploit code.
RCE via OOM corruption
100RISCO
abrir ↗Indexamos apenas o link público para a prova de conceito — nunca hospedamos nem redistribuímos código de exploração. Fontes: PoC-in-GitHub, Exploit-DB, Nuclei, Metasploit e VulnCheck XDB. A existência de PoC pública não significa que a falha seja explorável no seu ambiente.