Threats / Langflow / CVE-2025-3248
CVE-2025-3248
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Langflow vulnerability
Langflow contains a missing authentication vulnerability in the /api/v1/validate/code endpoint that allows unauthenticated remote code execution via crafted HTTP requests.
Verdict
Today item, not a backlog item.
An unauthenticated attacker can exploit missing authentication controls on a code validation endpoint to execute arbitrary code on affected Langflow instances. The vulnerability is actively exploited in the wild.
CISA KEV Yes · 2025-05-055Ransomware use Flagged5EPSS 0.99996 (verify live)6Exploit Weaponized · public PoC7CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
418 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-05), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99996 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Langflow, Langflow. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-306 Missing Authentication — weakness family: Authentication.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 28 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I identify the unauthenticated /api/v1/validate/code endpoint as lacking access controls.
Business
The organization's Langflow deployment is exposed to direct remote code execution without requiring valid credentials.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft malicious HTTP requests containing arbitrary code payloads to the unprotected endpoint.
Business
Attackers achieve code execution within the application runtime environment with no authentication barrier.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute commands with the privileges of the Langflow process to establish persistence or lateral movement.
Business
The compromise escalates from application-level access to potential infrastructure-wide impact depending on process privileges and network segmentation.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by VulnCheckCNA
Credited with finding itNaveen Sunkavally of Horizon3.aifinder