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-2026-23003-Cross-Chain-Bridge-Message-Forging-via-Missing-Origin-Chain-ID — Cross-chain bridge PoC for CVE-2026-23003: demonstrates message forging via missing origin chain ID using vulnerable Solidity contract and Python exploit. | Kitploit
Tools/GitHubGitHub/george0papasotiriou/cve-2026-23003-cross-chain-bridge-message-forging-via-missing-origin-chain-id
Vulnerability AnalysisExploitationLearning & EducationAdversarial Attack
GitHubgeorge0papasotiriou/cve-2026-23003-cross-chain-bridge-message-forging-via-missing-origin-chain-id

CVE-2026-23003-Cross-Chain-Bridge-Message-Forging-via-Missing-Origin-Chain-ID

Cross-chain bridge PoC for CVE-2026-23003: demonstrates message forging via missing origin chain ID using vulnerable Solidity contract and Python exploit.

View Repository
11353 months agoNot yet reviewed

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.

    1.1k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    599
  • 3

    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.

    394
  • 4

    ARTEX

    baarai/artex

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

    321
  • 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.

    277
  • 6

    Aliens_eye

    arxhr007/aliens_eye

    AI powered OSINT engine to discover and map 7,700+ social media identities across the web

    257

Explore all tools

Browse our collection of tools

View all tools →
Share

CVE-2026-23003 – Cross‑Chain Bridge Message Forging via Missing Origin Chain ID

Program Code (Solidity + Python exploit)

// Bridge.sol - Vulnerable bridge contract
contract Bridge {
    mapping(bytes32 => bool) public processed;
    event Deposited(address from, address to, uint256 amount, uint256 chainId);
    function deposit(address to, uint256 amount, uint256 chainId) external payable {
        emit Deposited(msg.sender, to, amount, chainId);
    }
    function withdraw(bytes memory proof, address from, address to, uint256 amount, uint256 chainId) external {
        // Verify proof signature (simulated)
        require(verifyProof(proof, from, to, amount, chainId), "Invalid proof");
        // Missing check: did this message originate from chainId?
        // An attacker can replay a Deposit event from another chain where they are the 'from'
        payable(to).transfer(amount);
    }
    function verifyProof(...) internal pure returns (bool) { return true; } // simplified
}

CVE-2026-23003 – Cross‑Chain Bridge Message Forging via Missing Origin Chain ID

Severity: Critical

Overview

A cross‑chain bridge validates message proofs but does not check the chain ID of the source chain. An attacker can replay a deposit event from a low‑security chain onto the main bridge, effectively minting tokens out of thin air.

Vulnerability Details

  • Type: Logic Vulnerability / Replay Attack
  • Impact: Unlimited token minting, total bridge drain.
  • Root Cause: The withdraw function accepts a chainId parameter from the proof but does not verify it matches the expected source chain; the proof only signs the message, not the chain context.

Exploit Demonstration

Deploy the vulnerable contract, simulate a deposit on a test chain, then call withdraw on the main chain with the same proof – the tokens are released.

Mitigation

  • Include the source chain ID in the signed message and verify it in the contract.
  • Use a chain‑specific nonce or sequence number.
  • Implement a multi‑signature validator that inspects the chain origin.

Installation & Usage

git clone https://github.com/yourorg/CVE-2026-23003.git
cd CVE-2026-23003
# Deploy with Hardhat/Foundry and test
Download Tool