Menu

The eMudhra fix lives in your Go binary, not in your Docker image
📰

The eMudhra fix lives in your Go binary, not in your Docker image

DEV Community: go·Jules Robineau·14 days ago
#nHOH87Kj
#devtogo#devto#dev#binary#version
Reading 0:00
15s threshold

On October 19, Go shipped two security releases: 1.27.3 and 1.26.10. The fix touches a single package, crypto/x509 . I rebuilt one of my Go services on the same Docker image as before. Go's own scanner still found the flaw.

TL;DR : the eMudhra fix is a list of eight banned keys, written into the code of crypto/x509 . That list is compiled into your binary. Updating the base image or the system certificates does not add it. You have to rebuild with Go 1.27.3 or 1.26.10, then redeploy. If your Dockerfile still builds with Go 1.25, rebuilding changes nothing: that version gets no more fixes.

Versions and source status: snapshot as of October 31, 2026. Check the latest fixes before deploying.

This article is for Go developers and for teams that ship Go services in containers.

What happened with eMudhra

eMudhra is a certificate authority . Most browsers and operating systems accept its certificates.

On October 17, Mozilla blocked eight of its intermediate certificates in Firefox.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.