# Optimism operator security updates

> Optimism distributed fixes for certificate validation in node, transaction submission and dispute software. Operators must install the updates to receive those fixes.

- URL: https://riadefi.com/on-chain/2026-10-22-optimism-emudhra-security-releases/
- Type: Upgrade or migration
- Stage: Confirmed
- Evidence: confirmed
- Materiality: material
- Event date: 2026-10-22
- Version: 1, published 2026-10-22 (first published 2026-10-22)
- Follow-up: 2026-10-23
- Advisor-relevant: no
- Affects: Optimism canonical bridge (protocol)

## What happened

Optimism published operator security updates on October 22, 2026, addressing compromised eMudhra certificates, according to its official releases.

## What changed

Optimism distributed fixes for certificate validation in node, transaction submission and dispute software. Operators must install the updates to receive those fixes.

## What did not change

Optimism states that the kona-host update leaves the proof program unchanged. The releases do not establish changes to bridge contracts or withdrawal terms.

## Confirmed

- Optimism strongly recommends the October 22 updates for op-supernode, op-node, op-conductor, op-challenger and op-batcher operators.
- Optimism identifies compromised eMudhra certificates as CVE-2026-111943 in its release notes.
- Optimism reports fixes for 7 reachable vulnerabilities in the preceding op-conductor release.
- Optimism requires affected calldata operators to reduce their maximum transaction size to 261,909 bytes before updating op-batcher.
- Optimism exempts blob, auto and Alt-DA configurations from that calldata check.

## Still open

- The releases do not establish which Optimism operators installed the fixes.
- Optimism does not report bridge losses or exploitation of these vulnerabilities in the cited releases.

## What it means for an advisor

- Ketju should review the Optimism bridge memo’s operational assumptions and obtain evidence that relevant operators installed the security fixes.
- Ketju should check whether affected transaction submission settings could interrupt deposits or withdrawals during operator updates.

## Sources

1. [op-supernode v1.0.6](https://github.com/ethereum-optimism/optimism/releases/tag/op-supernode/v1.0.6) · Optimism · 2026-10-22
2. [op-node v1.19.11](https://github.com/ethereum-optimism/optimism/releases/tag/op-node/v1.19.11) · Optimism · 2026-10-22
3. [op-conductor v0.9.6](https://github.com/ethereum-optimism/optimism/releases/tag/op-conductor/v0.9.6) · Optimism · 2026-10-22
4. [op-challenger v1.10.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-challenger/v1.10.1) · Optimism · 2026-10-22
5. [op-batcher v1.17.4](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher/v1.17.4) · Optimism · 2026-10-22
6. [kona-host v1.8.1](https://github.com/ethereum-optimism/optimism/releases/tag/kona-host/v1.8.1) · Optimism · 2026-10-22


---

Published by Ketju Research on RIADeFi (https://riadefi.com). Educational research for financial professionals; not investment, legal, tax, or compliance advice.
