How severe is GHSA-xhxx-56g3-mx2r?

No CVSS score has been assigned to GHSA-xhxx-56g3-mx2r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xhxx-56g3-mx2r?

Affected package information for GHSA-xhxx-56g3-mx2r is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-xhxx-56g3-mx2r?

Upgrade the affected component to the fixed release for GHSA-xhxx-56g3-mx2r, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-xhxx-56g3-mx2r in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-xhxx-56g3-mx2r if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-xhxx-56g3-mx2r actively exploited in the wild?

No public exploit code has been indexed for GHSA-xhxx-56g3-mx2r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-xhxx-56g3-mx2r?

GHSA-xhxx-56g3-mx2r has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-xhxx-56g3-mx2r?

GHSA-xhxx-56g3-mx2r is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xhxx-56g3-mx2r published, and has it been updated?

GHSA-xhxx-56g3-mx2r was published on September 12, 2026 and was last updated on September 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Flowise before 3.1.4 Denial of Service via text-to-speech/ab…

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-xhxx-56g3-mx2r.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Flowise versions before 3.1.4 contain an unauthenticated denial of service vulnerability in the /api/v1/text-to-speech/abort endpoint that accepts user-supplied chatflowId and chatId without ownership verification. Attackers can terminate active chatflow predictions for any user by submitting requests with known chatflow and chat identifiers, causing targeted service disruption.

Affected Products

1 product · 1 configurations

Application

flowiseflowiseai

< 3.1.4

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-xhxx-56g3-mx2r, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Flowise versions before 3.1.4 contain an unauthenticated denial of service vulnerability in the /api/v1/text-to-speech/abort endpoint that accepts user-supplied chatflowId and chatId without ownership verification. Attackers can terminate active chatflow predictions for any user by submitting requests with known chatflow and chat identifiers, causing targeted service disruption.

O3 Security · Impact-Aware SCA

Is GHSA-xhxx-56g3-mx2r in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

Flowise before 3.1.4 Denial of Service via text-to-speech/abortGHSA-xhxx-56g3-mx2r