dbcve.org
Pexip InfinityApplication · Pexip

CVE-2025-59683

CRITICAL · 9.1 CVSS v3.1 Published 2025-12-25
Fix available
A fix is available. Upgrade to 38.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Pexip Infinity 15.0 through 38.0 before 38.1 has Improper Access Control in the Secure Scheduler for Exchange service, when used with Office 365 Legacy Exchange Tokens. This allows a remote attacker to read potentially sensitive data and excessively consume resources, leading to a denial of service.

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

Pexip Infinity versions 15.0 through 38.0 contain improper access control in the Secure Scheduler for Exchange service when used with Office 365 Legacy Exchange Tokens. A remote attacker can exploit this to read potentially sensitive data and cause denial of service through excessive resource consumption.

MitigationUpgrade Pexip Infinity to version 38.1 or later to remediate this vulnerability. Given the critical severity (CVSS 9.1) involving both data disclosure and DoS, prioritize this upgrade immediately.

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
Pexip InfinityApplication
Affected:>= 15, < 38.1

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
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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. Determine your Pexip Infinity version
    Access the Pexip Infinity admin interface and navigate to the system information or about section to identify the installed software version
    Affected if The version displayed is 15.x, 16.x, 17.x, 18.x, 19.x, 20.x, 21.x, 22.x, 23.x, 24.x, 25.x, 26.x, 27.x, 28.x, 29.x, 30.x, 31.x, 32.x, 33.x, 34.x, 35.x, 36.x, 37.x, or 38.0 (anything from 15 through 38.0 inclusive)
  2. Verify if Secure Scheduler for Exchange is configured
    In the Pexip Infinity admin interface, examine the conferencing or scheduling settings to determine if the Secure Scheduler for Exchange feature has been enabled
    Affected if Secure Scheduler for Exchange is enabled and configured for use in your deployment
  3. Confirm Office 365 Legacy Exchange Tokens are in use
    Review the integration or calendar settings within the Pexip Infinity admin interface to check if Office 365 legacy exchange token authentication is configured
    Affected if Office 365 Legacy Exchange Tokens are selected or active as the authentication or synchronization method for calendar integration
  4. Check for unusual data access or resource consumption
    Review system logs and access audit records for any unexpected read operations on scheduling data or excessive API calls to Exchange services that may indicate exploitation
    Affected if Log evidence shows unauthorized access to scheduling data or abnormal resource usage patterns originating from the Secure Scheduler component

You are affected if your Pexip Infinity version is between 15 and 38.0 inclusive AND the Secure Scheduler for Exchange is enabled with Office 365 Legacy Exchange Tokens configured.

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 38.1 or later
Fixed in 38.1
Interim mitigation

Upgrade Pexip Infinity to version 38.1 or later to remediate this vulnerability. Given the critical severity (CVSS 9.1) involving both data disclosure and DoS, prioritize this upgrade immediately.

Recommended fix High confidence

Pexip Infinity 38.1

  1. 1. Review the Pexip Infinity 38.1 release notes for the security update details
  2. 2. Ensure you have a valid backup of your current Pexip Infinity configuration
  3. 3. Download the Pexip Infinity 38.1 release from the Pexip customer portal or official distribution channel
  4. 4. Follow the standard Pexip Infinity upgrade procedure as documented in the official administration guide
  5. 5. After upgrade, verify that the Secure Scheduler for Exchange service is functioning correctly
  6. 6. Confirm the version number shows 38.1 post-upgrade
Caveat No breaking changes expected for this point release upgrade; standard minor version upgrade process applies

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

Fix this in Pexip Infinity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
19.0 hours of engineering $3,300
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,280.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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