Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2025-3248 PoC — Langflow < 1.3.0 Unauthenticated RCE via /api/v1/validate/code

Source
Associated Vulnerability
Title:Langflow < 1.3.0 Unauthenticated RCE via /api/v1/validate/code (CVE-2025-3248)
Description:Langflow versions prior to 1.3.0 are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code.
Description
CVE-2025-3248: A critical flaw has been discovered in Langflow that allows malicious actors to execute arbitrary Python code on the target system. This can lead to full remote code execution without authentication, potentially giving attackers control over the server.
Readme
# CVE-2025-3248 – Execute arbitrary Python code on vulnerable Langflow server.
 
**Discovered by:** Naveen Sunkavally, Horizon3.ai
**Status:** Public Disclosure  
**Date Reported:** 2025-04-07
**CVE ID:** CVE-2025-3248

---

## 🧾 Screenshot
![ScreenShot](https://github.com/vigilante-1337/CVE-2025-3248/raw/main/static/CVE-2025-3248.png) 

---

## 🧩 Summary

A critical flaw has been discovered in Langflow that allows malicious actors to execute arbitrary Python code on the target system. This can lead to full remote code execution without authentication, potentially giving attackers control over the server. The issue stems from unsafe handling of code input, where user-supplied Python is executed without proper validation or sandboxing.

---

## 📈 Impact

- 🔧 **Remote Code Execution** – Run arbitrary Python code or system commands.
- 🔐 **Full Server Compromise** – Gain control of the system if Langflow runs with elevated privileges.
- 📂 **Data Exposure** – Access sensitive environment variables, credentials, and internal files.
- 🕳️ **Persistence** – Install reverse shells or backdoors for long-term access.

**CVSS Estimate:** Critical (Base Score ~9.8)

---

## 🧾 Affected version
- affected from 0 through 1.2.0 

---


## Installation
You should first install the vulnerable lab, theres a guide on the [Docker](https://github.com/vigilante-1337/CVE-2025-3248/blob/main/Docker/setup) folder
```bash
~$ git clone https://github.com/vigilante-1337/CVE-2025-3248
~$ cd CVE-2025-3248
~$ chmod +x exploit
~$ ./exploit -h
```

---

## 🧾 References

- [CVE-2025-3248 on MITRE (pending)](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-3248)

---

_Disclosure coordinated with respect to responsible disclosure guidelines. This document is released for educational and defensive purposes._
File Snapshot

[4.0K] /data/pocs/1b38d7fb468ba622205d0d9b9d77f5c9284dc311 ├── [4.0K] Docker │   └── [ 846] setup ├── [5.9K] exploit ├── [1.8K] README.md └── [4.0K] static └── [100K] CVE-2025-3248.png 2 directories, 4 files
Shenlong Bot has cached this for you
Remarks
    1. It is advised to access via the original source first.
    2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.
    3. Mirroring, verifying, and maintaining this POC archive takes ongoing effort, so local snapshots are a paid feature. Your subscription keeps the archive online — thank you for the support. View subscription plans →