dbcve.org
Pexip InfinityApplication · Pexip

CVE-2025-66378

HIGH · 7.5 CVSS v3.1 Published 2025-12-25
Fix available
A fix is available. Upgrade to 39.0 or later.
See remediation →
84/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
Pexip Infinity 38.0 and 38.1 before 39.0 has insufficient access control in the RTMP implementation, allowing an attacker to disconnect RTMP streams traversing a Proxy Node.

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 · moderate confidence

Pexip Infinity versions 38.0 and 38.1 contain insufficient access control in the RTMP implementation. This allows an unauthenticated attacker to disconnect RTMP streams traversing a Proxy Node by sending specially crafted network packets, causing service disruption for media streams.

MitigationUpgrade Pexip Infinity to version 39.0 or later to obtain the access control fix. Review RTMP stream configurations and monitor for unauthorized disconnect attempts until patching is complete.

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:>= 38.0, < 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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify the installed Pexip Infinity version
    Access the Pexip Infinity admin interface or use the management API to retrieve the current software version. Compare this version against the affected range: version 38.0 or 38.1, or any version >= 38.0 but < 39.0.
    Affected if The installed version falls within 38.0 to 38.1 inclusive, or any 38.x release prior to 39.0.
  2. Determine if RTMP functionality is in use
    Review the Pexip Infinity deployment configuration to identify whether RTMP streaming or RTMP ingress/egress is enabled. Check the Proxy Node settings for RTMP stream configurations.
    Affected if RTMP streaming is configured and active on any Proxy Node in the deployment.
  3. Confirm Proxy Node deployment
    Verify that Proxy Nodes are part of the Pexip Infinity architecture, as the vulnerability specifically affects RTMP streams traversing Proxy Nodes.
    Affected if Proxy Nodes are deployed and handling media traffic in the environment.
  4. Review for RTMP disconnect events
    Examine system logs, RTMP service logs, and Proxy Node event logs for unusual or unauthorized RTMP stream disconnection events occurring from external sources.
    Affected if Logs show unexpected RTMP stream disconnects originating from unauthenticated or unexpected network sources.
  5. Inspect RTMP access control settings
    Check the RTMP implementation configuration in the admin interface to determine if access control restrictions are properly configured for incoming RTMP connections.
    Affected if RTMP access controls are missing, weak, or improperly configured.

A user is affected if their Pexip Infinity deployment runs version 38.0 or 38.1 (or any version >= 38.0 but < 39.0), has RTMP streaming enabled, and includes Proxy Nodes handling RTMP traffic.

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 obtain the access control fix. Review RTMP stream configurations and monitor for unauthorized disconnect attempts until patching is complete.

Recommended fix High confidence

39.0 or later

  1. Upgrade Pexip Infinity from version 38.0 or 38.1 to version 39.0 or later to resolve the insufficient access control vulnerability in the RTMP implementation

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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