Tableau ServerApplication · Tableau

CVE-2025-26498

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 (establish-connection-no-undo 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

This is an unrestricted file upload vulnerability in Tableau Server's 'establish-connection-no-undo' modules that allows absolute path traversal, enabling attackers to write files to arbitrary locations on the filesystem by specifying absolute paths during file upload operations rather than being restricted to a designated upload directory.

MitigationUpgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 (or later) to patch the vulnerability. Alternatively, if immediate patching is not possible, restrict file upload functionality and monitor for suspicious upload requests targeting the connection establishment 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
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. Identify installed Tableau Server version
    Run 'tsm version' or check the Tableau ServerAbout dialog in the UI to retrieve the exact version number installed in your environment
    Affected if The installed version is less than 2023.3.19, or between 2024.2.0-2024.2.11 inclusive, or between 2025.1.0-2025.1.2 inclusive
  2. Confirm the 'establish-connection-no-undo' modules are present
    Inspect the Tableau Server installation directory for the presence of modules named 'establish-connection-no-undo' or similar path traversal-vulnerable components in the data connection or file upload subsystems
    Affected if These modules exist and are accessible within the Tableau Server installation
  3. Verify file upload functionality is enabled
    Check Tableau Server configuration settings (via TSM orAdmin Portal) for data source connection upload or file import features that utilize the vulnerable modules
    Affected if File upload or data source connection import functionality is enabled and accessible to users
  4. Review file upload configurations
    Examine Tableau Server configuration files and connection settings to determine if absolute path specification is allowed for uploads, or if path restrictions are properly enforced
    Affected if The configuration allows absolute path specification in file upload operations without proper validation or restriction

Your environment is affected if the installed Tableau Server version falls within the vulnerable ranges AND the file upload/connection establishment features are enabled and accessible.

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 vulnerability. Alternatively, if immediate patching is not possible, restrict file upload functionality and monitor for suspicious upload requests targeting the connection establishment modules.

Recommended fix High confidence

Tableau Server 2025.1.3 (or 2024.2.12 / 2023.3.19 depending on your version branch)

  1. 1. Back up your Tableau Server data, including the repository, files, and configuration. Refer to Tableau documentation for complete backup procedures.
  2. 2. Download the appropriate Tableau Server installer for your target fixed version (2025.1.3, 2024.2.12, or 2023.3.19) from the Tableau website or Salesforce support portal.
  3. 3. Stop all Tableau Server services before beginning the upgrade process.
  4. 4. Run the installer on the primary node, following the on-screen prompts for an in-place upgrade.
  5. 5. If you have a distributed deployment, run the upgrade on all additional nodes in the correct sequence per Tableau documentation.
  6. 6. After upgrade completes, verify all Tableau Server services start successfully.
  7. 7. Confirm the upgrade by logging into Tableau Server and checking the version information in the About section.
Caveat Review Tableau Server release notes for your target version for any breaking changes or migration requirements before upgrading

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-26498 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