Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-chm3-vqcf-52rx

HighCVSS 7.1 / 10
Published Aug 4, 2026·Last modified Aug 4, 2026
Affected Components(0)

No affected components available

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

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

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability.

Threat Intelligence
4.1

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
0.25%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Related Vulnerabilities

Browse More

High severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard