# CVE-2026-77573: Weblate: DNS rebinding in VCS operations allows server-side request forgery

> Attackers can exploit DNS rebinding in Weblate VCS operations to access internal services and expose private repository contents.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-45m9-pf98-8jmq

## What is CVE-2026-77573?

CVE-2026-77573 is a low-severity server-side request forgery vulnerability in WeblateOrg weblate, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Weblate is a web-based continuous localization platform used to manage software translations. In versions prior to 2026.8, a user permitted to manage component repository URLs can perform server-side request forgery against internal services through DNS rebinding during VCS operations. Weblate validates the hostname's first DNS resolution, but the external VCS clients that later connect perform a separate DNS lookup, so an attacker-controlled hostname that initially resolves to a public address can be re-pointed to an internal or private address before the connection is made. By triggering a clone, fetch, push, or similar remote operation, the attacker can cause Weblate to reach internal VCS-compatible services and potentially expose private repository contents. Installations that permit untrusted repository hostnames while using VCS_RESTRICT_PRIVATE=True are affected. This issue is fixed in version 2026.8.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2026-77573 being exploited?

There is no known exploitation of CVE-2026-77573 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77573 is a low-severity server-side request forgery vulnerability in WeblateOrg weblate, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77573 in the wild and no public exploit code.

Affected product: WeblateOrg weblate. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-77573/ (Markdown: https://insights.sbomify.com/CVE-2026-77573/index.md)
```

## Sources

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

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