How severe is GHSA-chm3-vqcf-52rx?

No CVSS score has been assigned to GHSA-chm3-vqcf-52rx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-chm3-vqcf-52rx?

GHSA-chm3-vqcf-52rx affects the following packages: flowise (npm). Ecosystems affected: npm.

How do I fix GHSA-chm3-vqcf-52rx?

Update flowise to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chm3-vqcf-52rx is resolved across your whole dependency graph.

How do I detect GHSA-chm3-vqcf-52rx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-chm3-vqcf-52rx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-chm3-vqcf-52rx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-chm3-vqcf-52rx can be triaged on real exposure rather than presence alone.

Is GHSA-chm3-vqcf-52rx actively exploited in the wild?

No public exploit code has been indexed for GHSA-chm3-vqcf-52rx 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-chm3-vqcf-52rx?

GHSA-chm3-vqcf-52rx has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th 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-chm3-vqcf-52rx?

GHSA-chm3-vqcf-52rx is classified as CWE-285 (CWE-285), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-chm3-vqcf-52rx published, and has it been updated?

GHSA-chm3-vqcf-52rx was published on August 4, 2026 and was last updated on August 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-chm3-vqcf-52rx — flowise

Fix: FlowiseAI/Flowise#6170

GHSA-chm3-vqcf-52rx is a CWE-285 vulnerability in flowise. A fix is available for flowise — see the affected versions and patch details below.

Flowise: Cross-workspace credential IDOR in openai-assistants-vector-store

Also known asCVE-2026-70472

Published

Aug 4, 2026

Updated

Aug 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-chm3-vqcf-52rx.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

flowisenpm

3Kdownloads / week

Description

Summary

These endpoints accept a client-controlled credential parameter. The server loads credentials by id and uses them directly, without checking whether that credential belongs to the caller’s workspace. If an attacker knows another workspace’s credentialId, they can use that workspace’s OpenAI key.

Details

Route permissions (assistants:*) only check feature access. They do not check credential ownership. The controller passes req.query.credential straight to the service. The service does findOneBy({ id: credentialId }), decrypts the credential, and calls OpenAI APIs. There is no workspaceId check in this flow, so this is an IDOR.

Impact

Cross-workspace unauthorized use of stored OpenAI keys.
Unauthorized read/modify/delete of victim vector stores and files.
Direct billing impact on victim OpenAI account.
Multi-tenant boundary violation with practical exploitability.

Reproduction steps

Set up two workspaces: A (attacker) and B (victim), each with an OpenAI credential.
Log in as a user in workspace A (with assistants-related permissions).
Call /api/v1/openai-assistants-vector-store and set credential to B’s credential ID.
Example: GET /api/v1/openai-assistants-vector-store?credential=<B_credentialId>.
If responses/actions are executed using B’s credential context, the issue is confirmed.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`flowise`	all versions	3.1.3`npm install flowise@3.1.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update flowise to 3.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chm3-vqcf-52rx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-chm3-vqcf-52rx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-chm3-vqcf-52rx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# Summary These endpoints accept a client-controlled `credential` parameter. The server loads credentials by `id` and uses them directly, without checking whether that credential belongs to the caller’s workspace. If an attacker knows another workspace’s `credentialId`, they can use that workspace’s OpenAI key. # Details Route permissions (`assistants:*`) only check feature access. They do not check credential ownership. The controller passes `req.query.credential` straight to the service. The service does `findOneBy({ id: credentialId })`, decrypts the credential, and calls OpenAI APIs. T

O3 Security · Impact-Aware SCA

Is GHSA-chm3-vqcf-52rx in your dependencies?

O3 Security finds GHSA-chm3-vqcf-52rx across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works