# CVE-2026-130385: Weblate 2026.11 through 2026.11.2 Information Disclosure via Task Status API Race


- **Severity:** Low 2.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-cvp4-3fmc-2xrv

## What is CVE-2026-130385?

CVE-2026-130385 is a low-severity vulnerability in WeblateOrg weblate, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2026-130385?

1 open source package ship an affected version, including weblate.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `weblate` | PyPI | `pkg:pypi/weblate` | From 2026.11 to 2026.11.2 | None |

## How do I fix CVE-2026-130385?

No fix has been published for CVE-2026-130385 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130385 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130385 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130385 and fix it if it is affected.

What it is: CVE-2026-130385 is a low-severity vulnerability in WeblateOrg weblate, published on 17 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130385 exists.

Affected packages and fixed versions:
- weblate (PyPI): affected from 2026.11 up to 2026.11.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130385/ (Markdown: https://insights.sbomify.com/CVE-2026-130385/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130385
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130385
- OSV: https://osv.dev/vulnerability/CVE-2026-130385

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130385/
Summaries are generated and may contain mistakes; the official description above is the record.
