Redpanda: CVE-2026-111943 (emudhra) Response
Timeline of updates
- identifiedEdited
We are responding internally to CVE-2026-111943 related to compromised root certificates.
We have assessed Redpanda Cloud and have remediated any clusters secured with mTLS and have mitigated any other potential impacted vectors. We have also patched all Golang runtimes.
We have concluded that Redpanda Brokers are not impacted in Redpanda Cloud (BYOC, Dedicated, Serverless).
For Cloud and Self Hosted customers, you should review your client CAs for clients connecting outside of Redpanda, and mitigate as needed.
For self-hosted clusters, particularly those with mTLS, Redpanda recommends updating truststores at the earliest opportunity.
- identified
We have concluded that Redpanda Brokers are not impacted in Redpanda Cloud (BYOC, Dedicated, Serverless).
For Cloud and Self Hosted customers, you should review your client CAs for clients connecting outside of Redpanda, and mitigate as needed.
For self-hosted clusters, particularly those with mTLS, Redpanda recommends updating truststores at the earliest opportunity.
- resolvedEdited
Redpanda has reviewed and confirmed that Redpanda Cloud and its associated applications are not at risk of CVE-2026-111943: https://nvd.nist.gov/vuln/detail/cve-2026-111943 (opens in new tab).
Self-Hosted Customers will receive a separate Technical Services Bulletin describing actions they can take to review their Self-Hosted clusters.
https://knowledgebase.redpanda.com/articles/1660912335-tsb-2026-44-self-hosted-emudhra-cve-2026-111943-response (opens in new tab): https://knowledgebase.redpanda.com/articles/1660912335-tsb-2026-44-self-hosted-emudhra-cve-2026-111943-response?preview=true (opens in new tab)
Changes Rewindex caught on this incident
- Incident silently edited: CVE-2026-111943 (emudhra) Response
- Incident updated: CVE-2026-111943 (emudhra) Response
- Incident updated: CVE-2026-111943 (emudhra) Response
- Incident silently edited: CVE-2026-111943 (emudhra) Response
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
633cbbd36d6cd718…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
7cc16f8e37ea6ccd…Version 3 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
149412baeaafae8a…Version 4 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
ebc23d35888462da…Version 5 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
945fcbe6ee36c95a…
Impact, status and times are the vendor’s own, as last archived. View on status.redpanda.com (opens in new tab).