> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/changelog/oct-2026/oct-21-2026-v1.104.1.md).

# Oct 21, 2026 - v1.104.1

#### Security

On 2026-10-20, eMudhra disclosed that the private keys of eight of its intermediate\
CA certificates are recoverable from the certificates themselves\
(<https://emudhra.we-have-a-problem.com/>). The intermediates chain to roots trusted by all major root programs, so an attacker on the network path could have impersonated any TLS endpoint to clients that do not enforce Certificate Transparency, which includes Go programs and most non-browser software.

This is not a vulnerability in Bindplane code. Like every Go program and Linux\
container image built before the disclosure, Bindplane v1.104.0 trusted the affected\
chain for its outbound TLS connections (database, SSO provider, webhooks, cloud\
services). There is no known exploitation of these keys, and we have no indication\
that any Bindplane deployment was targeted.

v1.104.1 closes the exposure in two independent ways:

* **Go 1.26.10** (CVE-2026-111943): the Go TLS stack now rejects any certificate chain containing the compromised intermediates, independent of the host trust store. This protects all v1.104.1 packages, including deb, rpm, container, and binary installs.
* **Updated container trust store**: the `bindplane-ee` images now build with Alpine Linux `ca-certificates 20261020-r0`, which distrusts the affected eMudhra roots.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bindplane.com/changelog/oct-2026/oct-21-2026-v1.104.1.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.