Proof-of-concept exploits and reproduction labs for CVEs analyzed by the Exploit Intelligence Platform
<p align="center">
<a href="https://exploit-intel.com">
<img src="https://cdn.jsdelivr.net/gh/exploitintel/eip-pocs-and-cves@main/.github/assets/eip-hero-banner.png" alt="Exploit Intelligence Platform" width="100%">
</a>
</p>
<h1 align="center">EIP PoCs and CVEs</h1>
<p align="center"><strong>CVE-focused PoC material, labs, and source-backed research from Exploit Intel workflows.</strong></p>
<p align="center">
<a href="https://exploit-intel.com"><img src="https://img.shields.io/badge/Exploit_Intel-platform-1689d8.svg" alt="Exploit Intelligence Platform"></a>
<a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-16b8c4.svg" alt="MIT License"></a>
</p>
This repository publishes packages from [Forge v4](https://github.com/exploitintel/eip-cve-public-v4), CVEForge, and PocSmith.
Each directory groups the material produced for one CVE: source-backed analysis,
Docker lab definitions, PoC code, recorded test results, fix assessment, and any
bypass research. Exact contents vary by target, so the per-CVE README is the
authority for setup, scope, and observed results.
Treat every script, container, and acquired dependency as untrusted offensive
security material. Review it before use and run it only in an isolated
environment that you own or are explicitly authorized to test.
**Browse:** [CVE index](#cve-index) | [Package layout](#typical-package-layout) |
[Setup](#setup) | [Usage](#usage) |
[How entries are produced](#how-entries-are-produced) |
[Related reading](#related-reading)
## CVE index
| CVE | Research package | CVSS |
|:----|:-----------------|:----:|
| [CVE‑2026‑45829](CVE-2026-45829/) | **Chroma ChromaDB (Python backend)**<br>`trust_remote_code` Code Injection (Pre-Auth) to RCE | **10.0** |
| [CVE‑2025‑14931](CVE-2025-14931/) | **Hugging Face smolagents**<br>Pickle Deserialization to RCE (Sandbox Escape) | **10.0** |
| [CVE‑2026‑28289](CVE-2026-28289/) | **FreeScout**<br>TOCTOU File Upload By