# Obol's required Charon security upgrade

> Obol updated Go and removed trust in emSign/AAA certificate roots from the software image.

- URL: https://riadefi.com/on-chain/2026-10-21-obol-charon-ca-certificates/
- Type: Upgrade or migration
- Stage: Confirmed
- Evidence: confirmed
- Materiality: material
- Event date: 2026-10-21
- Version: 1, published 2026-10-22 (first published 2026-10-22)
- Follow-up: 2026-10-23
- Advisor-relevant: no
- Affects: Obol Network (protocol)

## What happened

Obol published a required Charon security upgrade on October 21, 2026, according to its official release.

## What changed

Obol updated Go and removed trust in emSign/AAA certificate roots from the software image.

## What did not change

Obol still requires another upgrade before Gloas/Glamsterdam.

## Confirmed

- Obol identifies compromised certificates under CVE-2026-111943.
- Obol requires all operators to install the release.

## Still open

- Obol does not establish operator adoption in the release.
- The release does not establish validator losses or compromised signing keys.

## What it means for an advisor

- Ketju should review the Obol memo for certificate exposure and obtain upgrade confirmation from relevant operators.
- Advisors should establish whether covered staking providers use affected Charon installations.

## Sources

1. [Release v1.11.2](https://github.com/ObolNetwork/charon/releases/tag/v1.11.2) · Obol Network · 2026-10-21


---

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