PoC artifacts
73,479
ExploitDB
46,647
Metasploit
3,348
Repositories
23,484

Exploit catalog results

Showing 25 exploits on this page

GitHub

nullwhisper/CVE-2026-56292-AcyMailing-SQLi

Repository PoCby nullwhisperStars: 0Created 2026-08-13
ScannerCVE-2026-562927 files

16.9 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Python-based mass scanner that sends a crafted SQL injection payload to a specific Joomla AcyMailing endpoint and classifies targets as vulnerable, patched, or error based on the response, without extracting or dumping database contents beyond a version string.

Backdoor review

No backdoor observed in reviewed code

The PoC is a straightforward SQL injection scanner for CVE-2026-56292. It sends a crafted request to a target Joomla endpoint and parses the response to determine vulnerability. All code is readable and directly serves the disclosed exploit. No concealed payloads, data exfiltration to third parties, or deceptive behavior was found.

ClassificationScanner
Model confidence95%
AuthenticationNot required
Languagespython
Target softwareAcyMailing for Joomla
Attack typessql injection
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The code sends a SQL injection payload but only extracts the database version string to determine vulnerability; it does not exfiltrate data, establish a shell, or perform any post-exploitation actions. The README describes it as a 'single + mass scanner' and the script's output is limited to classification and version reporting.

README.md:18cve_2026_56292_acymailing_sqli.py:3cve_2026_56292_acymailing_sqli.py:36cve_2026_56292_acymailing_sqli.py:72-85

Requirements

  • Target must have AcyMailing component installed and the frontentityselect task accessible.cve_2026_56292_acymailing_sqli.py:7-8

Observed behavior

  • Sends a GET request with a UNION SELECT version() payload in the columns parameter to the loadEntityFront endpoint.cve_2026_56292_acymailing_sqli.py:35-36cve_2026_56292_acymailing_sqli.py:61-69
  • Parses the JSON response to extract a non-numeric id field as the database version string, indicating vulnerability.cve_2026_56292_acymailing_sqli.py:72-85
  • Classifies responses as vulnerable, patched, error, or safe based on HTTP status and response body keywords.cve_2026_56292_acymailing_sqli.py:88-141
  • Supports single target and mass scanning with multi-threading, output files for vulnerable/patched/error targets.cve_2026_56292_acymailing_sqli.py:192-205cve_2026_56292_acymailing_sqli.py:231-257
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Url
Payload withheldThe vulnerable endpoint targeted by the exploit.cve_2026_56292_acymailing_sqli.py:35
Payload
Payload withheldThe SQL injection payload used to extract the database version.cve_2026_56292_acymailing_sqli.py:36
Review boundaries

What the analysis did not establish

  • Evidence does not include the TECHNICAL.md writeup file referenced in README.md; only README.md, the scanner script, and requirements.txt are provided.
  • The repository contains 7 files total but only 3 text files are included; 4 files are omitted, including dorks.txt and LICENSE.
  • The scanner script is not executed; classification is based solely on static analysis of the provided source code.
  • Four files from the repository (dorks.txt, TECHNICAL.md, LICENSE, and a .gitignore) were not included in the text evidence, but their metadata and names are consistent with the disclosed project and do not suggest executable behavior.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

pemarine/cve-2026-41940-PoC

Repository PoCby pemarineStars: 0Created 2026-08-13
Model review verdict: Trojan behavior.StubCVE-2026-419403 files

17.2 KiB

AnalysisTrojan behaviordeepseek-v4-pro:cloud ·

Technical assessment

The repository claims to be a PoC for CVE-2026-41940 (cPanel/WHM auth bypass) but contains no exploit logic. The main script (cve.py) is a WSUS exploit simulator with only time.sleep calls and no network requests. The support module (exp.py) is a Windows-only PE mapper that fetches remote modules, unrelated to cPanel. The README describes cPanel exploitation but the code does not implement it.

Backdoor review

Trojan behavior

The repository claims to be a PoC for CVE-2026-41940, a cPanel/WHM authentication bypass. However, the main entry point `cve.py` does not contain any exploit code for this CVE. Instead, it imports and immediately executes `exp.run_sync()`, which connects to a hardcoded remote server (payload withheld:8765) to download and execute arbitrary, uninspected Python modules (`pe_core.py`, `manual_mapper.py`) in memory. This concealed, unrelated remote access trojan is materially misrepresented as a cPanel exploit.

ClassificationStub
Model confidence95%
AuthenticationNot required
LanguagesPython
Target softwarecPanelWHM
Attack typesauthentication_bypass
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a stub because the code does not implement the claimed cPanel/WHM authentication bypass. cve.py contains only placeholder simulation logic (time.sleep, print) and no actual exploit or scanner functionality. exp.py is an unrelated PE mapper. The README describes exploitation but the code is materially incomplete.

cve.py:13-145exp.py:1-225

Requirements

  • The README claims the tool exploits CVE-2026-41940 via CRLF injection in the Authorization header, but the code does not implement this.README.md:5

Observed behavior

  • cve.py defines a WSUSExploit class that simulates a WSUS attack using only time.sleep and print statements; it makes no HTTP requests and does not interact with cPanel/WHM.cve.py:13-145
  • exp.py is a Windows-only PE mapper client that downloads and executes remote modules from a hardcoded server; it is unrelated to cPanel/WHM exploitation.exp.py:1-225
Safety-review evidence

Behaviors behind the backdoor verdict

Flagged behaviors

Concealed Remote Code Execution
  • The main entry point `cve.py` imports `exp` and calls `exp.run_sync(FORCE_SYNC=True)` on line 11. The `exp.py` module contains a hardcoded configuration (lines 16-28) pointing to a remote server at `payload withheld:8765`. The `run_sync` function (line 125) calls `bootstrap`, which downloads Python modules `pe_core.py` and `manual_mapper.py` from this server and executes them in memory using `exec(compile(data, name, "exec"), module.__dict__)` (line 91). This behavior is completely unrelated to the claimed CVE-2026-41940 cPanel exploit and is not disclosed in the README.cve.py:3cve.py:11exp.py:16-28exp.py:125-138exp.py:84-91
Material Misrepresentation
  • The README.md file describes the tool as an exploit for CVE-2026-41940, a cPanel/WHM authentication bypass, and provides usage examples for scanning and post-exploitation. The actual code in `cve.py` is a completely unrelated WSUS exploit simulation that does not implement any of the described cPanel functionality. The `cve.py` script's `main` function parses arguments for a WSUS target, not a cPanel URL. The real malicious behavior is hidden in the imported `exp` module.README.md:1-5README.md:37-44cve.py:13cve.py:148-160

Observables

Ipv4
Payload withheldHardcoded remote server IP address in exp.py from which additional Python modules are downloaded and executed in memory.exp.py:17
Url
Payload withheldConstructed sync URL used to bootstrap the download of remote payloads.exp.py:35-36
Behavior
Payload withheldThe bootstrap function downloads Python modules from a remote server and executes them directly in memory without writing to disk, evading simple file-based detection.exp.py:84-91
Review boundaries

What the analysis did not establish

  • Evidence is limited to the three text files in the repository snapshot; no runtime behavior or external dependencies were observed.
  • The repository may be a decoy or placeholder; the actual exploit logic is absent from the provided code.
  • The actual payloads downloaded from the remote server (pe_core.py, manual_mapper.py) are not included in the evidence and were not reviewed. Their specific harmful actions are unknown, but the mechanism for concealed remote code execution is fully established.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

lxxexxbxx/CVE-2026-33017

Repository PoCby lxxexxbxxStars: 0Created 2026-08-13
ExploitCVE-2026-330177 files

51.3 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact contains a fully functional exploit (exploit.py) that achieves unauthenticated remote code execution on Langflow <= 1.8.1 by sending a crafted POST request to /api/v1/build_public_tmp/{flow_id}/flow with a malicious CustomComponent payload, resulting in a reverse shell. It also includes a scanner (poc.py) for blind RCE detection and a detailed writeup (README.md).

Backdoor review

No backdoor observed in reviewed code

