Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2025-61765_PoC — Proof of Concept of an unsafe pickle deserialization vulnerability in Socket.IO | Kitploit
Tools/GitHubGitHub/locus-x64/cve-2025-61765_poc
Payload GenerationVulnerability AnalysisExploitationWeb Application ExploitationLearning & EducationContainer Escape
GitHublocus-x64/cve-2025-61765_poc

CVE-2025-61765_PoC

Proof of Concept of an unsafe pickle deserialization vulnerability in Socket.IO

View Repository
1350 years agoNot yet reviewed
Share
Website

Summary

A remote code execution vulnerability in python-socketio versions prior to 5.14.0 allows attackers to execute arbitrary Python code through malicious pickle deserialization in multi-server deployments on which the attacker previously gained access to the message queue that the servers use for internal communications. You can find a detailed analysis of this vulnerability in the GitHub Advisory.

Run

There are three docker containers involved in this demo:

  1. Redis Server: Acts as the message broker.
  2. Vulnerable Socket.IO Server: A Flask-based server that uses python-socketio to handle WebSocket connections and communicates via Redis.
  3. Attacker Client: A client that connects to the Socket.IO server and sends a malicious payload to exploit the vulnerability.

There is a docker-compose.yml file that orchestrates these containers. To run the demo, execute the following command in the directory containing the docker-compose.yml file:

docker-compose up --build

This command will build and start all three containers. The Socket.IO server will be accessible at http://localhost:5000, and the attacker client will automatically attempt to exploit the vulnerability upon startup. You can check the evidence directory for any files created by the exploit in the socketio_server container.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    786
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    506
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    429
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    262
  • 6

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    256

Explore all tools

Browse our collection of tools

View all tools →