# io.Connect Desktop 10.5.2

Source: https://docs.interop.io/desktop/getting-started/changelog/platform/10-5-2/index.html

## io.Connect Desktop 10.5.2

*Release date: 29.10.2026*

| Components | Version |
|------------|---------|
| Electron | [44.9.3](https://releases.electronjs.org/release/v44.9.3) |
| Chromium | 152.0.7977.167 |
| Node.js | 24.22.0 |

[Version support policy](https://docs.interop.io/desktop/getting-started/version-support/index.md)

The following libraries are bundled with **io.Connect Desktop** 10.5.2 and will be used for [auto injection](https://docs.interop.io/desktop/getting-started/how-to/interop-enable-your-apps/javascript/index.md#auto_injection):

| Injected Library | Version |
|------------------|---------|
| [`@interopio/desktop`](https://www.npmjs.com/package/@interopio/desktop) | [6.23.2](https://docs.interop.io/desktop/getting-started/changelog/libraries/interopio-desktop/index.md#623-6232) |
| [`@interopio/fdc3`](https://www.npmjs.com/package/@interopio/fdc3) | 2.11 |

### Electron Upgrade

**io.Connect Desktop** 10.5.2 comes with an upgraded version of Electron. This upgrade was made to address security issues related to the underlying Electron framework.

The new Electron version contains the [mitigation for compromised eMudhra intermediate certificates](https://github.com/electron/electron/security/advisories/GHSA-jr5w-w6x2-84p9) (CVE-2026-115570), as well as security fixes backported from upstream Chromium, V8, ANGLE, PDFium, and Skia.

TLS connections using certificates issued through these intermediate certificates are now rejected both by the Chromium networking stack used by web apps and by the Node.js `tls`, `https`, and `fetch` modules. [This announcement](https://blog.google/security/protecting-chrome-and-android-users-from-compromised-emudhra-intermediate-ca-certificates/) by Google provides information about the compromised certificates.

## Improvements & Bug Fixes

> - Upgraded to Electron 44.9.3 (Chromium 152).
>
> - Fixed an issue related to properly handling the cached **io.Manager** data on platform startup when **io.Manager** is unreachable, ensuring that the platform starts with the cached data and reconnects to **io.Manager** when it becomes available.