The repository contains a PoC exploit for CVE-2026-33017, an unauthenticated RCE in Langflow. The provided Python scripts (exploit.py, poc.py) and README documentation are consistent with the disclosed vulnerability. The code sends a crafted HTTP request to a target Langflow server to achieve remote code execution. All actions are directed at the operator-specified target (--url) and callback address (--lhost). No concealed, unrelated, or operator-misrepresented harmful behavior was found.

ClassificationExploit
Model confidence100%
AuthenticationNot required
Languagespythonmarkdown
Target softwarelangflow
Attack typesremote code executioncode injectioneval injectionmissing authentication
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

exploit.py is a complete, weaponized exploit that actively exercises the vulnerability to achieve remote code execution and deliver a reverse shell. It goes beyond detection by executing attacker-controlled code on the target.

exploit.py:1-10exploit.py:193-217exploit.py:224-258

Requirements

  • Target running Langflow <= 1.8.1 with a public flow accessible via the build_public_tmp endpoint.README.md:15-16exploit.py:8-9
  • Attacker must be able to reach the target's HTTP service (default port 7860).exploit.py:271

Observed behavior

  • Authenticates to Langflow using admin credentials to obtain a JWT token.exploit.py:46-58
  • Creates a new public flow or uses an existing one to obtain a valid flow_id.exploit.py:61-83
  • Constructs a JSON payload containing a CustomComponent node with embedded Python code that spawns a reverse shell.exploit.py:101-186
  • Sends an unauthenticated POST request to /api/v1/build_public_tmp/{flow_id}/flow with the malicious payload, triggering exec() on the server.exploit.py:193-217
  • Listens for an incoming reverse shell connection and provides an interactive command shell.exploit.py:224-258
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Url
Payload withheldThe target endpoint for the exploit, as described in the CVE. The operator controls the base URL via the --url argument.exploit.py:195-197
Ip
Payload withheldExample attacker IP used in documentation. The operator controls the actual callback IP via the --lhost argument.README.md:194
Command
Payload withheldExample usage of the exploit script. All parameters are provided by the operator.README.md:210-213
Review boundaries

What the analysis did not establish

  • Only 3 of 7 repository files were provided as readable text; 4 files (Dockerfile, Dockerfile.attacker, docker-compose.yml, entrypoint.sh) are omitted.
  • The evidence is static source code; no dynamic execution or runtime behavior was observed.
  • Four files in the repository (Dockerfile, Dockerfile.attacker, docker-compose.yml, entrypoint.sh) were not provided as text and were not reviewed. Their metadata does not indicate executable payloads, but their content could not be verified.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

sonnelon/CVE-2026-33017-PoC

Repository PoCby sonnelonStars: 0Created 2026-08-13
ExploitCVE-2026-330171 file

3.7 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A Python script that exploits CVE-2026-33017 in Langflow by sending a crafted POST request to the unauthenticated payload withheld endpoint. The payload contains a custom component with embedded Python code that executes a reverse shell via os.system().

Backdoor review

No backdoor observed in reviewed code

The PoC is a straightforward Python script that exploits CVE-2026-33017 by sending a crafted POST request to a target Langflow instance. The payload contains a reverse shell connecting back to the operator-supplied host and port. All behavior is consistent with the disclosed unauthenticated RCE exploit, and no concealed or deceptive actions targeting the operator were found.

ClassificationExploit
Model confidence100%
AuthenticationNot required
Languagespython
Target softwarelangflow
Attack typesremote code executioncode injectioneval injection
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The script actively sends a crafted payload to a vulnerable endpoint to achieve remote code execution via a reverse shell, which is the definition of an exploit.

exploit.py:1-110

Requirements

  • Target Langflow instance with a public flow IDexploit.py:9
  • Attacker-controlled listener to receive reverse shellexploit.py:10-11

Observed behavior

  • Constructs a reverse shell payload using os.system() with a bash TCP reverse shell commandexploit.py:16-28
  • Embeds the reverse shell code inside a custom Langflow component definition in a JSON payloadexploit.py:30-83
  • Sends an unauthenticated POST request to the vulnerable build_public_tmp endpoint with the malicious payloadexploit.py:85-103
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Reverse Shell
Payload withheldThe exploit payload executes a reverse shell on the target, connecting back to the operator-controlled address and port provided via command-line arguments.exploit.py:19
Target Endpoint
Payload withheldThe script sends the exploit payload to this unauthenticated endpoint on the target server, which is the vulnerable endpoint described in CVE-2026-33017.exploit.py:86
Review boundaries

What the analysis did not establish

  • The review is based solely on the provided text of exploit.py; no other files or runtime behavior were examined.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

judgedbykira/CVE-2026-25938-FUXA-Unauthenticated-RCE

Repository PoCby judgedbykiraStars: 1Created 2026-08-13
ExploitCVE-2026-259382 files

12.3 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Python script that sends a crafted Node-RED flow to a vulnerable FUXA server's payload withheld endpoint to establish a reverse shell, achieving unauthenticated remote code execution.

Backdoor review

No backdoor observed in reviewed code

The PoC is a straightforward Python script and documentation for CVE-2026-25938, an unauthenticated RCE in FUXA. The script sends a user-supplied reverse shell command to a target server. All behavior is consistent with the disclosed exploit; no concealed, deceptive, or unrelated harmful actions were found.

ClassificationExploit
Model confidence100%
AuthenticationNot required
LanguagesPython
Target softwareFUXA
Attack typesRemote Code ExecutionAuthentication Bypass
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The Python script constructs and sends a malicious payload to a vulnerable endpoint with the intent of executing arbitrary commands on the target server, which is the definition of an exploit.

CVE-2026-25938.py:15-80CVE-2026-25938.py:82-87

Requirements

  • Target FUXA server version 1.2.8 through 1.2.10 with Node-RED plugin enabled.README.md:9
  • Attacker must have a listener ready to receive the reverse shell connection.CVE-2026-25938.py:15

Observed behavior

  • Sends an HTTP POST request to payload withheld with a JSON payload containing a Node-RED flow that includes an exec node configured to execute a bash reverse shell command.CVE-2026-25938.py:20-74
  • Prints success or failure message based on HTTP response status code (200 or 204).CVE-2026-25938.py:75-78
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Reverse Shell
Payload withheldThe exploit payload sends a reverse shell to the operator's specified IP and port, which is the disclosed purpose of the PoC.CVE-2026-25938.py:54
Target Endpoint
Payload withheldThe script sends a POST request to this endpoint on the target server to deploy a malicious Node-RED flow.CVE-2026-25938.py:22
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

sonalisarkar-2003/FTP-vsFTPD-CVE-2011-2523-VAPT-Report

Repository PoCby sonalisarkar-2003Stars: 0Created 2026-08-13
WriteupCVE-2011-25231 file

3.9 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A VAPT report documenting the scanning and exploitation of CVE-2011-2523 (vsFTPd 2.3.4 backdoor) on a Metasploitable 2 target using Nmap and Metasploit. The artifact contains no exploit or scanner code; it is a narrative report with embedded screenshots.

Backdoor review

No backdoor observed in reviewed code

The artifact is a payload withheld-only VAPT report describing the exploitation of CVE-2011-2523 against a Metasploitable 2 target. It contains no executable code, no instructions for the operator to run local commands, and no concealed or deceptive behavior. The report describes standard use of Nmap and Metasploit against a lab target.

ClassificationWriteup
Model confidence95%
AuthenticationNot required
Languagesmarkdown
Target softwarevsftpd
Attack typesbackdoorcommand execution
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a VAPT report in README.md that describes scanning and exploitation steps but contains no executable code, scripts, or configuration files. It is a technical writeup of a known vulnerability.

README.md:1-123

Requirements

  • Target running vsFTPd 2.3.4 with the backdoorREADME.md:56-60
  • Network access to target port 21 and port 6200README.md:60

Observed behavior

  • Describes using Nmap vuln script to detect the vulnerabilityREADME.md:84-88
  • Describes using Metasploit to exploit the backdoor and obtain a root Meterpreter sessionREADME.md:90-102
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Artifact Type
Payload withheldThe artifact is a single README.md file containing a Vulnerability Assessment and Penetration Testing (VAPT) report. It describes steps taken by a security analyst but contains no source code, scripts, or executable payloads.README.md:1-123
Exploit Target
Payload withheldThe report describes exploiting a known backdoor in vsFTPd 2.3.4 on a Metasploitable 2 virtual machine. This is the disclosed target of the exploit, not the operator's machine.README.md:3README.md:47
Exploit Tool
Payload withheldThe report states that the vulnerability was exploited using the Metasploit Framework, a standard penetration testing tool. The operator is expected to configure and run this tool themselves.README.md:15README.md:90
Review boundaries

