dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-52455

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-25
Fix available
A fix is available. Upgrade to 2023.3.19 / 2024.2.12 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Server-Side Request Forgery (SSRF) vulnerability in Salesforce Tableau Server on Windows, Linux (EPS Server modules) allows Resource Location Spoofing. 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

Server-Side Request Forgery (SSRF) vulnerability in Tableau Server's EPS Server modules on Windows and Linux allows attackers to make the server perform unintended requests to internal or external resources, enabling resource location spoofing. This network-exploitable flaw with low attack complexity could allow enumeration of internal services or exfiltration of data through the compromised server.

MitigationUpgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 or later to remediate this SSRF 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify Tableau Server is installed
    Check for Tableau Server installation by looking for the 'Tableau Server' service in Windows Services or by running 'tsm status' command in Linux/Windows command line
    Affected if Tableau Server is not installed on the system
  2. Determine installed Tableau Server version
    Run 'tsm version' from the Tableau Server bin directory, or check the version from the Tableau Server Configuration utility under 'About Tableau Server'
    Affected if Version cannot be determined or is in an affected range (< 2023.3.19, >= 2024.2 but < 2024.2.12, >= 2025.1 but < 2025.1.3)
  3. Check if EPS Server module is enabled
    Inspect the Tableau Server configuration by running 'tsm configuration get' for settings related to EPS (External Protocol Service) or review the tableaueps.conf file in the config directory if present
    Affected if EPS Server module is enabled and configured on the server
  4. Compare version against affected ranges
    Parse the version number from step 2 and compare: any version < 2023.3.19, or >= 2024.2 but < 2024.2.12, or >= 2025.1 but < 2025.1.3 is affected
    Affected if Installed version falls into any of the three affected ranges

A system is affected if Tableau Server with the EPS Server module enabled is running a version that falls below 2023.3.19, below 2024.2.12 (for 2024.2 branch), or below 2025.1.3 (for 2025.1 branch).

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 SSRF vulnerability.

Recommended fix High confidence

Tableau Server 2023.3.19 (or later 2023.x LTS), 2024.2.12 (or later 2024.2.x), or 2025.1.3 (or later 2025.1.x) depending on your release track

  1. Identify your current Tableau Server version via Tableau Server Manager or 'tsm version' command
  2. If running version < 2023.3.19: Upgrade to Tableau Server 2023.3.19 or later in the 2023.x LTS line
  3. If running version >= 2024.2 and < 2024.2.12: Upgrade to Tableau Server 2024.2.12 or later in the 2024.2.x line
  4. If running version >= 2025.1 and < 2025.1.3: Upgrade to Tableau Server 2025.1.3 or later in the 2025.1.x line
  5. After upgrade, verify the new version is running via 'tsm version'
  6. Review Tableau Server post-upgrade documentation for any configuration changes required
Caveat Standard Tableau Server upgrade considerations apply: test in non-production environment first, backup databases, review deprecated features in release notes

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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