dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-26494

HIGH · 7.7 CVSS v3.1 Published 2025-02-11
Fix available
A fix is available. Upgrade to after 2023.3.5 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable 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
Server-Side Request Forgery (SSRF) vulnerability in Salesforce Tableau Server allows Authentication Bypass.This issue affects Tableau Server: from 2023.3 through 2023.3.5.

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

Server-Side Request Forgery (SSRF) vulnerability in Tableau Server allows attackers to make the server perform unauthorized requests to internal or external resources, potentially bypassing authentication mechanisms. This affects versions 2023.3 through 2023.3.5.

MitigationApply the vendor-released patch by upgrading Tableau Server to the latest patched version (2023.3.6 or later) to remediate this SSRF authentication bypass 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, <= 2023.3.5

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Confirm Tableau Server installation
    Check if Tableau Server is installed on the system by looking for the Tableau Server processes or checking for the installation directory (commonly at C:\Program Files\Tableau\Tableau Server on Windows or /opt/tableau/tableau_server on Linux).
    Affected if Tableau Server is installed and running on the system.
  2. Identify installed Tableau Server version
    Open Tableau Server Administrator UI and navigate to the About page, or run the command 'tsm version' from the Tableau Services Manager command line if available, to retrieve the exact version number.
    Affected if The installed version is 2023.3, 2023.3.1, 2023.3.2, 2023.3.3, 2023.3.4, or 2023.3.5.
  3. Verify version against affected range
    Compare the identified version number against the affected range: versions greater than or equal to 2023.3 and less than or equal to 2023.3.5.
    Affected if The version falls within 2023.3 through 2023.3.5 inclusive.

The environment is affected if Tableau Server is running any version between 2023.3 and 2023.3.5 inclusive, as these versions contain the SSRF vulnerability.

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.

From vendor data
Upgrade available Upgrade to a release after 2023.3.5
Interim mitigation

Apply the vendor-released patch by upgrading Tableau Server to the latest patched version (2023.3.6 or later) to remediate this SSRF authentication bypass vulnerability.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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