CVE-2025-30080
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 · uneditedSignalling in Pexip Infinity 29 through 36.2 before 37.0 has improper input validation that allows remote attackers to trigger a temporary denial of service (software abort).
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 confidencePexip Infinity versions 29 through 36.2 contain improper input validation in the signalling component, allowing remote unauthenticated attackers to send specially crafted signals that trigger a software abort, resulting in temporary denial of service.
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>= 29.0, < 37.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.
-
Identify if Pexip Infinity is deployedCheck your installed applications or use system inventory tools to locate Pexip Infinity. Common locations include /opt/pexip or check for the 'pexip' service via 'systemctl list-units --type=service | grep pexip'Affected if Pexip Infinity software is found on the system
-
Determine the installed Pexip Infinity versionRun 'pexip --version' or check the admin interface under 'About' or 'System Information'. Alternatively, inspect /opt/pexip/version if accessible.Affected if The version returned is blank, unreadable, or cannot be determined
-
Compare installed version to affected rangeCheck the version number against the affected range: version >= 29.0 and < 37.0. For example, versions 29.0, 29.1, 30.0, 31.5, 36.0, 36.2 are all within the affected range.Affected if The installed version is 29.0 or higher but lower than 37.0
-
Assess signalling component exposureReview firewall rules and network configuration to determine if the signalling component (typically port 443 or 8443) is accessible from untrusted or public networks. Check network segmentation and ACLs.Affected if Signalling ports are exposed to untrusted networks without proper filtering
You are affected if Pexip Infinity version 29.0 through 36.2 (or any version < 37.0) is installed and its signalling component is network-accessible to untrusted parties.
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 · scoped37.0
Upgrade Pexip Infinity to version 37.0 or later to remediate this vulnerability. Organizations should also consider network segmentation and firewall rules to limit signalling exposure to untrusted networks.
Pexip Infinity 37.0
- Upgrade Pexip Infinity to version 37.0 or later to resolve the improper input validation vulnerability
- Verify the upgrade by reviewing the Pexip Infinity admin interface or release notes at docs.pexip.com
- Confirm the signalling service is functioning normally after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.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-30080 — 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-30080 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