CVE-2022-26656
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 before 27.3 allows remote attackers to trigger a software abort, and possibly enumerate usernames, via One Touch Join.
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 before version 27.3 contains a vulnerability in the One Touch Join feature that allows remote attackers to cause a software abort (denial of service) and potentially enumerate valid usernames by sending specially crafted requests through the One Touch Join interface.
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< 27.3CVSS 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
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 your systems for the presence of Pexip Infinity video conferencing platform. This is typically deployed as a virtual machine or appliance in enterprise environments.Affected if Pexip Infinity software is found on the system
-
Determine installed Pexip Infinity versionAccess the Pexip Infinity admin interface or use system commands to retrieve the installed version number. Compare against the affected range: versions before 27.3 are vulnerable.Affected if Installed version is lower than 27.3
-
Check if One Touch Join feature is enabledAccess the Pexip Infinity admin interface and navigate to the One Touch Join settings panel. Verify whether this feature is currently enabled for any users or conferences.Affected if One Touch Join feature is enabled and version is below 27.3
A Pexip Infinity installation is affected if it is running any version lower than 27.3 with the One Touch Join feature enabled.
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 · scoped27.3
Upgrade Pexip Infinity to version 27.3 or later to remediate this vulnerability.
27.3
- 1. Log in to the Pexip Infinity admin interface
- 2. Navigate to the version or system status section to confirm current deployment version
- 3. Review the Pexip upgrade documentation at docs.pexip.com for your deployment type
- 4. Plan maintenance window as upgrades may require service restart
- 5. Download and apply Pexip Infinity version 27.3 or later
- 6. After upgrade, verify the One Touch Join functionality is working correctly
- 7. Confirm the new version is displayed correctly in the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26656 — 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-2022-26656 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