PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-73604 FlowiseAI CVE debrief

AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-08-13T12:17:24.750Z and has not been modified since then. The NVD entry is currently Awaiting Analysis. Flowise before 3.1.3 contains an incomplete credential redaction vulnerability in the GET /api/v1/credentials/:id endpoint that returns decrypted secrets in plaintext. Authenticated users with credentials:view permission can retrieve sensitive data including database connection URLs with embedded passwords, cloud service account JSON with private keys, and API keys by calling this endpoint. The vulnerability allows access to sensitive information, including database connection URLs with embedded passwords, cloud service account JSON with private keys, and API keys. Security teams and administrators responsible for Flowise installations, particularly those with exposed API endpoints or sensitive data stored within Flowise, should be aware of this vulnerability and take immediate action to mitigate the risk. The CVE-2026-73604 record indicates an incomplete credential redaction vulnerability in Flowise before 3.1.3. Authenticated users with credentials:view permission can retrieve sensitive data via the GET /api/v1/credentials/:id endpoint. Evidence is based on official CVE and NVD records, as well as advisories from Vulncheck and FlowiseAI.

Vendor
FlowiseAI
Product
Flowise
CVSS
HIGH 7.1
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-13
Original CVE updated
2026-08-31
Advisory published
2026-08-13
Advisory updated
2026-08-31

Who should care

Security teams and administrators responsible for Flowise installations, particularly those with exposed API endpoints or sensitive data stored within Flowise, should be aware of this vulnerability and take immediate action to mitigate the risk.

Technical summary

The Flowise application before version 3.1.3 contains an incomplete credential redaction vulnerability. Specifically, the GET /api/v1/credentials/:id endpoint returns decrypted secrets in plaintext. Authenticated users with credentials:view permission can exploit this vulnerability to retrieve sensitive information, including database connection URLs with embedded passwords, cloud service account JSON with private keys, and API keys.

Defensive priority

Authenticated users with credentials:view permission can exploit this vulnerability, making it essential to limit access and monitor API requests.

Recommended defensive actions

  • Limit access to the GET /api/v1/credentials/:id endpoint to only necessary users and roles.
  • Monitor API requests to detect and respond to potential exploitation attempts.
  • Upgrade Flowise to version 3.1.3 or later to apply the fix.
  • Implement additional logging and monitoring to detect sensitive data exposure.
  • Review and update access controls for Flowise API endpoints.

Evidence notes

The CVE-2026-73604 record indicates an incomplete credential redaction vulnerability in Flowise before 3.1.3. Authenticated users with credentials:view permission can retrieve sensitive data via the GET /api/v1/credentials/:id endpoint. Evidence is based on official CVE and NVD records, as well as advisories from Vulncheck and FlowiseAI.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-73604 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-73604

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-73604 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-73604

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.