dbcve.org
Pexip InfinityApplication · Pexip

CVE-2025-66377

HIGH · 7.5 CVSS v3.1 Published 2025-12-25
Fix available
A fix is available. Upgrade to 39.0 or later.
See remediation →
80/100
Remediation priority · High
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 before 39.0 has Missing Authentication for a Critical Function in a product-internal API, allowing an attacker (who already has access to execute code on one node within a Pexip Infinity installation) to impact the operation of other nodes within the installation.

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 before version 39.0 contains a missing authentication vulnerability in a product-internal API. An attacker who has already achieved code execution on one node within a Pexip Infinity installation can exploit this unauthenticated internal API to impact the operation of other nodes in the same installation, enabling lateral movement across the cluster.

MitigationUpgrade Pexip Infinity to version 39.0 or later to remediate this vulnerability. Since the vulnerability assumes prior node compromise, also conduct a security investigation to determine the extent of any existing breach.

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:< 39.0

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Identify Pexip Infinity installation version
    Access the Pexip Infinity admin interface and navigate to the Dashboard or System > About page to view the installed software version. Alternatively, use the command line on a Pexip node: pexctl status or check /opt/pexip/etc/version if accessible.
    Affected if The displayed version number is below 39.0 (for example, 38.x, 37.x, or earlier).
  2. Verify cluster configuration
    Check if multiple nodes are deployed in the Pexip Infinity installation by accessing the admin interface under Platform > Nodes or by running pexctl show nodes on the command line.
    Affected if Multiple nodes exist in the cluster and the version is below 39.0, as the vulnerability enables lateral movement between nodes.
  3. Confirm internal API accessibility
    Review network segmentation between Pexip nodes. The product-internal API used for inter-node communication should be accessible within the cluster network. This is the default state for Pexip Infinity clusters.
    Affected if Inter-node communication is permitted and the version is below 39.0, allowing exploitation of the unauthenticated internal API.

You are affected if your Pexip Infinity installation is running any version prior to 39.0 and an attacker has already achieved code execution on at least one node in the cluster, enabling them to move laterally via the unauthenticated internal API.

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

Upgrade Pexip Infinity to version 39.0 or later to remediate this vulnerability. Since the vulnerability assumes prior node compromise, also conduct a security investigation to determine the extent of any existing breach.

Recommended fix High confidence

Pexip Infinity 39.0 or later

  1. 1. Back up your Pexip Infinity configuration and data before upgrading.
  2. 2. Review the official Pexip upgrade documentation at docs.pexip.com for your current version.
  3. 3. Plan your upgrade window, ensuring sufficient downtime for the migration.
  4. 4. Upgrade Pexip Infinity to version 39.0 or later.
  5. 5. After upgrade, verify that the product-internal API now properly requires authentication between nodes.
  6. 6. Confirm all nodes in the installation are running the updated version and are functioning correctly.

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

Fix this in Pexip Infinity Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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