DexSemon

GitHub · Repository owner · Source ID 187295194
Source profile

Source-scoped identity with 2 associated PoCs and 2 linked vulnerabilities.

Showing 2 PoCs on this page

GitHub

DexSemon/CVE-2026-27495

Repository PoC0Created 2026-07-08ExploitCVE-2026-274953 files

13.1 KiB

GitHubPoC details
Analysisdeepseek-v4-pro:cloud ·

Technical assessment

Python script that authenticates to n8n, creates a workflow containing a JavaScript sandbox escape payload, executes it, and extracts results. It includes both a probe mode (--probe) that detects the vulnerability and an RCE mode (--cmd) that executes arbitrary OS commands via child_process.execSync when NODE_FUNCTION_ALLOW_BUILTIN=* is set.

Backdoor review

No backdoor observed in reviewed code

The supplied evidence consists of a README and a Python exploit script for CVE-2026-27495. The script authenticates to a target n8n instance, creates a workflow containing a JavaScript sandbox escape payload, executes it, and displays the results. All behavior is consistent with a legitimate proof-of-concept exploit for the stated vulnerability. No concealed executable behavior, unrelated remote access, persistence mechanisms, credential exfiltration, or deceptive payloads were observed.

ClassificationExploit
Model confidence98%
AuthenticationRequired
Languagespythonjavascript
Target softwaren8n
Attack typessandbox escaperemote code execution
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact contains a complete Python script that actively exploits CVE-2026-27495 by authenticating to n8n, injecting a sandbox escape payload into a workflow, executing it, and extracting results. The RCE mode executes arbitrary OS commands, which is exploitation, not mere detection.

exploit.py:210-280exploit.py:17-36

Requirements

  • Authenticated user with permission to create or modify workflowsexploit.py:95-104
  • Task Runners enabled (N8N_RUNNERS_ENABLED=true)README.md:12
  • For RCE mode, NODE_FUNCTION_ALLOW_BUILTIN=* must be setREADME.md:38

Observed behavior

  • Authenticates to n8n instance using provided credentialsexploit.py:95-104
  • Creates a workflow containing a Code node with a JavaScript sandbox escape payloadexploit.py:106-136
  • Executes the workflow and polls for completionexploit.py:138-163
  • In probe mode, checks if sandbox was escaped and host constructors are mutableexploit.py:39-72
  • In RCE mode, executes an OS command via child_process.execSync and returns outputexploit.py:17-36
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Credential Handling
Payload withheldCredentials are used only for the intended exploit flow against the user-specified target; no exfiltration to a third party is observed.exploit.py:95-104exploit.py:289-292
Command Execution
Payload withheldThis is the documented RCE capability of the CVE-2026-27495 exploit and is controlled by the user-supplied --cmd argument.exploit.py:17-37exploit.py:293-294
Network Communication
Payload withheldAll network traffic is directed to the target specified by the user; no hardcoded external callbacks or data leaks are present.exploit.py:77-83exploit.py:287-288
Review boundaries

What the analysis did not establish

  • One file (likely docker-compose.yml) is omitted from the evidence; its content is not available for analysis.
  • The evidence does not include execution output or verification that the exploit was successfully run.
  • One file (docker-compose.yml, 445 bytes) was present in the repository but not included as readable text; its content was not reviewed. The exploit script does not import or execute it, and it is described in the README as a lab deployment file.
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

DexSemon/CVE-2026-25194

Repository PoC0Created 2026-07-02ExploitCVE-2026-251943 files

15.6 KiB

GitHubPoC details
Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A Python script that exploits CVE-2026-35194, a SQL code injection vulnerability in Apache Flink, to achieve remote code execution on TaskManagers via the SQL Gateway REST API. It provides two injection vectors (JSON field name and LIKE pattern) to inject arbitrary Java code into generated code.

Backdoor review

No backdoor observed in reviewed code

The repository contains a proof-of-concept exploit for CVE-2026-35194 targeting Apache Flink SQL Gateway. The Python script (exploit.py) and README.md describe and implement two SQL injection vectors (JSON field name and LIKE pattern) to achieve remote code execution on a vulnerable TaskManager. All code is consistent with the stated exploit purpose: it connects to a user-supplied target, checks the version, creates a session, and injects a user-supplied shell command. No concealed backdoor, unrelated payload, persistence mechanism, or credential exfiltration is present. The exploit behavior is transparent and directed solely at the specified target.

ClassificationExploit
Model confidence100%
AuthenticationNot required
LanguagesPython
Target softwareApache Flink
Attack typesCode InjectionRemote Code Execution
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a Python script that actively exploits a vulnerability to achieve remote code execution. It constructs and sends malicious payloads to a target service, injects arbitrary Java code, and executes shell commands on the remote host. This is the definition of an exploit.

exploit.py:1-7exploit.py:152-157exploit.py:184-189

Requirements

  • Network access to the Flink SQL Gateway REST API (default port 8083)exploit.py:14-15
  • Target must be running a vulnerable version of Apache Flink (1.15.0–1.20.3, 2.0.0–2.2.0)exploit.py:9-10

Observed behavior

  • Checks if the target is a vulnerable Flink SQL Gateway by querying /v1/info and parsing the version string.exploit.py:47-87
  • Creates a SQL Gateway session via POST /v1/sessions.exploit.py:89-104
  • Constructs a malicious SQL statement that injects Java code into a generated code string via a crafted JSON field name (JSON vector) or LIKE pattern (LIKE vector).exploit.py:139-197
  • Submits the malicious SQL statement to the gateway, triggering code generation and execution of the injected Java code (Runtime.getRuntime().exec) on the TaskManager.exploit.py:199-244
  • Provides a --check-only mode that only performs version detection without exploitation.exploit.py:312-316
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Exploit Behavior
Payload withheldThis is the normal, documented behavior of a PoC exploit for the stated CVE.exploit.py:199-244exploit.py:286-358
Target Interaction
Payload withheldNo connections to unrelated external hosts or services are made.exploit.py:50-51exploit.py:92-97exploit.py:108-111exploit.py:119-125
Review boundaries

What the analysis did not establish

  • Evidence does not include the Docker Compose file or any other files from the repository, so the lab environment setup cannot be verified.
  • The CVE record (CVE-2026-25194) was absent from the acquired CVEList, so the vulnerability details could not be corroborated against the official record.
  • The analysis is based solely on static review of the provided source code; the code was not executed, and its effectiveness is not confirmed.
  • One file (docker-compose.yml) was present in the repository but not included in the text evidence; its content 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.