dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-52453

HIGH · 8.2 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 →
88/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 on Windows, Linux (Flow Data Source 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 Salesforce Tableau Server's Flow Data Source modules on Windows and Linux allows attackers to make the server perform unauthorized requests to internal or external resources, enabling resource location spoofing and potential access to internal services.

MitigationUpgrade Tableau Server to version 2025.1.3, 2024.2.12, or 2023.3.19 or later to resolve the SSRF vulnerability in Flow Data Source 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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/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. Identify Tableau Server installed version
    Run 'tsm version' from the Tableau Services Manager command line, or check the Tableau Server installation directory for version information typically found in the About dialog or installation logs
    Affected if The installed version is less than 2023.3.19, OR is 2024.2.x but less than 2024.2.12, OR is 2025.1.x but less than 2025.1.3
  2. Confirm Flow Data Source module usage
    Review Tableau Server logs or configuration files for evidence of Flow Data Source connections being created or executed. Check if users have permissions to create or run flows that connect to external data sources
    Affected if Flow Data Source modules are actively used or enabled on the server, as the SSRF vulnerability resides specifically in these modules
  3. Check network configuration for external data connections
    Examine Tableau Server's data source connection settings and outbound network rules. Look for any external or remote data source configurations that could be exploited through SSRF
    Affected if The server allows outbound HTTP/HTTPS connections from Flow Data Source modules to arbitrary URLs, as this is the attack vector for the SSRF flaw
  4. Review recent network access logs
    Analyze Tableau Server access logs and proxy logs for unusual outbound requests, particularly to unexpected or attacker-controlled domains originating from flow execution processes
    Affected if Unusual or unauthorized outbound requests are present, indicating potential exploitation attempts or successful SSRF attacks

You are affected if Tableau Server is running any version below 2023.3.19, between 2024.2.0-2024.2.11, or between 2025.1.0-2025.1.2 AND Flow Data Source modules are enabled or in use on your server.

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 resolve the SSRF vulnerability in Flow Data Source modules.

Recommended fix High confidence

2023.3.19 (for 2023.x branch), 2024.2.12 (for 2024.2.x branch), or 2025.1.3 (for 2025.1.x branch) - choose the appropriate version based on your current branch

  1. 1. Identify the current Tableau Server version by checking About Tableau Server in the UI or running 'tsm version' command
  2. 2. Determine which upgrade path applies based on current version: if <2023.3.19 upgrade to 2023.3.19 or later; if >=2024.2 and <2024.2.12 upgrade to 2024.2.12 or later; if >=2025.1 and <2025.1.3 upgrade to 2025.1.3 or later
  3. 3. Create a full backup of the Tableau Server repository, workgroup, and files using Tableau Server Management (TSM) or manual backup procedures
  4. 4. Download the appropriate fixed version installer from help.salesforce.com or the Tableau website
  5. 5. Run the upgrade installer on the Tableau Server, following the standard upgrade documentation for your operating system (Windows or Linux)
  6. 6. After upgrade completes, verify the server is running and check that all services are healthy using TSM: tsm status
  7. 7. Confirm the installed version matches the expected fixed release using 'tsm version'
Caveat Review Tableau release notes for the target version as there may be feature changes or deprecated functionalities between major releases; ensure compatibility with existing workbooks and data sources

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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