dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-26497

HIGH · 7.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 →
82/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
Unrestricted Upload of File with Dangerous Type vulnerability in Salesforce Tableau Server on Windows, Linux (Flow Editor modules) allows Absolute Path Traversal.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

Unrestricted file upload vulnerability with absolute path traversal in Tableau Server's Flow Editor modules on Windows and Linux. An attacker can upload files with dangerous types to arbitrary filesystem locations, potentially achieving remote code execution or system compromise.

MitigationUpgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 or later to remediate this vulnerability.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Check installed Tableau Server version on Windows
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Tableau\Tableau Server\, or check the version from Add/Remove Programs. Alternatively, open Tableau Server Repository and run: SELECT * FROM versions
    Affected if The version is less than 2023.3.19, or is 2024.2.x before 2024.2.12, or is 2025.1.x before 2025.1.3
  2. Check installed Tableau Server version on Linux
    Run command: tsm version or check the package version using rpm -q tableau-server or dpkg -l tableau-server
    Affected if The version is less than 2023.3.19, or is 2024.2.x before 2024.2.12, or is 2025.1.x before 2025.1.3
  3. Verify Flow Editor module is accessible
    Log into Tableau Server as an administrator, navigate to the Server Settings or Explore section, and confirm whether Flow functionality is enabled. Check for the presence of Flows in the navigation pane or attempt to access the Flow Runner/Editor interface at /flows/
    Affected if Flow Editor modules are enabled and accessible to users on the server

You are affected if your Tableau Server version falls within any of these ranges: < 2023.3.19, >= 2024.2 but < 2024.2.12, or >= 2025.1 but < 2025.1.3 AND Flow Editor functionality is enabled on your Windows or Linux installation.

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 remediate this vulnerability.

Recommended fix High confidence

Tableau Server 2025.1.3 (or 2024.2.12 / 2023.3.19 minimum per respective branch)

  1. Back up the current Tableau Server installation, including the data directory and configuration files
  2. Review the Tableau Server upgrade documentation for your current version to ensure compatibility
  3. Download the appropriate fixed version from Salesforce/Tableau: 2025.1.3 or later, 2024.2.12 or later, or 2023.3.19 or later
  4. Stop all Tableau Server services before beginning the upgrade
  5. Run the Tableau Server installer for the chosen fixed version
  6. Follow the on-screen upgrade wizard, selecting the upgrade option to preserve existing data and configurations
  7. After installation completes, verify all Tableau Server services start successfully
  8. Validate that the Flow Editor modules are functioning correctly and the vulnerability is resolved
Caveat Review Tableau Server release notes for the target version to check for any breaking changes or deprecated features before upgrading

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,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 $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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