WeblateOrg Weblate up to 2026.11.2 ChangeManager ChangeManager.last_changes information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00+ |
Summary
A vulnerability marked as problematic has been reported in WeblateOrg Weblate up to 2026.11.2. The affected element is the function ChangeManager.last_changes of the component ChangeManager. This manipulation causes information disclosure.
This vulnerability is tracked as CVE-2026-129881. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in WeblateOrg Weblate up to 2026.11.2. Affected by this vulnerability is the function ChangeManager.last_changes of the component ChangeManager. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
Weblate 2026.6 through 2026.11.2 contains an information disclosure vulnerability in ChangeManager.last_changes() that exposes workspaces the viewer cannot view by skipping Workspace.can_view() checks site-wide. Anonymous visitors on instances with REQUIRE_LOGIN disabled and only public projects can query /changes/, /api/changes/, or RSS/CSV feeds to obtain hidden workspace names, UUIDs, actions, and timestamps.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-129881 since 11/16/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/16/2026). The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.5VulDB Meta Temp Score: 4.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/16/2026 Advisory disclosed11/16/2026 CVE reserved
11/16/2026 VulDB entry created
11/16/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CNA: VulnCheck
CVE: CVE-2026-129881 (🔒)
GCVE (CVE): GCVE-0-2026-129881
GCVE (VulDB): GCVE-100-437707
Entry
Created: 11/16/2026 15:57Changes: 11/16/2026 15:57 (75)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.