dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-55411

MEDIUM · 6.8 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ToolJet is the open-source foundation am AI-native platform for building and deploying internal tools, workflows and AI agents. Prior to 3.20.1780-lts, the authenticated endpoint POST /api/data-sources/decrypt returns the decrypted plaintext for any credential whose credential_id is supplied in the request body. Unlike every neighbouring data-source route, this handler is not protected by ValidateDataSourceGuard, does not receive the calling @User(), and the underlying CredentialsService.getValue() looks the credential up by id only, with no organization scoping. As a result, any authenticated user of any organization can decrypt the data-source secrets of any other organization by supplying that organization's credential_id — a cross-tenant confidentiality breach. This vulnerability is fixed in 3.20.1780-lts.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an IDOR (Insecure Direct Object Reference) vulnerability allowing cross-tenant data access. The POST /api/data-sources/decrypt endpoint accepts any credential_id without ValidateDataSourceGuard protection or organization scoping, enabling any authenticated user to decrypt data-source credentials from any organization by supplying the credential_id.

MitigationUpgrade to version 3.20.1780-lts or later. Until then, disable the vulnerable endpoint or implement temporary organization-level access controls to restrict decryption requests to the caller's organization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the /api/data-sources/decrypt endpoint is accessible
    Send a POST request to /api/data-sources/decrypt with a valid authentication token but without any body, or with a test credential_id, and observe if the endpoint responds (even with an error indicating missing parameters). If the endpoint returns a structured response rather than a 404, it is exposed.
    Affected if The endpoint is exposed and responds to authenticated requests.
  2. Check the installed product version
    Inspect the product's version information through its admin UI, API (e.g., GET /api/version), configuration file, or CLI command. Compare this version against the fixed version 3.20.1780-lts.
    Affected if The installed version is earlier than 3.20.1780-lts.
  3. Test organization scoping enforcement
    Authenticate as a user belonging to Organization A. Make a POST request to /api/data-sources/decrypt with a credential_id that belongs to Organization B (a different organization). Observe whether the request is rejected with an organization mismatch error or allowed to proceed.
    Affected if The request succeeds or returns credential data from an organization other than the authenticated user's organization.
  4. Verify ValidateDataSourceGuard is implemented
    Examine the application source code, configuration, or API gateway settings for the presence of ValidateDataSourceGuard middleware or protection logic on the /api/data-sources/decrypt endpoint. Look for organization validation checks that ensure the authenticated user owns the requested credential_id.
    Affected if ValidateDataSourceGuard protection is missing or organization validation is not enforced on this endpoint.

User is affected if running a version earlier than 3.20.1780-lts AND the /api/data-sources/decrypt endpoint is accessible without proper cross-tenant isolation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 3.20.1780-lts or later. Until then, disable the vulnerable endpoint or implement temporary organization-level access controls to restrict decryption requests to the caller's organization.

Recommended fix High confidence

3.20.1780-lts

  1. Check the current ToolJet version by accessing the admin panel or checking the deployment configuration
  2. Plan for upgrade during a maintenance window to avoid service disruption
  3. Back up the current database and configuration files before upgrading
  4. Upgrade ToolJet to version 3.20.1780-lts by pulling the latest LTS Docker image or using the package manager appropriate to your deployment method
  5. After upgrading, verify the new version is running by checking the admin panel or API response headers
  6. Test that the /api/data-sources/decrypt endpoint now properly validates organization context before returning credentials
  7. Ensure the ValidateDataSourceGuard is now applied to this endpoint and that credentials are scoped to the user's organization

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55411 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55411 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data