What the analysis did not establish

  • Evidence consists of a single Markdown report with embedded image links; no exploit or scanner source code is present.
  • Screenshots referenced in the report are not included in the evidence packet.
  • The report references external image URLs for evidence screenshots, but these are not included in the review packet and their content cannot be verified.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

wzhdgithub/GhostLock

Repository PoCby wzhdgithubStars: 0Created 2026-08-13
ExploitCVE-2026-4349963 files

339.6 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The GhostLock repository is a local privilege escalation exploit for CVE-2026-43499, a Linux kernel UAF vulnerability in the rtmutex PI futex path. It uses pselect() and futex operations to trigger a use-after-free on a kernel stack-allocated rt_mutex_waiter, then leverages pipe_buffer heap spraying and fd_set data to control the freed memory. The exploit achieves arbitrary kernel write via the rb_erase() red-black tree operation, modifies the current process's cred structure to gain root privileges, and disables SELinux by writing to selinux_state.enforcing.

Backdoor review

No backdoor observed in reviewed code

The reviewed evidence consists of a Makefile, README, and exploitation documentation for a local privilege escalation exploit targeting CVE-2026-43499. The content describes a standard kernel exploit chain (UAF, arbitrary write, credential modification, SELinux disable) and provides build/usage instructions. No concealed or materially misrepresented behavior harming the operator or an unrelated system was identified. The disclosed behavior is consistent with the stated purpose of a local privilege escalation proof-of-concept.

ClassificationExploit
Model confidence95%
AuthenticationNot required
LanguagesCMakefileMarkdown
Target softwareLinux kernelAndroid GKI
Attack typeslocal privilege escalationuse-after-freearbitrary kernel writeSELinux bypass
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact contains a complete, multi-stage exploit implementation that exercises the CVE-2026-43499 vulnerability to achieve local privilege escalation and SELinux disablement. The README and exploitation documentation describe the full exploit chain, including UAF triggering, heap spraying, arbitrary write via rb_erase, and credential/SELinux modification. The Makefile compiles the exploit source code into an executable binary. This is not a scanner or a writeup; it is functional exploit code.

README.md:1-8README.md:22-30docs/exploitation.md:6-15Makefile:1-27

Requirements

  • Local unprivileged user access to a vulnerable Linux/Android system with USB debugging enabled and ADB connection.README.md:121-125
  • Kernel version must match one of the supported targets (e.g., 6.6.118-android15 for OPPO Find X8).README.md:133-135

Observed behavior

  • Triggers a use-after-free on a kernel stack-allocated rt_mutex_waiter via pselect() and futex PI operations.README.md:14-20docs/exploitation.md:58-91
  • Sprays the kernel heap with pipe_buffer objects to control the memory layout and reoccupy the freed waiter memory.docs/exploitation.md:19-40
  • Constructs a fake rt_mutex_waiter via fd_set data to control the rb_erase() operation, achieving an arbitrary kernel write primitive.docs/exploitation.md:95-155
  • Modifies the current process's cred structure to set uid/gid to 0 and grant all capabilities, and disables SELinux by setting selinux_state.enforcing to 0.README.md:27-30docs/exploitation.md:171-226
  • Spawns a root shell and optionally starts a mini ADB server for continued access.README.md:147-160
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Target
Payload withheldThe artifact is a local privilege escalation exploit for a specific Linux kernel vulnerability.README.md:5-8
Exploit Behavior
Payload withheldThe exploit modifies the current process's credentials to root and disables SELinux, which is standard behavior for a local privilege escalation exploit.README.md:27-30
Network Behavior
Payload withheldThe README mentions a 'miniadb listening on USB' in the output example, which is a disclosed feature for post-exploitation interaction, not a concealed backdoor.README.md:159
Review boundaries

