CVE-2026-132125 json
Weblate 5.0 through 2026.11.2 Privilege Escalation via Component List Deletion
published 14h ago modified 13h ago also EUVD-2026-128620
- cvss
- 2.1
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Weblate 5.0 through 2026.11.2 contains a privilege escalation vulnerability where deleting a component list leaves stale Group.projects rows, widening team scope to whole projects. A user with componentlist.edit who deletes a list grants 'From component list' team members their full role, including project.edit, across possibly private projects.
Is CVE-2026-132125 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.1 | CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 3.3 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N |
Inferred packages
No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.
| ecosystem | package | repository | affected |
|---|---|---|---|
| pypi | weblate | weblateorg/weblate | >= 5.0, <= 2026.11.2 |
Affected products
- WeblateOrg weblate
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/WeblateOrg/weblate/issues/22910
issue-tracking
-
github.com
/WeblateOrg/weblate
product
-
vulncheck.com
/advisories/weblate-5.0-through-2026.11.2-privilege-escalation-via-component-list-deletion
third-party-advisory
Sources
- CVE List CVE-2026-132125
- NVD CVE-2026-132125
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.