11-19 更新 实时
首页/ 技术栈/ 正文

Weaviate 如何应对 eMudhra 证书泄露事件

技术栈 来源:Weaviate Blog 2026-10-22 08:00 0 阅读 机器翻译
Weaviate 如何应对 eMudhra 证书泄露事件

昨天,Weaviate 的工程团队为我们的全部客户资产和基础设施平台打了补丁,以缓解证书颁发机构 eMudhra 泄露的八张证书带来的风险。虽然端到端流程耗时不到 17 小时,我们的企业版客户在六小时内就完成了补丁修复,但这只是故事的一半。

昨天补丁工作中尤其令人惊叹的是,来自我们所有工程团队(核心开发团队、控制台团队、平台团队和智能体团队)以及产品支持部门的同事组成了一支专项小组,共同协作,把我们环境中几乎每一个字节都升级到了 Go 1.27.3 版本。作为一个团队,我们创建并审查了 pull request、推送了 tag、跟进晋级过程,并看到我们各项服务的测试全部通过。

我们数据库的安全性和可靠性至关重要,我们深知,所有客户信任都建立在这一基础之上。看着 Weaviate 工程团队的工作令人振奋:从始终处于 AI 可能性最前沿的应用研究团队,到管理横跨三家云服务商的复杂计算、安全、可观测性和部署基础设施的平台工程师,以及介于两者之间的每一个人。

如果你认为自己发现了安全漏洞,请前往我们的安全报告页面,了解如何向我们提交报告。Weaviate 会联系你确认收到报告,并告知后续步骤。我们要求研究人员在漏洞被修复并公布之前不要公开披露漏洞,除非你已收到 Weaviate 安全团队的回复,确认可以公开。

欢迎查看快速入门教程,或注册一个免费的 Weaviate Cloud 账户。

译文由英文原文机器翻译,术语按行业惯例统一,可在文末展开原文核对。

查看英文原文(How Weaviate responded to the eMudhra certificate compromise)

Yesterday, the engineering team at Weaviate patched our entire customer estate and infrastructure platform to mitigate the risk of eight leaked certificates from the certificate authority eMudhra. While the end-to-end process took us less than 17 hours, and our Enterprise customers were patched within six hours, that's only half of the story.

What was particularly amazing about yesterday's patching effort was that a task force of colleagues from all our engineering teams (our core developers, console, platform and agents teams) and our product support function came together to co-ordinate rolling almost every byte of our environment to Go version 1.27.3. As one team, we created and reviewed pull requests, pushed tags, watched promotions and saw the tests of our services pass.

The security and reliability of our database is paramount to us, and we understand that it is this foundation upon which all of our customer trust is built. It is inspiring watching the Weaviate engineering team at work; from our applied research team who live on the bleeding edge of what is possible with AI, to our platform engineers who manage complex compute, security, observability and deployment infrastructure across three cloud providers, and everyone in between.

Reporting Security Issues​

If you think you have found a security vulnerability, please go to our Security Report page to learn how to send us a report. Weaviate will contact you to acknowledge your report, and advise on next steps. We ask that researchers do not disclose vulnerabilities publicly until they have been fixed and announced, unless you have received a response from the Weaviate security team that you can do so.

Ready to start building?​

Check out the Quickstart tutorial, or sign up for a free Weaviate Cloud account.

正文保留英文原文,标题与摘要由机器翻译。

本文由采集器自动同步

原文发布于 Weaviate Blog(How Weaviate responded to the eMudhra certificate compromise),标题、摘要与正文由机器翻译,术语按行业惯例统一,未经人工逐句校订。

阅读原文 ↗