What the analysis did not establish

  • Only 3 of 63 files in the repository were provided as text evidence. The core exploit source code (e.g., src/core/main.c, src/core/pipe.c) is not included, so the analysis relies on the README and documentation descriptions of the exploit logic.
  • The compiled binary 'ghostlock' is present in the repository but was not analyzed; its behavior is inferred from the documentation.
  • The evidence packet reports complete_artifact_coverage as false, indicating that not all files were inspected.
  • Core exploit source code (src/core/*.c) was not included in the selected text evidence; only documentation and build files were reviewed.
  • The compiled binary 'ghostlock' was flagged as metadata-only and not analyzed.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Hunt-Benito/the-sanitizer-is-the-weapon-cve-2026-68749-cve-2026-68750-quadratic-dos-in-elixir-html-sanitize-ex

Repository PoCby Hunt-BenitoStars: 0Created 2026-08-13
ExploitCVE-2026-68749CVE-2026-687504 files

7.6 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a proof-of-concept exploit for CVE-2026-68749 and CVE-2026-68750 in html_sanitize_ex. It contains an Elixir script (payload withheld) that generates malicious payloads and executes them against the vulnerable library functions (HtmlSanitizeEx.html5/1 and HtmlSanitizeEx.basic_html/1) to trigger quadratic CPU exhaustion, measuring and reporting the resulting timing differences.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence consists of a README and a PoC script (payload withheld) that demonstrate two quadratic-complexity denial-of-service vulnerabilities in the html_sanitize_ex library. The code generates benign and malicious HTML payloads, times their processing by the vulnerable library, and prints the timing ratio. No backdoor, concealed harm, or deceptive behavior is present. The script only calls the vulnerable library functions locally and prints results; it does not establish persistence, exfiltrate data, or execute unrelated commands.

ClassificationExploit
Model confidence95%
AuthenticationNot required
LanguagesElixirMarkdown
Target softwarehtml_sanitize_ex
Attack typesDenial of Service (CPU Exhaustion)
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact includes executable code (payload withheld) that actively calls the vulnerable functions with crafted malicious inputs to trigger the described vulnerabilities, which is the definition of an exploit. The payload withheld describes it as a 'PoC' and provides instructions to run it, confirming its purpose is to exercise the vulnerability.

poc.exs:1-76README.md:1-3README.md:22-29

Requirements

  • Elixir >= 1.14 and internet connection to fetch the vulnerable html_sanitize_ex 1.5.2 dependency.README.md:24
  • The vulnerable version of html_sanitize_ex (1.5.2) must be installed via mix deps.get.README.md:27

Observed behavior

  • Generates a benign CSS payload and a malicious CSS payload (differing by a single ':') and calls HtmlSanitizeEx.html5/1 on both, measuring execution time to demonstrate the quadratic regex backtracking (CVE-2026-68749).poc.exs:18-25poc.exs:42-52
  • Generates payloads of 2,000 and 20,000 sibling HTML elements and calls HtmlSanitizeEx.basic_html/1 on both, measuring execution time to demonstrate the quadratic traversal (CVE-2026-68750).poc.exs:31-33poc.exs:54-62
  • Prints the measured timings and the ratio of attack time to benign time, showing the super-linear performance degradation.poc.exs:48-51poc.exs:58-61
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

File
Payload withheldThe main PoC script that generates payloads and measures execution time of the vulnerable library.poc.exs:1-76
File
Payload withheldDocumentation explaining the vulnerabilities, reproduction steps, and expected results.README.md:1-93
Review boundaries

What the analysis did not establish

  • One binary file (.gitignore) was flagged but not analyzed; it is 39 bytes and unlikely to contain executable code.
  • Two text files (mix.exs and .gitignore) are reported in the inventory but their content is not included in the evidence packet, so their exact contents cannot be verified.
  • One binary file (.gitignore, 39 bytes) was not inspected; its small size and non-executable context make it unlikely to contain harmful logic.
  • Two text files (mix.exs and .gitignore) were omitted from the text content but their metadata is present; mix.exs is expected to contain dependency pinning as described in the README.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

CynepMyx/nginx-rift-check

Repository PoCby CynepMyxStars: 0Created 2026-08-13
ScannerCVE-2026-429457 files

37.5 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A Python script that parses nginx configuration dumps to detect patterns vulnerable to CVE-2026-42945. It identifies specific directive pairs (rewrite with '?' in replacement followed by an unnamed capture like $1) and reports findings without exploiting the vulnerability.

Backdoor review

No backdoor observed in reviewed code

The repository contains a Python script (payload withheld) and its documentation (payload withheld) designed to detect nginx configurations vulnerable to CVE-2026-42945. The script parses nginx configuration dumps, identifies a specific pattern of 'rewrite' and subsequent directives using unnamed captures, and reports findings. No backdoor, deceptive payload, or concealed harmful behavior was observed. The code's functionality is fully disclosed and aligns with its stated purpose.

ClassificationScanner
Model confidence95%
AuthenticationNot required
LanguagesPython
Target softwarenginx
Attack typesheap buffer overflow
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a configuration scanner that detects vulnerable directive patterns for CVE-2026-42945. It does not send crafted HTTP requests, trigger the overflow, or execute any exploit code; it only analyzes static configuration text and reports findings.

README.md:3-5check_rewrite.py:1-12

Requirements

  • Requires an nginx configuration dump (e.g., from 'nginx -T') as input.README.md:46-48

Observed behavior

  • Parses nginx configuration text to identify location blocks containing a 'rewrite' directive with a '?' followed by arguments, and a subsequent directive using an unnamed capture ($1-$9).check_rewrite.py:197-282
  • Reports findings with location, rewrite, and consumer directive details, along with confidence levels (high/low).check_rewrite.py:398-424
  • Exits with code 0 if no vulnerable pattern found, 1 if found, 2 if parsing fails.check_rewrite.py:496-499
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

File
Payload withheldThe main analysis script. It reads nginx configuration text, parses it for a specific vulnerability pattern, and outputs findings to stdout or as JSON. It does not make network connections, execute external commands, or write files.check_rewrite.py:1-503
File
Payload withheldDocumentation for the tool, explaining the vulnerability, detection logic, usage, and limitations. It matches the behavior implemented in the script.README.md:1-92
Review boundaries

What the analysis did not establish

  • Only two text files (payload withheld, payload withheld) from the repository are included; five other files are omitted, so the full repository content is not available for review.
  • The evidence packet reports complete_artifact_coverage as false, indicating not all repository files were analyzed.
  • Five files from the repository were not included in the text evidence, but their metadata indicates they are test files and sample configurations, which are unlikely to contain backdoor logic.
  • The analysis is limited to the provided text; any behavior in uninspected binary files (none reported) or external dependencies (none used) is not assessed.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Type010/cve-2025-21479-iqoo11pro

Repository PoCby Type010Stars: 0Created 2026-08-13
WriteupCVE-2025-214792 files

35.3 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A technical writeup documenting the process of porting and executing a temporary root exploit for CVE-2025-21479 on a vivo iQOO 11 Pro. The document details the vulnerability, target device, porting steps, and verification results, but the exploit binary itself is explicitly not provided.

Backdoor review

Backdoor review undetermined

The repository contains a README.md documenting a local privilege escalation exploit for CVE-2025-21479 and a binary file 'payload withheld' which is the compiled exploit payload. The README explicitly states the binary is delivered without source code. The behavior of the binary, including any potential backdoor or deceptive functionality, cannot be reviewed because its contents are uninspected binary data. No positive evidence of a backdoor or deception is present in the readable documentation, but the critical executable behavior is entirely omitted from the reviewable evidence.

ClassificationWriteup
Model confidence95%
AuthenticationNot required
LanguagesChinese
Target softwareQualcomm Adreno GPU firmware (a740_sqe.fw)Android 15Linux kernel 5.15
Attack typesprivilege escalationmemory corruption
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a README.md file that provides a detailed technical analysis of the vulnerability, the porting process, and verification results. It explicitly states the exploit binary 'payload withheld' is a 'binary delivery, source code not public' and is not included as readable text. The packet metadata confirms the binary is flagged and not analyzed, and the analysis routing classifies the artifact as 'NO_POC_CODE_IDENTIFIED'. This constitutes a writeup without executable exploit or scanner code.

README.md:107README.md:1-119

Requirements

  • Target device must be a vivo iQOO 11 Pro running Android 15 (PD2254B_A_15.2.12.2.W10) with vulnerable Adreno 740 GPU firmware v675.README.md:17-21
  • The compiled exploit binary 'payload withheld' must be pushed to the device and executed.README.md:78-80

Observed behavior

  • The exploit achieves arbitrary physical memory read/write by exploiting a GPU firmware vulnerability.README.md:9
  • It bypasses SELinux by physically overwriting selinux_state.enforcing to 0.README.md:45
  • It grants full capabilities to the process while keeping uid=2000 to evade a vivo root-detection watchdog.README.md:47
  • The result is a root shell with full capabilities and SELinux in permissive mode.README.md:69-72
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Binary File
Payload withheldThe compiled exploit payload for CVE-2025-21479, described as a binary delivery with no source code available. Its behavior cannot be analyzed from the provided evidence.README.md:107
Review boundaries

What the analysis did not establish

  • The exploit binary 'payload withheld' is present in the repository but is a binary file that was not analyzed; its source code is not provided.
  • The analysis is based solely on the README.md writeup; the actual exploit code was not inspected or executed.
  • The 'payload withheld' binary (sha256:dc7b0588353381042a6e421b47360431f729739fca260d7730be09b8a044317a) is the core exploit payload and is uninspected. Its behavior, including any potential backdoor, cannot be determined from the provided evidence.
  • The review is limited to the README.md documentation; no source code for the exploit is available for analysis.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

josephfarah-ciso/CVE-2026-9999-exploit

Repository PoCby josephfarah-cisoStars: 0Created 2026-08-13
ScannerCVE-2026-99992 files

17.4 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A WebGL-based fuzzing harness that checks for GPU process crashes in vulnerable Chrome versions on macOS. It fingerprints the browser, runs curated shader stress tests, and mutates GLSL to detect context loss events, but does not deliver a payload or achieve code execution.

Backdoor review

No backdoor observed in reviewed code

The repository contains a README and a self-contained HTML PoC harness for CVE-2026-9999. The harness fingerprints the browser, runs curated WebGL shader triggers, and fuzzes GLSL to hunt for GPU process crashes. All code is client-side JavaScript that operates locally in the browser. No network requests, data exfiltration, remote payloads, or concealed harmful behavior are present. The artifact's behavior is fully consistent with its documented purpose as a research and fuzzing harness.

ClassificationScanner
Model confidence95%
AuthenticationNot required
LanguagesHTMLJavaScriptGLSL
Target softwareGoogle ChromeANGLE Metal backend
Attack typesfuzzingvulnerability scanning
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a scanner because it checks for a vulnerability (GPU process crash via WebGL context loss) without exploiting it. The README explicitly states the root cause is not public and the harness is hypothesis-driven, designed to hunt for a crash rather than deliver a payload. The HTML/JS code compiles shaders and monitors for context loss events, which is detection, not exploitation.

README.md:20README.md:42-43README.md:207-208cve-2026-9999-poc.html:53-55

Requirements

  • Chrome version < 148.0.7778.216 on macOS with Metal GPU supportREADME.md:11README.md:58-63

Observed behavior

  • Fingerprints the browser to determine if the Chrome version is below the fixed version 148.0.7778.216cve-2026-9999-poc.html:38-47
  • Compiles and draws eight curated WebGL2 shaders designed to stress the ANGLE Metal shader translatorcve-2026-9999-poc.html:90-108
  • Generates and executes mutated GLSL fragment shaders in a loop, monitoring for WebGL context loss eventscve-2026-9999-poc.html:110-162
  • Logs context loss events and persists crashing shader source to localStorage for later analysiscve-2026-9999-poc.html:53-55cve-2026-9999-poc.html:150-153
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

LocalStorage Key
Payload withheldThe harness saves a crashing shader to localStorage for later retrieval by the operator, as documented in the README.cve-2026-9999-poc.html:152
LocalStorage Key
Payload withheldThe harness saves crash event logs to localStorage for later retrieval by the operator, as documented in the README.cve-2026-9999-poc.html:61-62
Review boundaries

What the analysis did not establish

  • The root cause of CVE-2026-9999 is not public; the harness is based on analyst hypothesis, not a confirmed trigger.
  • The artifact only detects GPU process crashes (context loss); it does not confirm whether a crash is the specific CVE or an unrelated issue.
  • No ASAN build or crash signature is provided to validate findings.
  • The review is limited to the two text files provided; no external dependencies or network resources are fetched or analyzed.
  • The artifact is a hypothesis-driven fuzzing harness for a vulnerability with no public root cause, so its effectiveness in triggering the specific CVE is unverified.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

jobusa755-a11y/CVE-2026-65640-

Repository PoCby jobusa755-a11yStars: 0Created 2026-08-13
Not analyzedCVE-2026-656401 file
GitHub

yanchenyu360/CVE-2026-41940-Security-Patch

Repository PoCby yanchenyu360Stars: 0Created 2026-08-13
ScannerCVE-2026-419404 files

34.9 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A C++ program that applies a temporary, unofficial patch to cPanel/WHM installations to mitigate CVE-2026-41940. It modifies Perl source files to add input sanitization, purges existing malicious session files, and restarts services. It does not exploit the vulnerability.

Backdoor review

No backdoor observed in reviewed code

The repository contains a C++ source file (payload withheld) and a payload withheld that implement a local privilege-escalation patch for CVE-2026-41940, an authentication bypass in cPanel/WHM. The code requires root/Administrator privileges, backs up target Perl files, inserts sanitization subroutines to filter control characters from session data, purges existing malicious session files, and restarts cPanel services. All behavior is consistent with the disclosed purpose of applying a temporary security patch. No concealed network calls, data exfiltration, unrelated payload execution, or deceptive behavior was observed.

ClassificationScanner
Model confidence95%
AuthenticationNot required
LanguagesC++
Target softwarecPanelWHM
Attack typesauthentication bypass
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a mitigation tool that modifies existing software to prevent exploitation of CVE-2026-41940. It does not contain any code to exercise or trigger the vulnerability; instead, it scans for and patches vulnerable files, and removes malicious session artifacts. This matches the definition of a scanner.

README.md:2-3cve_patch.cpp:706-758

Requirements

  • Must be executed with root/Administrator privileges on a system running cPanel/WHM.cve_patch.cpp:131-139
  • Requires OpenSSL development libraries for compilation.README.md:8

Observed behavior

  • Locates cPanel/WHM Perl source files (.pm, .pl) on the system.cve_patch.cpp:650-704
  • Backs up original files before modification.cve_patch.cpp:177-244
  • Injects Perl subroutines (_cve_2026_41940_sanitize, _cve_2026_41940_clean) and calls to them into session and authentication functions to strip control characters and newlines from session data, user, and password variables.cve_patch.cpp:246-383
  • Scans session directories and deletes files containing carriage returns, newlines, or control characters (0x00-0x1F, 0x7F).cve_patch.cpp:474-532
  • Restarts cPanel, cpsrvd, and whostmgrd services after patching.cve_patch.cpp:534-591
  • Verifies the patch by checking for the presence of injected sanitizer functions and a patch marker in the modified files.cve_patch.cpp:593-648
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

File
Payload withheldMain patch implementation that modifies local cPanel Perl files and restarts services.cve_patch.cpp:1-758
File
Payload withheldDocumentation stating the patch is an unofficial temporary fix for CVE-2026-41940.README.md:1-8
Review boundaries

What the analysis did not establish

  • Evidence includes only two of four repository files; the other two files are omitted and their content is unknown.
  • The artifact is a temporary, unofficial patch and may not fully address all attack vectors.
  • Two files in the repository (unclassified, 14225 bytes total) were not provided as text and were not analyzed. Their content and potential behavior are unknown.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

HORKimhab/CVE-2026-68820

Repository PoCby HORKimhabStars: 1Created 2026-08-13
Not analyzedCVE-2026-53413CVE-2026-688203 files
GitHub

nullwhisper/CVE-2026-14282

Repository PoCby nullwhisperStars: 1Created 2026-08-13
ExploitCVE-2026-142826 files

13.5 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Python script that uploads a PHP web shell to a vulnerable GoDAM WordPress plugin instance via an unauthenticated WPForms file upload, then executes arbitrary commands on the target server.

Backdoor review

No backdoor observed in reviewed code

The PoC is a straightforward exploit for CVE-2026-14282. It uploads a PHP webshell to a vulnerable WordPress target and executes a user-supplied command. All behavior is consistent with the disclosed vulnerability and the artifact's own documentation. No concealed, deceptive, or unrelated harmful actions were found.

ClassificationExploit
Model confidence98%
AuthenticationNot required
Languagespython
Target softwareGoDAM WordPress plugin
Attack typesarbitrary file uploadremote code execution
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The primary artifact is a Python script that actively uploads a PHP web shell to a vulnerable server and executes arbitrary commands, which constitutes exploitation rather than mere detection or scanning.

cve_2026_14282_poc.py:30cve_2026_14282_poc.py:58-80cve_2026_14282_poc.py:164-170

Requirements

  • Target must have a page containing a WPForms form with a GoDAM record field.cve_2026_14282_poc.py:33-55
  • The GoDAM plugin version must be <= 1.12.2 and the save_video_file() handler must be active.README.md:8-15

Observed behavior

  • Fetches a target page and parses HTML to extract WPForms form IDs and GoDAM field IDs.cve_2026_14282_poc.py:33-55
  • Constructs a multipart POST request with a PHP file disguised as video/mp4 and submits it to the detected form.cve_2026_14282_poc.py:58-80
  • Attempts to access the uploaded PHP shell at a predictable web-accessible path and verifies execution by checking for a marker string.cve_2026_14282_poc.py:83-96
  • Executes an attacker-supplied system command via the uploaded shell and prints the output.cve_2026_14282_poc.py:164-170
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Webshell
Payload withheldThe PHP payload uploaded to the target server to achieve remote code execution.cve_2026_14282_poc.py:30
Command Execution
Payload withheldThe operator-supplied command is executed on the target server via the uploaded webshell.cve_2026_14282_poc.py:164-170
Review boundaries

What the analysis did not establish

  • Evidence does not include the lab setup files (docker-compose.yml, setup.php) or the vulnerable plugin binaries; only the README, PoC script, and requirements.txt are provided.
  • The PoC script was not executed; classification is based solely on static analysis of the provided source code.
  • Three files (lab/docker-compose.yml, lab/setup.php, and a .gitignore) were not included in the text evidence, but their metadata shows they are lab setup files and do not affect the PoC's runtime behavior.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

nullwhisper/CVE-2026-14840

Repository PoCby nullwhisperStars: 0Created 2026-08-13
ExploitCVE-2026-148406 files

13.3 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a Python script that exploits CVE-2026-14840 by sending multiple votes with spoofed X-Forwarded-For IPs to bypass per-IP vote restrictions in the YOP Poll WordPress plugin.

Backdoor review

No backdoor observed in reviewed code

The PoC script cve_2026_14840_poc.py performs exactly the disclosed exploit: it sends POST requests to a target WordPress site's YOP Poll REST API endpoint with a spoofed X-Forwarded-For header to bypass per-IP vote limits. No hidden, deceptive, or unrelated harmful behavior is present. The script's actions are limited to the operator-specified target, and all network communication is directly tied to the vote-casting functionality.

ClassificationExploit
Model confidence95%
AuthenticationNot required
LanguagesPython
Target softwareYOP Poll WordPress plugin
Attack typesAuthentication Bypass by Spoofing
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The script actively sends crafted requests to cast multiple votes, which is the exploitation of the vulnerability, not just detection. It is described as a 'PoC' and its main purpose is to demonstrate the bypass by successfully casting votes.

cve_2026_14840_poc.py:1-15cve_2026_14840_poc.py:143-145

Requirements

  • Target must have a page containing a YOP Poll with the vulnerable plugin version (< 7.0.6).README.md:8-12
  • The attacker must be able to send HTTP requests to the target WordPress site.cve_2026_14840_poc.py:38

Observed behavior

  • Fetches a target page and extracts poll ID, nonce, and answer IDs from embedded JSON.cve_2026_14840_poc.py:35-67
  • Sends multiple POST requests to the YOP Poll REST API endpoint with a randomly generated IP in the X-Forwarded-For header.cve_2026_14840_poc.py:70-111
  • Reports the target as vulnerable if more than one vote is accepted.cve_2026_14840_poc.py:165-167
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Network Endpoint
Payload withheldThe script sends vote-casting POST requests to these endpoints on the operator-specified target. This is the core of the disclosed exploit.cve_2026_14840_poc.py:92-95
Http Header
Payload withheldThe script sets a spoofed IP address in the X-Forwarded-For header for each vote request, which is the mechanism for bypassing the per-IP vote restriction.cve_2026_14840_poc.py:89
Dependency
Payload withheldStandard Python HTTP libraries required to run the PoC. No unusual or suspicious dependencies are included.requirements.txt:1-2
Review boundaries

What the analysis did not establish

  • The lab setup files (docker-compose.yml, setup.php) are not included in the text evidence, so the full lab environment cannot be analyzed.
  • The evidence does not include the vulnerable plugin binary, so the exact vulnerable code path cannot be verified.
  • Three files (lab/docker-compose.yml, lab/setup.php, and the .gitignore) were not included in the text evidence, but their omission is not material to the backdoor review as they are described as lab setup files and the primary executable PoC script was fully provided.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

aramosf/CVE-2026-24031

Repository PoCby aramosfStars: 0Created 2026-08-12
ExploitCVE-2026-2403114 files

155.5 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A Python 3 script that performs an unauthenticated SQL injection authentication bypass against Dovecot IMAP/POP3 services. It sends crafted usernames containing UNION SELECT payloads to log in as any user without knowing the real password, and includes a detection phase for the vulnerable no-escape condition.

Backdoor review

No backdoor observed in reviewed code

The PoC is a self-contained Python 3 script that exploits CVE-2026-24031, a SQL injection in Dovecot's SQL-based authentication. The code connects to a user-supplied target, sends crafted IMAP/POP3 authentication payloads, and reports success or failure. All behavior is consistent with the disclosed exploit: no hidden payloads, unauthorized data exfiltration, or concealed persistence mechanisms are present. The script uses only standard library modules and does not download or execute external code.

ClassificationExploit
Model confidence100%
AuthenticationNot required
LanguagesPython
Target softwareDovecot
Attack typesSQL InjectionAuthentication Bypass
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The Python script actively sends SQL injection payloads over the network to bypass authentication and log in as an arbitrary user, which constitutes exploitation, not merely detection or scanning.

cve-2026-24031-poc.py:196-217README.md:5-9

Requirements

  • Dovecot 2.4.0 or 3.1.0 with SQL passdb and auth_username_chars set to emptyREADME.md:20-22
  • Network reachability to the IMAP/POP3/ManageSieve serviceREADME.md:76

Observed behavior

  • Connects to a target IMAP or POP3 service and sends an AUTHENTICATE PLAIN command with a crafted username containing a SQL UNION SELECT payload to override the password column for a victim usercve-2026-24031-poc.py:64-72cve-2026-24031-poc.py:119-128
  • Sends a detection payload (' OR '1'='1' -- ) to fingerprint the no-escape condition by checking for a 'temporary failure' responsecve-2026-24031-poc.py:75-77cve-2026-24031-poc.py:226-237
  • Reports successful authentication bypass when the server returns an OK response for the injected credentialscve-2026-24031-poc.py:247-254
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Network Connection
Payload withheldThe script connects to a target specified by the operator via command-line arguments (lines 172-173 of cve-2026-24031-poc.py). This is the disclosed exploit target.cve-2026-24031-poc.py:172-173
Exploit Payload
Payload withheldThe script constructs SQL injection payloads (lines 64-77) to bypass Dovecot authentication, matching the described vulnerability.cve-2026-24031-poc.py:64-77
Review boundaries

What the analysis did not establish

  • Only the README.md and cve-2026-24031-poc.py files were provided as text; 11 other text files and 1 non-text file were omitted from the evidence packet.
  • The evidence packet reports complete_artifact_coverage as false, indicating not all repository files were analyzed.
  • The repository contains 12 additional files (including binary assets and lab configuration) that were not provided as text. Their content was not reviewed, but the core exploit logic is fully contained in the reviewed Python script.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

LuisCastellanos-dev/cobol-shield

Repository PoCby LuisCastellanos-devStars: 0Created 2026-08-12
ScannerCVE-2021-425745 files

13.4 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a security toolkit that detects and cleans invisible Unicode characters in source code and data files. It provides a CI checker (check-invisibles.py) that scans files for dangerous Unicode ranges and exits with a non-zero code on detection, and a sanitizer (clean-invisibles.py) that removes such characters and generates an audit log. The tools are designed to mitigate CVE-2021-42574 (Trojan Source) and related Unicode attacks. No exploit code is present; the tools only identify and report the presence of dangerous characters.

Backdoor review

No backdoor observed in reviewed code

The repository contains a security toolkit for detecting and cleaning invisible Unicode characters in COBOL source code, addressing CVE-2021-42574. The provided Python scripts perform local file scanning and sanitization as documented. No concealed, deceptive, or harmful behavior targeting the operator or unrelated systems was found.

ClassificationScanner
Model confidence98%
AuthenticationNot required
LanguagesPythonCOBOL
Target softwareGnuCOBOLZowe APICOBOL legacy systems
Attack typesUnicode Bidirectional Algorithm manipulationTrojan Source
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The primary artifact is a scanner. The check-invisibles.py script is explicitly described as a 'CI checker' that 'exits 1 on detection' (README.md line 32). It scans files for dangerous Unicode characters and reports their locations without modifying the target or exercising a vulnerability. The clean-invisibles.py script is a sanitizer that removes dangerous characters, which is a defensive tool, not an exploit. No code in the artifact attempts to exploit CVE-2021-42574 or any other vulnerability; it only detects and cleans the presence of dangerous Unicode sequences.

README.md:32tools/check-invisibles.py:1-14tools/check-invisibles.py:37-43

Requirements

  • Python 3 interpretertools/check-invisibles.py:1
  • Read access to target filestools/check-invisibles.py:66-74

Observed behavior

  • Scans files with specific extensions for Unicode characters in predefined dangerous rangestools/check-invisibles.py:20-28tools/check-invisibles.py:34
  • Reports the file, line, column, and hex bytes of any dangerous character foundtools/check-invisibles.py:54-62
  • Exits with code 1 if any dangerous characters are detected, 0 otherwisetools/check-invisibles.py:85-94
  • Sanitizer removes dangerous characters and creates a backup of the original filetools/clean-invisibles.py:82-86
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

File Scanning Behavior
Payload withheldThis is the disclosed functionality of the PoC, acting as a CI checker.tools/check-invisibles.py:46-63tools/check-invisibles.py:85-91
File Sanitization Behavior
Payload withheldThis is the disclosed functionality of the PoC, acting as a sanitizer with forensic logging.tools/clean-invisibles.py:34-89
Network Activity
Payload withheldThe scripts operate solely on the local filesystem, reading and writing files as specified by the user-provided path argument.tools/check-invisibles.py:1-98tools/clean-invisibles.py:1-135
Review boundaries

What the analysis did not establish

  • Two files (src/AUDITOR-INVISIBLE.cob and .github/workflows/unicode-check.yml) are referenced in the README but not included in the evidence packet; their content is unknown.
  • The evidence packet reports complete_artifact_coverage as false, indicating that not all files from the repository snapshot are included.
  • The analysis is based solely on the provided text content; no code was executed, and the behavior described is inferred from static analysis.
  • Two files (src/AUDITOR-INVISIBLE.cob and .github/workflows/unicode-check.yml) were not provided as text and were not reviewed.
  • The review is limited to the supplied text evidence and does not include execution or analysis of the compiled COBOL program.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

enriquenegri-cyberlaw/boa-cve-2009-4496-analysis

Repository PoCby enriquenegri-cyberlawStars: 0Created 2026-08-12
WriteupCVE-2009-44964 files

14.8 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact is a defensive vulnerability analysis writeup for payload withheld. It documents the vulnerability, performs a root cause analysis, compares vulnerable and patched code, and assesses severity. It explicitly states no active testing, exploitation, or scanning was performed, and contains no exploit or scanner code.

Backdoor review

No backdoor observed in reviewed code

The repository contains a defensive analysis of payload withheld. The provided text files (README.md and analysis/payload withheld.md) are purely documentation. They describe a historical vulnerability, its root cause, patch analysis, and defensive implications. There is no executable code, no exploit payload, no network requests, and no instructions for the operator to perform any action that could harm their own system or a third party. The content is consistent with its stated purpose of cybersecurity education and defensive analysis.

ClassificationWriteup
Model confidence98%
AuthenticationNot required
LanguagesMarkdown
Target softwareBoa web server
Attack typesLog Injection
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a technical analysis document (writeup) that describes a vulnerability, its root cause, and remediation. It contains no code intended to exploit or scan for the vulnerability. The document explicitly disclaims any active exploitation or scanning.

README.md:13-33analysis/CVE-2009-4496.md:48-52

Requirements

  • An HTTP request containing terminal escape sequences must be sent to a vulnerable Boa server.README.md:61
  • The resulting log file must be viewed with a terminal emulator that interprets the escape sequences.README.md:65

Observed behavior

  • The writeup describes the vulnerability conceptually, showing how an unsanitized request pathname is written to an error log.README.md:133-153
  • The writeup describes the patch, which introduces an escaping function to sanitize the pathname before logging.README.md:185-189
  • The writeup explicitly states that no active testing, exploitation, or scanning was performed against any third-party system.README.md:33analysis/CVE-2009-4496.md:48-52
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

CVE ID
Payload withheldThe artifact is a documented analysis of this specific vulnerability in the Boa web server.README.md:8
REPOSITORY PURPOSE
Payload withheldThe README explicitly states the project's objective is defensive analysis, not exploitation. No active testing was performed.README.md:13-33
Review boundaries

What the analysis did not establish

  • The evidence packet reports complete_artifact_coverage as false, indicating that not all files from the repository are included. Two text files (SCOPE.md and analysis/PATCH-ANALYSIS.md) are listed in the repository structure but their content is not provided.
  • Two text files (SCOPE.md and analysis/PATCH-ANALYSIS.md) were identified in the repository inventory but their content was not included in the evidence packet. The packet metadata indicates they are text files, and the included README.md describes their expected content as defining ethical boundaries and documenting patch differences, which is consistent with the overall defensive analysis theme.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

kagancapar/CVE-2026-54984

Repository PoCby kagancaparStars: 0Created 2026-08-12
WriteupCVE-2026-549842 files

17.3 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A public disclosure record for CVE-2026-54984, a heap-based buffer overflow in Windows ICC file parsing. The repository contains no proof-of-concept code or technical analysis, only advisory identifiers, scoring, affected builds, patch KBs, and a timeline assembled from vendor and ZDI advisories.

Backdoor review

No backdoor observed in reviewed code

The repository contains only two Markdown files (English and Turkish) that document the CVE-2026-54984 vulnerability disclosure. The README explicitly states it contains no proof of concept or technical analysis. No executable code, scripts, shellcode, or commands are present. The content is purely informational, summarizing public advisories, affected products, and a timeline.

ClassificationWriteup
Model confidence100%
AuthenticationNot required
LanguagesMarkdown
Target softwareMicrosoft Windows Imaging ComponentMscms.dll
Attack typesheap-based buffer overflow
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a writeup because it provides substantive technical analysis of CVE-2026-54984, including vulnerability description, attack characteristics, affected products, and a disclosure timeline, without containing any exploit or scanner code. The author explicitly states the repository contains no PoC or technical analysis, but the assembled advisory information constitutes a writeup.

README.md:8README.md:28-44README.md:46-61

Requirements

  • User interaction is required; the target must open or process attacker-supplied content (e.g., a malicious ICC color profile).README.md:55

Observed behavior

  • The artifact describes the vulnerability as a heap-based buffer overflow in Mscms.dll during ICC profile parsing, allowing an out-of-bounds write that can lead to arbitrary code execution in the context of the current process.README.md:32README.md:36
  • The artifact provides a table of affected Windows versions and their fixed build numbers, along with corresponding KB articles.README.md:67-82
  • The artifact explicitly states it contains no proof of concept and no technical analysis.README.md:8
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Disclosure
Payload withheldConfirms the artifact is a documentation-only repository with no executable exploit code.README.md:8
Review boundaries

What the analysis did not establish

  • The artifact contains no executable code, no proof-of-concept, and no original technical analysis beyond what is stated in the vendor and ZDI advisories. The author notes that ZDI acquisition terms grant exclusivity over technical detail.
  • Review is limited to the two text files provided; no other files exist in the repository snapshot.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

aisha-jimoh/cve-2025-55182-react2shell-analysis

Repository PoCby aisha-jimohStars: 0Created 2026-08-12
Not analyzedCVE-2025-551822 files
GitHub

matesz44/cve-2026-39987

Repository PoCby matesz44Stars: 0Created 2026-08-12
ExploitCVE-2026-399875 files

16.2 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Go-based exploit for CVE-2026-39987 that connects to the unauthenticated /terminal/ws WebSocket endpoint on Marimo <0.23.0 to obtain a PTY shell and execute arbitrary system commands.

Backdoor review

No backdoor observed in reviewed code

The repository contains a Go-based proof-of-concept (PoC) exploit for CVE-2026-39987, a pre-authentication remote code execution vulnerability in Marimo. The provided source code (main.go) and documentation (README.md) describe and implement a straightforward WebSocket client that connects to the vulnerable /terminal/ws endpoint and executes user-supplied commands. No concealed, deceptive, or operator-directed harmful behavior beyond the advertised exploit functionality was observed in the reviewed text files.

ClassificationExploit
Model confidence95%
AuthenticationNot required
LanguagesGo
Target softwaremarimo
Attack typesRemote Code ExecutionAuthentication Bypass
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a command-line tool that actively exploits the missing authentication on the /terminal/ws endpoint to execute arbitrary commands on the target. The README and main.go show it takes a target URL, connects via WebSocket, and runs commands (default 'uname -a', custom via -c, or interactive shell via -i). This is exploitation, not just detection or scanning.

README.md:14cmd/cve-2026-39987/main.go:14-15cmd/cve-2026-39987/main.go:17-19README.md:47-81

Requirements

  • Target running Marimo <0.23.0 with the /terminal/ws WebSocket endpoint exposed.README.md:14

Observed behavior

  • Connects to the target WebSocket URL without authentication.cmd/cve-2026-39987/main.go:17
  • Executes a default command (uname -a) or a user-specified command on the remote host via the terminal session.README.md:47-55README.md:57-66
  • Supports an interactive mode that provides a live shell to the attacker.README.md:68-81
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Behavior
Payload withheldThe PoC implements the advertised CVE-2026-39987 exploit by connecting to the vulnerable endpoint and running commands, which is the expected behavior for a PoC.cmd/cve-2026-39987/main.go:14-15cmd/cve-2026-39987/main.go:17-19cmd/cve-2026-39987/main.go:31-36
Dependency
Payload withheldStandard WebSocket library used for the exploit connection; no indication of malicious modification.go.mod:6
Review boundaries

What the analysis did not establish

  • The runner package (pkg/runner) that contains the actual WebSocket connection and command execution logic is not included in the supplied text files; only main.go, README.md, go.mod, and go.sum are provided.
  • The evidence does not include the go.sum file content for the runner package, so the exact implementation of the exploit connection and shell interaction cannot be verified from the supplied text alone.
  • The pkg/runner package source is not included in the selected text files; its implementation is unknown.
  • One file (likely a binary or non-text file) was omitted from the text evidence and not analyzed.
  • The go.sum file was provided as text but its binary content was not inspected for tampering.
  • The review is limited to static analysis of the provided text; no dynamic execution or network behavior was observed.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Boreas37/CVE-2026-41452-PoC

Repository PoCby Boreas37Stars: 1Created 2026-08-12
ExploitCVE-2026-414522 files

8.2 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Python script that exploits CVE-2026-41452 in Krayin CRM by sending an AJAX POST request to bypass installer middleware and overwrite the primary admin account, then logs in to confirm takeover.

Backdoor review

No backdoor observed in reviewed code

The PoC consists of a README and a Python script that demonstrate the CVE-2026-41452 authentication bypass. The script sends HTTP requests to overwrite the admin account and then logs in to confirm access. No backdoor, deceptive payload, or concealed harmful behavior is present. The code performs only the advertised exploit steps against the target CRM instance.

ClassificationExploit
Model confidence98%
AuthenticationNot required
Languagespython
Target softwareKrayin CRM
Attack typesauthentication bypassaccount takeover
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The Python script actively sends crafted HTTP requests to overwrite the admin account and then authenticates to confirm access, which constitutes exploitation rather than mere detection or scanning.

poc_cve-2026-41452.py:71-81poc_cve-2026-41452.py:84-103poc_cve-2026-41452.py:106-116

Requirements

  • Target Krayin CRM instance (≤2.2.0 or 2.2.4) with installer endpoint accessiblepoc_cve-2026-41452.py:4

Observed behavior

  • Sends a non-AJAX POST to /install/api/admin-config-setup to confirm the middleware blocks normal requestspoc_cve-2026-41452.py:57-68
  • Sends an AJAX POST with X-Requested-With: XMLHttpRequest header to bypass CanInstall middleware and overwrite admin user (id=1) with attacker-supplied credentialspoc_cve-2026-41452.py:71-81
  • Extracts CSRF token from /admin/login page and logs in with the overwritten credentialspoc_cve-2026-41452.py:84-103
  • Accesses /admin/dashboard to confirm successful admin takeoverpoc_cve-2026-41452.py:106-116
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Behavior
Payload withheldThis is the documented CVE exploit behavior; it targets the vulnerable CRM, not the PoC operator.poc_cve-2026-41452.py:71-77
Exploit Behavior
Payload withheldStandard proof-of-exploit verification; no unrelated actions.poc_cve-2026-41452.py:84-116
Review boundaries

What the analysis did not establish

  • Only the two text files (README.md and poc_cve-2026-41452.py) were reviewed; no binary files were present or analyzed.
  • The review does not assess whether the exploit works as claimed, only whether the supplied evidence contains backdoor or deceptive behavior.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Boreas37/CVE-2026-73034-PoC

Repository PoCby Boreas37Stars: 1Created 2026-08-12
ExploitCVE-2026-730343 files

7.9 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A bash script that exploits CVE-2026-73034, an unauthenticated path traversal vulnerability in DB-GPT v0.8.1, by sending crafted HTTP requests with directory traversal sequences in the 'user-id' header to write arbitrary files to the server.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence consists of a README and a bash PoC script for CVE-2026-73034. Both files describe and demonstrate the path traversal vulnerability in DB-GPT v0.8.1. The script sends crafted HTTP requests to a target server to write files outside the intended directory, and then verifies the file placement via docker exec. No concealed executable behavior, persistence, credential theft, or unrelated payload delivery is present. The script's actions are consistent with a legitimate proof-of-concept for the stated CVE.

ClassificationExploit
Model confidence100%
AuthenticationNot required
Languagesbash
Target softwareDB-GPT
Attack typespath traversalarbitrary file write
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The script actively sends crafted HTTP requests to a vulnerable endpoint to write files to arbitrary locations on the server, which is the definition of an exploit. It includes verification steps to confirm successful exploitation.

poc_cve-2026-73034.sh:48-50poc_cve-2026-73034.sh:55-57poc_cve-2026-73034.sh:63-68

Requirements

  • A running, vulnerable instance of DB-GPT v0.8.1 or earlier.poc_cve-2026-73034.sh:6
  • Network access to the target's /api/v1/python/file/upload endpoint.poc_cve-2026-73034.sh:35
  • Docker must be installed and accessible for the verification steps.poc_cve-2026-73034.sh:63-65

Observed behavior

  • Sends a normal upload request with a safe 'user-id' header as a control test.poc_cve-2026-73034.sh:42-44
  • Sends an exploit request with a 'user-id' header containing directory traversal sequences to write a file to /tmp/pwned/.poc_cve-2026-73034.sh:48-50
  • Sends a second exploit request to write a file to /root/.poc_cve-2026-73034.sh:55-57
  • Verifies the exploit by executing commands inside the target Docker container to list and read the written files.poc_cve-2026-73034.sh:63-68
  • Tests a fixed build of the application to confirm the vulnerability is patched and the exploit is blocked.poc_cve-2026-73034.sh:72-76
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Vulnerability Exploit
Payload withheldThe PoC demonstrates the core vulnerability described in CVE-2026-73034 by injecting directory traversal sequences into the user-id header to write files to arbitrary locations.poc_cve-2026-73034.sh:48-50poc_cve-2026-73034.sh:55-57
Verification Command
Payload withheldThe script uses docker exec to verify that the uploaded files were written to the traversal target directories, which is standard for a PoC that validates the exploit.poc_cve-2026-73034.sh:62-68
Review boundaries

What the analysis did not establish

  • The evidence packet reports complete_artifact_coverage as false, indicating one file (likely a license or similar) was omitted from the text content, but the two provided files (README.md and poc_cve-2026-73034.sh) are complete and sufficient for classification.
  • One file (unclassified, 2411 bytes) was omitted from text analysis per binary policy; its metadata was flagged but not inspected. No evidence suggests it contains harmful content, but it was not reviewed.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

GitHub

Boreas37/CVE-2026-33267-PoC

Repository PoCby Boreas37Stars: 1Created 2026-08-12
ScannerCVE-2026-332672 files

5.4 KiB

Analysisdeepseek-v4-pro:cloud ·

Technical assessment

The artifact contains a Python script that sends a raw HTTP request with '@'-prefixed headers to a target Apache Traffic Server and prints the response. It is designed to verify whether the server is vulnerable to CVE-2026-33267 by checking if the headers are leaked to plugins or stripped. It does not exploit the vulnerability to achieve any impact beyond detection.

Backdoor review

No backdoor observed in reviewed code

The repository contains a README and a Python PoC script for CVE-2026-33267. The script sends a raw HTTP request with '@'-prefixed headers to demonstrate the vulnerability. No backdoor, deceptive payload, or concealed harmful behavior is present. The code performs only the advertised network test and prints the response.

ClassificationScanner
Model confidence95%
AuthenticationNot required
LanguagesPython
Target softwareApache Traffic Server
Attack typesInput Validation
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The Python script sends a crafted request to trigger the vulnerability but only observes the response; it does not perform any action that exploits the metadata spoofing to achieve unauthorized access, data modification, or other impact. The README explicitly states the script 'demonstrates and verifies the primitive (leak vs. strip)' and that the practical RCE chain depends on target plugins, which this code does not implement.

README.md:47-51at_headers_spoof.py:2-19

Requirements

  • Target must be running a vulnerable version of Apache Traffic Server (9.2.0-9.2.14 or 10.1.0-10.1.3) with a plugin that logs or acts on '@' headers.README.md:9-10

Observed behavior

  • Sends a raw HTTP GET request containing '@Ats-Internal: pwned' and '@Another-At: test' headers to a specified host and port.at_headers_spoof.py:50-57
  • Receives and prints the first 400 bytes of the HTTP response.at_headers_spoof.py:63-75
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Network Connection
Payload withheldThe PoC connects to a target specified by the user to send a crafted HTTP request, which is the expected behavior for a vulnerability demonstration.at_headers_spoof.py:59-61
Http Request
Payload withheldThe script constructs and sends an HTTP request containing the spoofed internal headers to trigger the vulnerability.at_headers_spoof.py:50-57
Review boundaries

What the analysis did not establish

  • The analysis is based solely on the provided source code and documentation; the code was not executed, and its effectiveness or safety is not verified.
  • The artifact relies on an external custom plugin ('at_probe') for full verification, which is not included in the provided files.
  • Only the two text files (README.md and at_headers_spoof.py) were reviewed; no other files exist in the repository.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.