CVE-2026-111943 for self-hosted 1Password tools (eMudhra certificate authority issue)

Published:

Summary

On October 17, 2026, a researcher showed that the private keys for eight intermediate certificate authorities run by eMudhra could be recovered. Anyone with those keys could create certificates that software would trust. This issue is tracked as CVE-2026-111943.

This is an industry-wide issue. 1Password wasn’t compromised, and we have no evidence it was used against 1Password or our customers. 1Password.com and our hosted services are already updated, and you don’t need to do anything for them.

Some 1Password tools that run in your own environment check certificates themselves. If you use any of them, update to the version listed below or newer.

Who may be affected

You may be affected if you use any of these tools in your own environment:

  • 1Password CLI
  • Self-hosted 1Password SCIM Bridge
  • 1Password Connect server and Connect SDKs
  • 1Password SDKs
  • 1Password Kubernetes Operator, Kubernetes Secrets Injector, and Helm charts
  • 1Password Terraform provider, Pulumi provider, and HashiCorp Vault plugin
  • 1Password for Linux

The following aren’t affected, and you don’t need to do anything:

  • 1Password.com and hosted services, including hosted provisioning
  • 1Password for Mac, Windows, iOS, and Android
  • 1Password in your browser

These apps rely on certificate protections from your operating system or browser, which already block the affected certificates.

Update any of the following tools you use to the version listed or newer:

  • 1Password CLI: 2.41.1
  • 1Password SCIM Bridge (self-hosted): 2.9.17
  • 1Password Connect server: 1.8.4
  • 1Password SDK for Python: 0.4.2 (if you use it on Linux)
  • Connect SDK for Python: 2.1.1
  • Kubernetes Operator: 1.12.1
  • Kubernetes Secrets Injector: 1.0.3
  • Helm charts: connect 2.4.3, secrets-injector 1.2.1
  • Terraform provider: 3.4.1
  • Pulumi provider: 1.2.1
  • HashiCorp Vault plugin: 1.1.2

Some tools use the certificate checks built into their language runtime, so there’s no new 1Password release for them. Update the runtime, then rebuild or redeploy your app:

  • 1Password SDK for Go and Connect SDK for Go: Go 1.26.10 or newer, or Go 1.27.3 or newer
  • 1Password SDK for JavaScript and Connect SDK for JavaScript: Node.js 22.23.4 or newer, Node.js 24.22.1 or newer, or Node.js 26.12.1 or newer

If you use 1Password for Linux, update to 8.12.44 or newer when it’s available on November 3, 2026. If your organization manages app updates centrally, make sure your Linux devices are on 8.12.44 or newer.

What you should know

Certificate authorities issue the certificates that let software confirm the identity of the server it connects to. Someone who can intercept network traffic could use a forged certificate to pose as a trusted server, but only to software that still trusts the affected certificates.

Your 1Password account and the data in your vaults don’t rely on certificate authorities. 1Password includes an additional layer of cryptographic defenses when apps communicate with 1Password servers, so a forged certificate can’t be used to read or change your vault data. To learn more, see How we use Secure Remote Password.

What we’re doing

We removed trust for the affected eMudhra certificates from 1Password.com and our hosted services, and released updated versions of the tools listed above. We’ll release the 1Password for Linux update on November 3, 2026, and we’ll update this article if anything changes.

Questions

If you have questions, ask in the 1Password Developer Slack or contact 1Password Support.