CVE-2025-49088
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 32.0 through 37.1 before 37.2, in certain configurations of OTJ (One Touch Join) for Teams SIP Guest Join, has Improper Input Validation in the OTJ service, allowing a remote attacker to trigger a software abort via a crafted calendar invite, leading to 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 · high confidencePexip Infinity versions 32.0 through 37.1 contain an improper input validation vulnerability in the OTJ (One Touch Join) service for Teams SIP Guest Join. A remote attacker can exploit this by sending a crafted calendar invite containing malicious input, triggering a software abort and causing 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>= 32.0, < 37.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Check Pexip Infinity installed versionLog into the Pexip Infinity admin interface and navigate to Platform > System > About, or use the CLI command 'show system information' to retrieve the current software version.Affected if The installed version is 32.0, 32.1, 32.2, 33.0, 33.1, 34.0, 34.1, 35.0, 35.1, 36.0, 36.1, 37.0, or 37.1 (any version >= 32.0 and < 37.2).
-
Verify if OTJ service for Teams is enabledIn the Pexip Infinity admin interface, navigate to Services > One Touch Join or Platform > Services > OTJ, and check whether the One Touch Join service is enabled and configured for Microsoft Teams integration.Affected if The OTJ service is enabled and configured for Teams SIP Guest Join; the vulnerability only applies when this feature is active.
-
Check for Teams SIP Guest Join configurationNavigate to Conferencing > Deployments or Services > Teams integration settings and examine whether any SIP Guest Join policies or rules are defined that accept calendar invites from external sources.Affected if SIP Guest Join for Teams is configured and accepts incoming calendar invites from untrusted sources.
You are affected if your Pexip Infinity version is 32.0 through 37.1 AND the OTJ service for Teams SIP Guest Join is enabled and processing calendar invites.
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.2
Upgrade Pexip Infinity to version 37.2 or later to remediate this vulnerability. Consider implementing network segmentation and filtering for calendar invite traffic to reduce attack surface pending the upgrade.
37.2
- Upgrade Pexip Infinity to version 37.2 or later
- After upgrade, verify the OTJ (One Touch Join) service for Teams SIP Guest Join is functioning correctly
- Confirm the vulnerability is resolved by testing with crafted calendar invites or reviewing release notes for 37.2
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-49088 — 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-49088 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