CVE-2026-111943: Distrust compromised intermediate certificates in crypto/x509

Published Oct 19, 2026
·
Updated

Affected versions include emSign ECC Root CA - G3, which can allow certificate paths through distrusted emSign intermediates.

Affected versions may accept certificate paths containing distrusted emSign intermediate public keys. The private keys corresponding to these intermediates are now well known.

Version 1.0.10+ removes this root.

The webpki-roots 0.26.11 compatibility package contains no independent trust store and re-exports the roots from its separately resolved 1.x dependency. That parent dependency must resolve to 1.0.10 or newer; an older parent remains affected by this advisory.

Other sources

Affected versions include emSign ECC Root CA - G3, which can allow certificate paths through distrusted emSign intermediates.

Affected versions may accept certificate paths containing distrusted emSign intermediate public keys. The private keys corresponding to these intermediates are now well known.

Version 1.0.10+ removes this root.

Version 0.26.11 is a compatibility wrapper that re-exports parent::TLSSERVERROOTCERTS from its webpki-root-certs 1.x dependency; it contains no separate root certificate list. Its resolved 1.x dependency must be updated to 1.0.10 or later.

— OSV

Affected versions may accept certificate paths containing distrusted emSign intermediate public keys when the configured trust anchors allow such paths. The private keys corresponding to these intermediates are now well known.

Versions 0.103.16 and 0.104.0-alpha.8 reject paths containing these public keys.

— OSV

Go releases 1.27.3 and 1.26.10 address the following issue:

https://groups.google.com/g/golang-nuts/c/K22sG2AYnKU

crypto/x509: mitigation for security concerns with a specific Certificate Authority

We're blocking trust in a small set of intermediate certificates due to specific security concerns around their operation.

Verify will now filter out chains which contain these intermediates, preventing them from being returned to the caller.

We highly recommend immediately upgrading to this release.

This is CVE-2026-111943 and Go issue https://go.dev/issue/82345.

— Red Hat

Go: CVE-2026-111943 Distrust compromised intermediate certificates in crypto/x509

— Microsoft

On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.

— Ubuntu

Affected Software

30 affected componentsFixes available
go Go
bitnami/golang<1.26.10
1.26.10
bitnami/golang>=1.27.0-0<1.27.3
1.27.3
go/stdlib<1.26.10
1.26.10
go/stdlib>=1.27.0-0<1.27.3
1.27.3
rust/rustls-webpki>=0.0.0-0<0.103.16
0.103.16
rust/rustls-webpki>=0.104.0-alpha.1<0.104.0-alpha.8
0.104.0-alpha.8
rust/webpki-roots>=0.0.0-0<0.26.11
0.26.11
rust/webpki-roots>=0.26.12-0<1.0.10
1.0.10
rust/webpki-root-certs>=0.0.0-0<0.26.11
0.26.11
rust/webpki-root-certs>=0.26.12-0<1.0.10
1.0.10
ubuntu/golang-1.24*
ubuntu/golang-1.26*
ubuntu/golang-1.24*
ubuntu/golang-1.26*
ubuntu/golang-1.26*
ubuntu/golang-1.24*
ubuntu/golang-1.26*
debian/golang-1.19<=1.19.8-2
debian/golang-1.24<=1.24.4-1
debian/golang-1.26
1.26.10-1
debian/golang-1.27
1.27.3-1
debian/golang-1.19*
debian/golang-1.24*
debian/golang-1.26<1.26.10-1
1.26.10-1
debian/golang-1.27<1.27.3-1
1.27.3-1
alpine/docker<29.9.2-r0
29.9.2-r0
alpine/docker-cli-buildx<0.38.1-r0
0.38.1-r0
alpine/docker-cli-compose<5.6.1-r0
5.6.1-r0
alpine/go<1.26.10-r0
1.26.10-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade bitnami/golang to a version that resolves this vulnerability.

    Fixed in 1.26.10
  2. Upgrade

    Upgrade bitnami/golang to a version that resolves this vulnerability.

    Fixed in 1.27.3
  3. Upgrade

    Upgrade go/stdlib to a version that resolves this vulnerability.

    Fixed in 1.26.10
  4. Upgrade

    Upgrade go/stdlib to a version that resolves this vulnerability.

    Fixed in 1.27.3
  5. Upgrade

    Upgrade rust/rustls-webpki to a version that resolves this vulnerability.

    Fixed in 0.103.16
  6. Upgrade

    Upgrade rust/rustls-webpki to a version that resolves this vulnerability.

    Fixed in 0.104.0-alpha.8
  7. Upgrade

    Upgrade rust/webpki-roots to a version that resolves this vulnerability.

    Fixed in 0.26.11
  8. Upgrade

    Upgrade rust/webpki-roots to a version that resolves this vulnerability.

    Fixed in 1.0.10
  9. Upgrade

    Upgrade rust/webpki-root-certs to a version that resolves this vulnerability.

    Fixed in 0.26.11
  10. Upgrade

    Upgrade rust/webpki-root-certs to a version that resolves this vulnerability.

    Fixed in 1.0.10
  11. Upgrade

    Upgrade debian/golang-1.26 to a version that resolves this vulnerability.

    Fixed in 1.26.10-1
  12. Upgrade

    Upgrade debian/golang-1.27 to a version that resolves this vulnerability.

    Fixed in 1.27.3-1
  13. Upgrade

    Upgrade alpine/docker to a version that resolves this vulnerability.

    Fixed in 29.9.2-r0
  14. Upgrade

    Upgrade alpine/docker-cli-buildx to a version that resolves this vulnerability.

    Fixed in 0.38.1-r0
  15. Upgrade

    Upgrade alpine/docker-cli-compose to a version that resolves this vulnerability.

    Fixed in 5.6.1-r0
  16. Upgrade

    Upgrade alpine/go to a version that resolves this vulnerability.

    Fixed in 1.26.10-r0
  17. Upgrade

    Upgrade Go to a version that resolves this vulnerability.

    Fixed in 1.27.3
  18. Upgrade

    Upgrade Go to a version that resolves this vulnerability.

    Fixed in 1.26.10
  19. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.0.10
  20. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.103.16
  21. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.104.0-alpha.8

Event History

Oct 19, 2026
Advisory Published
via OSV·12:00 PM
Data Sourced
via OSV·12:00 PM
DescriptionAffected Software
Oct 20, 2026
Data Sourced
via Red Hat·09:43 AM
DescriptionSeverityAffected Software
Oct 21, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·12:52 AM
Data Sourced
via MITRE·12:52 AM
DescriptionWeakness
Data Sourced
via OSV·01:17 AM
Severity
Data Sourced
via NVD·01:17 AM
Description
Exploit Published
via GitHub·11:55 PM
Oct 28, 2026
Data Sourced
via Microsoft·08:47 AM
DescriptionSeverityWeakness
Oct 30, 2026
Data Sourced
via NVD·01:18 PM
SeverityWeakness

Frequently Asked Questions

1

Which deployments may need additional attention beyond normal system trust-store updates?

The concern is limited to narrower cases where the system trust store may not be updated without further action. On most platforms, Go uses the system root certificates provided to it.

2

What operation is protected by the added denylist?

The denylist is applied when crypto/x509 Verify is called. Verification returns an error if the chain includes any known intermediate certificate that is no longer considered trustworthy.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203