Alert: Vidyo WebRTC for Browsers using Chromium Version 151.0.7922 and later (Fixed)—July 30, 2026

Update: Fix has been identified and deployed

  • This issue has been addressed by VidyoConnect WebRTC version 26.1.1 and SDK version 26.1.1.0004.
  • You can find the release notes for WebRTC here and the VidyoPlatform JavaScript SDK here.
  • Cloud customers have already been updated with the latest build. Downloads are available for on-premises customers at our download site.

Which products are affected?

  • VidyoConnect for WebRTC (all versions) on browsers using Chromium Versions 151 and later. This includes Chrome version 151.0.7922.72 or later for Windows and macOS and Microsoft Edge version 151.0.4129.50 and later for Windows and macOS.
  • VidyoPlatform JavaScript SDK on browsers using Chromium Versions 151 and later. This includes Chrome version 151.0.7922.72 or later for Windows and macOS and Microsoft Edge version 151.0.4129.50 and later for Windows and macOS.

How are users impacted?

Users of VidyoConnect WebRTC using the affected Chrome and Microsoft Edge versions will not be able to join conferences. They may see one or more of the following behaviors:

  • They will join the call and drop repeatedly.
  • They will see the following screen when they try to join the call:

Understanding this notification

  • Google has released Chromium version 151.0.7922. With this version, there appears to be changes to the SDP message structure for WebRTC. These changes are preventing the media negotiation from completing successfully and thus the endpoint cannot join the conference properly. This change affects browsers using the affected versions of Chromium, Google Chrome, and Microsoft Edge.
  • The last version of Chrome known to work as expected is 150.0.7871.187.
  • This affects all versions of VidyoConnect for WebRTC and VidyoPlatform JavaScript SDK.

What can users/admins do in the meantime?

  • If you are using managed devices across your organization, do not update to the latest version of Chrome and Microsoft Edge.
  • For Epic integrations, if you are using the ‘jvw’ parameter in your conferences, we recommend temporarily disabling it until we identify and resolve the issue.
  • Users on Microsoft Edge and Apple’s Safari do not have this issue.

What's Vidyo doing about it?

  • Vidyo is urgently working on an update that resolves this issue.
  • For VidyoCloud customers, Vidyo will roll out a fix to all environments once available.
  • For customers using a self-hosted VidyoConnect for WebRTC app, prepare for an update to your application.
  • For SDK customers using a self-contained WebRTC client using the VidyoPlatform SDK, prepare to release an updated to your application with an updated SDK.

Need help?

If you still need help you can contact your Vidyo Reseller or the Vidyo Support Team via the Contact Us support page.

Disclaimer

This is an active and developing investigation. The information above is based on our current understanding and may change as additional details become available. References to Google Chrome or a recent browser update are provided for informational purposes only and do not constitute a final determination regarding the cause of the issue. Google and Chrome are trademarks of Google LLC. We are not affiliated with Google, and no responsibility or fault is being legally attributed to Google at this stage.