dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-26496

CRITICAL · 9.3 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 2023.3.19 / 2024.2.12 or later.
See remediation →
98/100
Remediation priority · Urgent
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
Access of Resource Using Incompatible Type ('Type Confusion') vulnerability in Salesforce Tableau Server, Tableau Desktop on Windows, Linux (File Upload modules) allows Local Code Inclusion.This issue affects Tableau Server, Tableau Desktop: 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

A type confusion vulnerability in Tableau's file upload modules allows attackers to bypass type checking and inject malicious code that gets executed locally on the affected system. This occurs due to improper type validation during the file upload process, enabling local code inclusion and potential full system compromise.

MitigationUpgrade Tableau Server and Desktop installations to versions 2025.1.3, 2024.2.12, or 2023.3.19 or later to address the type confusion vulnerability in file upload 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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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. Identify if Tableau Server is installed
    Check for Tableau Server processes or installation directories. On Windows, look for 'Tableau Server' in Programs and Features or check for the 'tabadmin' or 'tsm' command-line tools in the installation path (typically C:\Program Files\Tableau\Tableau Server). On Linux, check for /tableau_server directory or run 'tsm status'.
    Affected if Tableau Server is found installed on the system
  2. Determine the installed Tableau Server version
    Run 'tsm version' from the Tableau Server bin directory, or on Windows check the version in the Control Panel > Programs and Features > Tableau Server, or view the version in the Tableau Server Configuration utility under Server Status.
    Affected if The installed version is less than 2023.3.19, or between 2024.2.0 and 2024.2.11 inclusive, or between 2025.1.0 and 2025.1.2 inclusive
  3. Check if file upload functionality is enabled
    Review Tableau Server configuration settings for file upload modules. Access the Tableau Server Repository (typically in the 'workgroup' database) and query the 'data_connections' or 'upload_settings' tables for upload-related configuration flags. Alternatively, check via TSM: 'tsm configuration get -k features.allowUploads' or similar upload-related keys.
    Affected if File upload modules are enabled and accessible to users
  4. Verify the file type validation configuration
    Examine the Tableau Server file upload configuration files (such as tabmon.xml or upload settings in the Tableau Server Repository). Look for the 'AllowNetFile' or 'NetFile' settings in the server's configuration. Check if strict file type enforcement is disabled.
    Affected if Type validation is disabled or set to permissive mode, allowing file type bypass

A user is affected if Tableau Server is installed with a version matching the affected ranges AND file upload modules are enabled, allowing untrusted file uploads to be processed.

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 and Desktop installations to versions 2025.1.3, 2024.2.12, or 2023.3.19 or later to address the type confusion vulnerability in file upload modules.

Recommended fix High confidence

Tableau Server/Desktop: upgrade to 2025.1.3, 2024.2.12, or 2023.3.19 (whichever is applicable based on your release track)

  1. 1. Identify the current installed version of Tableau Server or Tableau Desktop
  2. 2. If running Tableau Server < 2023.3.19, plan upgrade to 2023.3.19 or later
  3. 3. If running Tableau Server >= 2024.2 and < 2024.2.12, plan upgrade to 2024.2.12 or later
  4. 4. If running Tableau Server >= 2025.1 and < 2025.1.3, plan upgrade to 2025.1.3 or later
  5. 5. For Tableau Desktop on Windows or Linux (File Upload modules), apply the same version-based fixes
  6. 6. Schedule maintenance window for upgrade process
  7. 7. Backup existing Tableau data and configurations
  8. 8. Execute upgrade following Salesforce/Tableau official documentation

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
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,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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