CVE-2026-62249: Weblate: Restricted-component change history leaked to non-member project users through the nested `GET /api/projects/{slug}/changes/` endpoint

Published Aug 26, 2026
·
Updated

Weblate is a web-based continuous localization platform used to manage software translations. In versions prior to 2026.7, an authenticated user with access to a project can retrieve the change history of restricted components in that project through nested API change endpoints, even without permission to view those components directly. The nested endpoints do not apply the component-level access checks enforced on the direct component views, so the requester can enumerate changes for components that should be hidden from them. The exposed data can include the restricted component's identity, translation and unit links, and change payload fields such as source or translated string content in the target, old, and details values. This issue is fixed in version 2026.7.

Affected Software

1 affected component
Weblate weblate<2026.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Weblate to a version that resolves this vulnerability.

    Fixed in 2026.7

Event History

Aug 26, 2026
CVE Published
via MITRE·08:29 PM
Data Sourced
via MITRE·08:29 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated user who has access to a Weblate project can exploit it, even if they are not permitted to view specific restricted components within that project.

2

What access or interaction does exploitation require?

The attacker needs valid authentication and access to the affected project. Exploitation is performed through nested project change-history API endpoints and does not require user interaction.

3

What information may be exposed?

The change history can disclose the identity of restricted components, translation and unit links, and change payload fields. Exposed payload data may include source or translated string content in target, old, and details values.

4

How can I determine whether an instance is affected?

Weblate versions earlier than 2026.7 are affected. A practical verification is to use an authenticated account that can access a project but lacks access to a restricted component, then check whether the nested project change-history endpoint returns changes for that component.

5

What should be done to remediate the issue?

Upgrade Weblate to version 2026.7, which fixes the missing component-level access checks on the nested endpoints.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203