Skip to main content
Menu
CVEs

CVE

Weblate information disclosure in task status API

CVE-2026-130385EUVD-2026-127022

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

2.3LowCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
20/100 · provisional
12% of weblate downloads last week were affected versions (906).PyPI, per-version counts from ClickPy, 7.8K downloads in the last 7 days, read Nov 14, 2026
None on Exploit-DB, Metasploit or GitHub

Summary

Weblate, a web-based translation platform, has a race condition in its task status API that lets authenticated project members who lack the vcs.view permission read unredacted repository error messages. Those messages can reveal upstream repository URLs, filesystem paths, and host names, and an attacker can reach the bug remotely over the network with low-privilege login.

Written by a model from the sources below. Verify against them.

Original description

Weblate 2026.11 through 2026.11.2 contains a time-of-check time-of-use race condition in the GET /api/tasks/{pk}/ endpoint that exposes unredacted repository error messages. Authenticated project members lacking vcs.view permission can poll failing repository tasks to obtain RepositoryCommandError text revealing upstream repository URLs, filesystem paths, and host names.

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects PyPI packages
  • Severity2.3/10CVSS 2.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 39 if advisories confirm default setups are exposed

Impact

  • Widely used

    weblate has 3.9k weekly downloads.Source: pypistats.org

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130385 (Weblate 2026.11 through 2026.11.2 Information Disclosure via Task Status API Race), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130385 (entry last updated 2026-11-17):
Affected:
- PyPI package weblate: from 2026.11, through 2026.11.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130385 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130385 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/WeblateOrg/weblate/issues/22890
- https://github.com/WeblateOrg/weblate/blob/weblate-2026.11.2/weblate/utils/celery.py#L278-L316
- https://github.com/WeblateOrg/weblate/blob/weblate-2026.11.2/weblate/api/views.py#L6150-L6162
- https://www.vulncheck.com/advisories/weblate-2026.11-through-2026.11.2-information-disclosure-via-task-status-api-race
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130385
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130385"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • From 2026.11 · through 2026.11.2

    No fix released. The latest release, 2026.11.2, is still affected.

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Report
  2. Repository
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130385

Is CVE-2026-130385 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-130385?

weblate (PyPI): from 2026.11 through 2026.11.2.Source: cve.now feed data

More CVEs