Vulnerability report

Active exploitation observed Confirmed confidence Not in CISA KEV

CVE-2024-8181

Flowise Authentication Bypass

FlowiseAI / Flowise · 1.8.2

Watch CVE-2024-8181 Browse KEV feed
Severity
CVSS 9.8 · Critical
Confidence
Confirmed
Exploit status
Observed in sensors
EPSS
45.1%
First observed
12 Jun 2026
Last observed
08 Oct 2026

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2024-8181 is an unauthenticated Flowise Authentication Bypass. An Authentication Bypass vulnerability exists in Flowise version 1.8.2. This could allow a remote, unauthenticated attacker to access API endpoints as...

Is it exploited?

Yes. Previdian sensors observed exploitation attempts with confirmed confidence. Also confirmed by third-party sources.

Who is affected?

FlowiseAI / Flowise 1.8.2.

What should we do?

Patch immediately, validate internet-facing exposure, and monitor for matching requests.

Overview

An Authentication Bypass vulnerability exists in Flowise version 1.8.2

An Authentication Bypass vulnerability exists in Flowise version 1.8.2. This could allow a remote, unauthenticated attacker to access API endpoints as an administrator and allow them to access restricted functionality.

flowiseai Affected
flowise
1.8.2
FlowiseAI Affected
Flowise
1.8.2
Published
27 Aug 2024
Exploitation Reported
30 Jul 2025
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
None

Tags

nuclei_scanner

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

The Shadowserver

Recorded 30 Jul 2025

A trusted third party reported exploitation.

Active exploitation observed

Previdian sensor

First observed 12 Jun 2026

Previdian first observed exploitation attempts targeting this vulnerability in our honeypot sensors.

Proof of concept available

Nuclei Templates

Recorded 12 Jun 2026

Public scanner or PoC coverage increases practical exploitability.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
The Shadowserver First 2025-07-30 00:00 UTC
Previdian Sensors 2026-06-24 16:09 UTC

Operational indicators for this CVE are listed under Detection.

Sensor telemetry

First-party evidence of exploitation activity

Previdian sensors recorded exploitation attempts targeting this vulnerability. The cards and chart show volume, unique attackers, and daily activity.

87

Attempts observed

30

Unique attacker IPs

17

Attacker countries

BG · BR · CH · CN · DE · ER · HK · IN · IR · MY · NL · NZ · PL · RU · US · VN · YE

12

Sensors observed

CVE-2024-8181 exploitation attempts over the last 88 days

Daily events observed by Previdian sensors

Updated 09 Oct 2026

0
2
24
6
4
4
4
0
2
1
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
1
0
2
0
1
0
4
1
2
0
0
0
0
0
0
0
0
0
0
0
1
0
2
3
2
0
0
0
0
0
0
0
0
2
2
0
1
0
0
0
1
0
0
1
2
3
1
1
0
3
0
1
0
14 Jul 1 Aug 19 Aug 6 Sep 9 Oct

First observed 12 Jun 2026 · Last observed 08 Oct 2026

Pro adds sensor region and window summaries. Enterprise adds raw IPs, paths, User-Agents, and payloads.

Start 14-day Pro trial

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
5
18
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Attacker IP Indicators

Attacker IP indicators observed · available in Pro and Enterprise.

Sensor-derived attacker IP indicators are available to Pro and Enterprise accounts under Detection and through the Pro API.

Learn about Pro API access

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Scanner Reference Detected
Nuclei https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2024/CVE-2024-8181.yaml 25 Apr 2025

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.8 Critical

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

45.1%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Improper Authentication CWE-287

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

Flowise <= 1.8.2 Authentication Bypass

nuclei · Created Unknown

Timeline

From disclosure to observed exploitation

  1. 14:20 UTC

    Public PoC available

    Public proof-of-concept code published

  2. 00:34 UTC

    Indicators of compromise added (38)

    Indicators of compromise recorded

  3. 00:34 UTC

    Observed by Previdian sensors

    Evidence-backed exploitation signal

  4. 00:00 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party attested exploitation

  5. 00:00 UTC

    Nuclei template available

    Scanner coverage available

  6. 13:10 UTC

    CVE published

    Vulnerability disclosed publicly

  7. 15:06 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2024-8181

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2024-8181",
  "confidence": "Confirmed",
  "cvss_score": 9.8,
  "cvss_estimated": false,
  "epss_score": 0.4505,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": true
  },
  "sensor_telemetry": { "attempts": 87, "sensors": 12 }
}