dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-26495

HIGH · 7.5 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to 2020.4.19 / 2021.1.16 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Cleartext Storage of Sensitive Information vulnerability in Salesforce Tableau Server can record the Personal Access Token (PAT) into logging repositories.This issue affects Tableau Server: before 2022.1.3, before 2021.4.8, before 2021.3.13, before 2021.2.14, before 2021.1.16, before 2020.4.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 · moderate confidence

Tableau Server versions before 2022.1.3, 2021.4.8, 2021.3.13, 2021.2.14, 2021.1.16, and 2020.4.19 store Personal Access Tokens (PATs) in cleartext within logging repositories, allowing unauthorized actors with log access to retrieve valid authentication credentials.

MitigationUpgrade Tableau Server to a patched version (2022.1.3+, 2021.4.8+, 2021.3.13+, 2021.2.14+, 2021.1.16+, or 2020.4.19+) and rotate any PATs that may have been exposed in logs.

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:>= 2020.4, < 2020.4.19>= 2021.1, < 2021.1.16>= 2021.2, < 2021.2.14>= 2021.3, < 2021.3.13>= 2021.4, < 2021.4.8>= 2022.1, < 2022.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Determine installed Tableau Server version
    Run 'tsm version' from the Tableau Services Manager command line on the server, or check the Tableau Server Admin Portal under 'About Tableau Server'
    Affected if Version is 2020.4.x before 2020.4.19, 2021.1.x before 2021.1.16, 2021.2.x before 2021.2.14, 2021.3.x before 2021.3.13, 2021.4.x before 2021.4.8, or 2022.1.x before 2022.1.3
  2. Verify Personal Access Token usage exists
    Check Tableau Server for active PATs via 'tabcmd gettoken' or through the Tableau Server Admin UI under 'Personal Access Tokens' settings
    Affected if Any Personal Access Tokens have been created or used in the environment
  3. Inspect log repositories for credential patterns
    Search Tableau log directories (default location: C:\ProgramData\Tableau\Tableau Server\data\tabsvc\logs on Windows or /var/opt/tableau/tableau_server/data/tabsvc/logs on Linux) for plaintext token strings using grep or a text search for patterns resembling base64-encoded or raw PAT values
    Affected if Log files contain cleartext Personal Access Token values or recognizable PAT identifiers

Environment is affected if running a vulnerable Tableau Server version (pre-patch) AND Personal Access Tokens were used, with those tokens present in log files.

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 2020.4.19 / 2021.1.16 / 2021.2.14 or later
Fixed in 2020.4.192021.1.162021.2.14
Interim mitigation

Upgrade Tableau Server to a patched version (2022.1.3+, 2021.4.8+, 2021.3.13+, 2021.2.14+, 2021.1.16+, or 2020.4.19+) and rotate any PATs that may have been exposed in logs.

Recommended fix High confidence

Upgrade to 2022.1.3 or later (or the latest 2021.4.x/2021.3.x patch for your branch: 2020.4.19, 2021.1.16, 2021.2.14, or 2021.3.13)

  1. 1. Identify the current Tableau Server version by checking the server or using Tableau Server Administration.
  2. 2. Determine which version branch your current installation is on (2020.4.x, 2021.1.x, 2021.2.x, or 2021.3.x).
  3. 3. Back up the Tableau Server repository (PostgreSQL) and all configuration files before upgrading.
  4. 4. Download the appropriate fixed version installer from the Tableau help.salesforce.com portal or Tableau download archives.
  5. 5. Run the installer on the primary node first, following standard Tableau Server upgrade procedures.
  6. 6. Wait for the upgrade to complete and verify all services are running.
  7. 7. On additional nodes in a distributed deployment, run the upgrade installer sequentially.
  8. 8. After upgrade, verify that logging no longer captures PAT credentials by reviewing new log entries.
Caveat Standard Tableau Server upgrade considerations apply - review compatibility with existing customizations, connectors, and ensure adequate downtime window for the migration

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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