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-2395 — Proof-of-concept demonstrating a race condition in the tar npm package (v7.5.3) causing file collisions during parallel extraction, leading to data corruption or overwrite. | Kitploit
Tools/GitHubGitHub/open-flaw/cve-2026-2395
Vulnerability AnalysisExploitationSupply Chain SecurityLearning & Education
GitHubopen-flaw/cve-2026-2395

CVE-2026-2395

Proof-of-concept demonstrating a race condition in the tar npm package (v7.5.3) causing file collisions during parallel extraction, leading to data corruption or overwrite.

View Repository
3410 months agoNot yet reviewed
Share

CVE-2026-23950

Proof of concept for CVE-2026-23950 - Race condition vulnerability in tar package.

Description

This repository demonstrates a race condition vulnerability in the tar npm package (version 7.5.3) that allows for file collision during extraction. The vulnerability exploits Unicode normalization differences where collision_ss and collision_ß can be treated as the same file due to case-insensitive collisions.

Vulnerability Details

  • CVE ID: CVE-2026-23950
  • Affected Package: tar
  • Affected Version: 7.5.3
  • Vulnerability Type: Race condition leading to file collision
  • Impact: File content corruption/overwriting during parallel extraction

How It Works

The exploit creates a tar archive with two files:

  1. collision_ss - containing 1000 'A' characters
  2. collision_ß - containing 1000 'B' characters

When extracted with parallel processing enabled (jobs: 8), the race condition can cause these files to collide, resulting in:

  • Only one file being created
  • Both filenames potentially pointing to the same inode
  • Content from one file overwriting the other

Setup

npm install

Usage

node index.js

Expected Output

If the race condition is successfully exploited:

  • Files will share the same inode
  • Output will display [*] GOOD

If the vulnerability is not triggered:

  • Two separate files will be created
  • Output will display [-] No collision

Impact

This vulnerability could lead to:

  • Data loss or corruption
  • Security bypasses if file content verification is performed after extraction
  • Unexpected application behavior due to missing or corrupted files

Remediation

Update to a patched version of the tar package when available.

Disclaimer

This code is for educational and research purposes only. Do not use this exploit for malicious purposes.

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.

    930
  • 2

    ghostlock-app

    yukonga/ghostlock-app

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

    554
  • 3

    redforge

    cybersecurity91/redforge

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

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

    349
  • 5

    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.

    326
  • 6

    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.

    289

Explore all tools

Browse our collection of tools

View all tools →