r/programming (Top) · October 20, 2026 · 1 min readcurated by Sönke
Go 1.27.3 and 1.26.10 now reject certificate chains tied to eight blocked CA public keys after applications are rebuilt. The supplied material describes the releases as an emergency response to security concerns but gives no explanation of the affected authorities or the underlying issue. The linked report is the relevant follow-up for Go maintainers.
Illustration: The Dev Dispatch
The r/programming post links to a report about Go 1.27.3 and Go 1.26.10. Both versions reject certificate chains that rely on eight blocked CA public keys once an application has been rebuilt with either release.
The supplied material does not identify the keys or explain the security concerns behind the block. It presents the change as an emergency update.
Attackers took control of parts of the .gh, .sl and .as country-code domains and used altered DNS data to obtain unauthorized TLS certificates for sev…
Scott Helme’s report examines a failure in eMudhra’s certificate authority infrastructure: private keys corresponding to public certificates had tiny …
Everyone is talking about the model that found CVE-2026-109618 and CVE-2026-109619. The more uncomfortable number is that Cisco puts about half of int…
The php2shell exploits leave nothing in your logs. You only see what the attacker does next, which means detection depends on www-data almost never do…
Comments
No comments yet — be the first.
Open the discussion
No account or password needed — just enter your e-mail and we’ll send you a one-time sign-in link. First time here? You’re set up automatically.
Your rating will be applied automatically after you sign in.
Check your inbox
We’ve sent a sign-in link to …. Open it on this device — this tab will sign you in automatically.
Nothing arrived? Check your spam folder — and mark the mail as "Not spam" so it lands in your inbox next time.