dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2025-15097

HIGH · 7.3 CVSS v3.1 Published 2025-12-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A vulnerability was found in Alteryx Server. Affected by this issue is some unknown functionality of the file /gallery/api/status/. Performing manipulation results in improper authentication. The attack is possible to be carried out remotely. The exploit has been made public and could be used. Upgrading to version 2023.1.1.13.486, 2023.2.1.10.293, 2024.1.1.9.236, 2024.2.1.6.125 and 2025.1.1.1.31 can resolve this issue. Upgrading the affected component is recommended.

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

Alteryx Server contains an authentication bypass vulnerability in the /gallery/api/status/ API endpoint. The issue allows remote attackers to access the endpoint without proper authentication, potentially exposing sensitive server status information or enabling further attacks.

MitigationUpgrade Alteryx Server to one of the fixed versions (2023.1.1.13.486, 2023.2.1.10.293, 2024.1.1.9.236, 2024.2.1.6.125, or 2025.1.1.1.31) to resolve the improper authentication vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 Alteryx Server installation
    Check for Alteryx Server by reviewing installed programs in Windows Control Panel > Programs and Features, or look for the Alteryx Service in Windows Services (services.msc)
    Affected if Alteryx Server is not installed on the system
  2. Determine installed Alteryx Server version
    Log into the Alteryx Server UI as an administrator, then navigate to Help > About to view the version information. Alternatively, check the installation directory for version files or the Alteryx Service properties in Windows Services
    Affected if The installed version falls before 2023.1.1.13.486, 2023.2.1.10.293, 2024.1.1.9.236, 2024.2.1.6.125, or 2025.1.1.1.31 (i.e., versions 2023.1.x before .13, 2023.2.x before .10, 2024.1.x before .9, 2024.2.x before .6, or 2025.1.x before .31)
  3. Verify endpoint accessibility
    Send an unauthenticated HTTP GET request to the /gallery/api/status/ endpoint using a tool like curl or a browser: http(s)://<server_hostname>/gallery/api/status/ - observe whether the request returns a successful response without providing any login credentials
    Affected if The endpoint returns HTTP 200 with server status data or any sensitive information without requiring authentication

The environment is affected if Alteryx Server is installed with a version prior to the fixed releases AND the /gallery/api/status/ endpoint responds to unauthenticated requests with sensitive data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Alteryx Server to one of the fixed versions (2023.1.1.13.486, 2023.2.1.10.293, 2024.1.1.9.236, 2024.2.1.6.125, or 2025.1.1.1.31) to resolve the improper authentication vulnerability.

Recommended fix High confidence

2025.1.1.1.31 (or any of: 2023.1.1.13.486, 2023.2.1.10.293, 2024.1.1.9.236, 2024.2.1.6.125)

  1. Download the appropriate installer for your current version from the Alteryx Customer Portal or official download channels
  2. Backup your Alteryx Server data and configuration before upgrading
  3. Stop the Alteryx Server service
  4. Run the installer for the fixed version (2023.1.1.13.486, 2023.2.1.10.293, 2024.1.1.9.236, 2024.2.1.6.125, or 2025.1.1.1.31)
  5. Follow the on-screen installation prompts
  6. After installation completes, restart the Alteryx Server service
  7. Verify the /gallery/api/status/ endpoint now requires proper authentication
  8. Confirm normal server functionality after upgrade
Caveat Review Alteryx release notes for your specific version jump for any deprecation notices or migration requirements

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

Have this fixed 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 help mitigating

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-15097 — 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-15097 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