dbcve.org
Tableau ServerApplication · Tableau

CVE-2025-52454

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 (Amazon S3 Connector 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

This is a Server-Side Request Forgery (SSRF) vulnerability in the Amazon S3 Connector modules of Tableau Server running on Windows and Linux. The flaw allows attackers to spoof resource locations, potentially causing the Tableau Server to make unintended requests to attacker-controlled endpoints. This could lead to data exfiltration, internal network reconnaissance, or bypassing network restrictions.

MitigationUpgrade Tableau Server to version 2025.1.3 or later, 2024.2.12 or later, or 2023.3.19 or later to remediate this vulnerability. Until patches are applied, restrict network access to the S3 connector endpoints and monitor for unusual outbound requests.

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 installed Tableau Server version
    On Windows, check via Tableau Server Manager or run 'tsm version'. On Linux, run 'tsm version' or check /opt/tableau/tableau_server/version.txt
    Affected if The installed version falls into any of these ranges: < 2023.3.19, >= 2024.2 but < 2024.2.12, or >= 2025.1 but < 2025.1.3
  2. Determine if Amazon S3 Connector is configured
    Check Tableau Server repository settings or look for S3 connection configurations in the Tableau Server data source connections. On Windows, inspect via Tableau Server Manager or Repository. On Linux, check /var/opt/tableau/tableau_server/data/ for S3-related configuration files.
    Affected if The Amazon S3 Connector module is enabled or configured to connect to S3 buckets, making the SSRF flaw exploitable
  3. Verify S3 connector endpoints are accessible
    Review network configuration and firewall rules controlling outbound connections from the Tableau Server to AWS S3 endpoints (typically *.s3.amazonaws.com)
    Affected if The server can make outbound HTTP/HTTPS requests to arbitrary URLs, which would allow the SSRF to reach attacker-controlled endpoints

You are affected if your Tableau Server version is in one of the vulnerable ranges AND the Amazon S3 Connector is enabled or configured on your instance.

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 or later, 2024.2.12 or later, or 2023.3.19 or later to remediate this vulnerability. Until patches are applied, restrict network access to the S3 connector endpoints and monitor for unusual outbound requests.

Recommended fix High confidence

Tableau Server 2025.1.3 or later (or 2024.2.12+ / 2023.3.19+ if staying on older branches)

  1. 1. Back up your current Tableau Server installation, including all databases and configuration files.
  2. 2. Review the Tableau Server upgrade documentation for your current version at help.salesforce.com.
  3. 3. Download the appropriate fixed version: 2025.1.3 (or later), 2024.2.12 (or later), or 2023.3.19 (or later) from the official Tableau/Salesforce distribution site.
  4. 4. Run the Tableau Server installer/upgrade executable on your Windows or Linux server.
  5. 5. Follow the on-screen prompts, ensuring you select the upgrade option rather than a fresh install.
  6. 6. After upgrade completes, verify the Amazon S3 Connector modules are functioning correctly.
  7. 7. Confirm the Tableau Server services are running and the web interface is accessible.
  8. 8. Test that external resource connections (especially S3) work as expected to verify the SSRF fix.
Caveat Review release notes before upgrading - major version upgrades may introduce configuration or feature changes that require adjustment

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

Fix this in Tableau Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,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 $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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