漏洞和事件处理

产品漏洞报告

参见

如果你已经使用 AI 来发现 Weblate 中的安全问题,请阅读 使用 AI 创建问题。

Weblate 开发团队坚定致力于安全相关问题负责任的报告和披露。我们已经实施并遵守和及时向 Weblate 传输安全更新目标相适应的政策。

Product vulnerability reports cover security issues in Weblate source code, release artifacts, and documented Weblate security properties. They do not replace operational incident response for a particular deployment.

Reports concerning the separately distributed Weblate Client (wlc) are evaluated against the wlc threat model, which documents its intended trust boundaries, supported security properties, and explicit non-goals.

在公开的 GitHub issues tracker 中报告低和中等严重的安全问题。这些报告通过正常的开发流程公开讨论和修复。

Report high and critical severity vulnerabilities privately to security@weblate.org, through GitHub, or using HackerOne. Do not open public issues for these vulnerabilities. Please describe the issue, affected versions, and steps to reproduce it, if known.

If you are unsure of the severity, you may start through a private channel. If the security team assesses a privately reported issue as low or medium severity, we will ask you to continue in a public GitHub issue. Redirecting a report does not itself confirm that the issue is a vulnerability.

Public discussion allows the community to help review and fix low and medium severity issues. Private coordination focuses on vulnerabilities with serious impact, reducing the risk to users while a fix is prepared. This approach is similar to the curl vulnerability disclosure policy.

Self-hosted operators should use this process when they believe an incident in their own deployment is caused by a Weblate product vulnerability. Local containment, recovery, customer notification, provider escalation, and other deployment-specific incident response remain the operator's responsibility.

A member of the security team will respond to private reports within 48 hours, and depending on what action is taken, you may get more follow-up emails. Suspected active exploitation and severe security incidents receive immediate internal attention under 事件报告. Acknowledging a report or completing an investigation does not postpone reporting deadlines.

备注

发送加密报告

如果想发送加密邮件(可选),请使用 security@weblate.org 的公钥,ID 为 8EA7 6E43 0976 3323 C2E3 D5A0 C472 9F23 8A80 EA93.

最常用的 key 服务器上有这枚公钥,使用 WKD 或 直接从 weblate.org.

提示

Weblate 在很多事情上依赖于第三方部件。如果你发现一个影响这些部件的漏洞,请直接报告给相应的项目。如果它也影响已发布的 Weblate 工件或 Weblate 部署,请使用上面基于严重性的流程将影响报告给 Weblate。

这些中的一些是:

安全研究和测试

研究 Weblate 中的安全问题时:

  • Use the Sandbox translation project for testing on Hosted Weblate.

  • Only interact with accounts you own or have explicit permission from the account holder to use.

  • Avoid privacy violations, data destruction, and service interruption or degradation.

  • Do not perform denial-of-service attacks, spam, social engineering (including phishing), or physical attacks.

  • Obtain explicit permission from the operator before testing other deployments.

You may report availability vulnerabilities demonstrated safely in an environment you control. The prohibition on disruptive testing does not exclude these reports.

Weblate 所运营服务的事故

Operational incidents affecting Hosted Weblate, Dedicated Weblate, or other deployments operated by Weblate s.r.o. are handled using Weblate 事件响应计划.

When such an incident also involves a Weblate product vulnerability, the vulnerability report and any public advisory follow the severity-based product vulnerability reporting process and 漏洞披露政策 on this page.

自托管服务部署事故

Operators of self-hosted Weblate deployments are responsible for their local incident response process, including containment, recovery, notification, and provider-specific escalation. The Weblate-operated Weblate 事件响应计划 can be used as a reference, but it is not a maintained incident response plan for third-party deployments.

If a self-hosted incident appears to be caused by a Weblate product vulnerability, report it using the product vulnerability reporting process above.

漏洞披露政策

Weblate 只发布严重性为高和严重的安全漏洞的安全公告。这些漏洞私下处理直至协同披露,漏洞公告会和包含漏洞修复的 release 一起发布在 https://github.com/WeblateOrg/weblate/security/advisories。公告确认受影响的版本、影响、严重性以及用户可采取的缓解漏洞的步骤。

Weblate does not publish security advisories for low or medium severity issues. Their fixes follow the normal public development process and are documented in the release notes.

Technical details may be delayed when publishing them would create greater security risks than benefits while users apply the fix. The incident handler records the reason and a review date in the private incident note. This does not delay authority reports or protective advice users need.

政府部门报告

Weblate adopts the following reporting timelines as a voluntary policy baseline for actively exploited Weblate product vulnerabilities and severe product-security incidents. This includes affected shipped dependencies and incidents learned about through self-hosted deployments. Severe security incidents affecting Weblate-operated services also follow this baseline.

报告

Deadline

早期预警

Without undue delay, within 24 hours of awareness.

主通知

Without undue delay, within 72 hours of awareness.

Final report for an actively exploited vulnerability

Within 14 days after a corrective or mitigating measure becomes available.

Final report for a severe incident

Within one calendar month after the main incident notification.

Hours include weekends and holidays. Acknowledgment, incident declaration, handover, or completion of an investigation does not restart these clocks. When an event involves both active exploitation and a severe incident, track both reporting obligations and final-report deadlines.

These timelines follow the European Commission reporting guidance. The incident handler records whether mandatory or voluntary reporting applies and uses the corresponding route. For CRA reporting, the Single Reporting Platform routes notifications to the coordinating CSIRT and ENISA. This policy does not determine Weblate's regulatory role or claim compliance; see 产品和联系信息.

For classification, submission steps, and private incident records, see 事件报告.

用户通知

Weblate informs impacted users of active exploitation or severe security incidents without undue delay, including available mitigations and corrective actions. Where appropriate, warnings address all users. Known affected contacts, including Hosted and Dedicated Weblate customers, receive e-mail notifications. For high and critical severity vulnerabilities, public GitHub security advisories provide warnings and updates for self-hosted users whose contact details are not known. Low and medium severity issues are tracked in public GitHub issues and release notes. The severity-based reporting and advisory policy does not delay required authority reports or protective advice to users.

Initial warnings can provide protective advice before a fix or detailed vulnerability disclosure is ready. Authority reporting, user warnings, and publication of technical details proceed separately as needed.

Personal-data breaches also require a separate assessment of notifications to affected individuals, even when there is no active exploitation or severe product-security incident.