dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-52446

HIGH · 8.0 CVSS v3.1 Published 2025-07-25
Fix available
A fix is available. Upgrade to 2023.3.19 / 2024.2.12 or later.
See remediation →
83/100
Remediation priority · High
No privileges

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
Authorization Bypass Through User-Controlled Key vulnerability in Salesforce Tableau Server on Windows, Linux (tab-doc api modules) allows Interface Manipulation (data access to the production database cluster).This issue affects Tableau Server: before 2025.1.3, before 2024.2.12, before 2023.3.19.

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

Authorization bypass vulnerability in Tableau Server's tab-doc API modules allows attackers to manipulate user-controlled keys to bypass authorization checks and gain unauthorized access to the production database cluster through interface manipulation.

MitigationUpgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 or later to patch the authorization bypass in the tab-doc API modules.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tableau ServerApplication
Affected:< 2023.3.19>= 2024.2, < 2024.2.12>= 2025.1, < 2025.1.3

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Tableau Server is installed
    Check for Tableau Server installation by looking for the installation directory (commonly C:\Program Files\Tableau\Tableau Server on Windows or /opt/tableau/tableau_server on Linux) or by running 'tsm status' command if the Tableau Server command line tools are available.
    Affected if Tableau Server is not found on the system (not affected).
  2. Determine the installed Tableau Server version
    Run 'tsm version' from the Tableau Services Manager command line, or check the version information in the Tableau Server installation directory, or look in Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Tableau\Tableau Server [Version] for Windows installations.
    Affected if A version number is returned that falls within the affected ranges: < 2023.3.19, >= 2024.2 and < 2024.2.12, or >= 2025.1 and < 2025.1.3.
  3. Compare version against CVE-affected ranges
    Parse the version number obtained from the previous step and compare it numerically against the three vulnerable version ranges: any version before 2023.3.19, any version from 2024.2.0 through 2024.2.11, or any version from 2025.1.0 through 2025.1.2.
    Affected if The installed version matches one of these three patterns: less than 2023.3.19, between 2024.2.0 and 2024.2.11 inclusive, or between 2025.1.0 and 2025.1.2 inclusive.

If Tableau Server is installed and the version falls below 2023.3.19, is between 2024.2.0-2024.2.11, or is between 2025.1.0-2025.1.2, the environment is affected by this authorization bypass vulnerability in the tab-doc API modules.

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
Upgrade available Upgrade to 2023.3.19 / 2024.2.12 / 2025.1.3 or later
Fixed in 2023.3.192024.2.122025.1.3
Interim mitigation

Upgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 or later to patch the authorization bypass in the tab-doc API modules.

Recommended fix High confidence

2025.1.3 (or latest 2025.x release); alternatively 2024.2.12 or 2023.3.19 depending on your current release line

  1. 1. Back up the Tableau Server repository database and configuration settings
  2. 2. Review Tableau Server upgrade prerequisites and release notes for the target version (2023.3.19, 2024.2.12, or 2025.1.3)
  3. 3. Download the appropriate Tableau Server installer for your platform from the official Tableau website or Salesforce customer portal
  4. 4. Stop all Tableau Server services before upgrading
  5. 5. Run the Tableau Server upgrade installer on the primary node
  6. 6. If using a distributed deployment, run the upgrade on additional nodes in the cluster
  7. 7. Restart Tableau Server services after the upgrade completes
  8. 8. Verify the server is running and validate the upgrade by checking the Server version in Tableau Server Management
Caveat Review Tableau Server release notes for any breaking changes between your current version and the target upgrade version before proceeding

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52446 — 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-2025-52446 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