CVE-2025-48704
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 · uneditedPexip Infinity 35.0 through 37.2 before 38.0 has Improper Input Validation in signalling that allows an attacker to trigger a software abort, resulting in 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 · moderate confidencePexip Infinity versions 35.0 through 37.2 contain improper input validation in the signalling component. An attacker can send specially crafted signalling messages that trigger a software abort, causing a denial of service condition.
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>= 35.0, < 38.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Pexip Infinity is installedCheck system for Pexip Infinity installation. Common locations: /opt/pexip/ or check for pexip services via 'systemctl list-units | grep pexip' or 'ps aux | grep pexip'Affected if Pexip Infinity is not found on the system
-
Determine installed Pexip Infinity versionRun command to check version, typically via admin CLI: 'show version' or check /opt/pexip/version file if accessible. May also check via management interface.Affected if Version cannot be determined or is not Pexip Infinity
-
Compare version against affected rangeCheck if installed version falls within >= 35.0 and < 38.0. If version is 35.0, 35.x, 36.x, 37.0, 37.1, or 37.2, it is in the affected range.Affected if Installed version is 35.0 through 37.2 inclusive
-
Confirm signalling component is activeVerify the Pexip signalling service is running. Check via 'systemctl status pexip-signalling' or equivalent service status command for your deployment.Affected if Signalling service is running and accessible to network traffic
User is affected if Pexip Infinity version 35.0 through 37.2 is installed and the signalling component is active and reachable.
Generated from the published advisory. Verify against your own configuration.
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 · scoped38.0
Upgrade Pexip Infinity to version 38.0 or later to address the input validation vulnerability.
38.0
- Verify the current Pexip Infinity version by accessing the admin interface or using the management API
- Review the Pexip upgrade documentation at docs.pexip.com for the upgrade procedure
- Create a backup of the current Pexip Infinity configuration
- Schedule a maintenance window for the upgrade
- Follow the documented upgrade process to upgrade to version 38.0
- Verify the upgrade was successful and the service is functioning normally
- Monitor the system logs to confirm the vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-48704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-48704 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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