PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-77573 WeblateOrg CVE debrief

CVE-2026-77573 is a server-side request forgery (SSRF) vulnerability in Weblate, a web-based continuous localization platform. An attacker with permission to manage component repository URLs can cause Weblate to reach internal VCS-compatible services, potentially exposing private repository contents. This issue is fixed in version 2026.8. Weblate validates the hostname's first DNS resolution, but external VCS clients perform a separate DNS lookup, allowing an attacker-controlled hostname to be re-pointed to an internal or private address before the connection is made. Installations permitting untrusted repository hostnames while using VCS_RESTRICT_PRIVATE=True are affected.

Vendor
WeblateOrg
Product
weblate
CVSS
LOW 3.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-26
Original CVE updated
2026-09-09
Advisory published
2026-08-26
Advisory updated
2026-09-09

Who should care

Defenders responsible for Weblate installations, especially those permitting untrusted repository hostnames with VCS_RESTRICT_PRIVATE=True, should assess exposure and prioritize verification and remediation.

Why it matters

CVE-2026-77573 is a server-side request forgery (SSRF) vulnerability in Weblate that can lead to potential exposure of private repository contents. Defenders should prioritize verifying Weblate installations, especially those permitting untrusted repository hostnames with VCS_RESTRICT_PRIVATE=True, and ensure they are updated to version 2026.8.

  • Potential exposure of private repository contents
  • Verification of Weblate installations and configurations
  • Monitoring for suspicious activity
  • Remediation priority for installations permitting untrusted repository hostnames

Technical summary

The vulnerability allows an attacker with permission to manage component repository URLs to perform SSRF attacks against internal services through DNS rebinding during VCS operations. Weblate validates the hostname's first DNS resolution, but external VCS clients perform a separate DNS lookup, allowing an attacker-controlled hostname to be re-pointed to an internal or private address before the connection is made.

Defensive priority

Defenders should prioritize verifying Weblate installations, especially those permitting untrusted repository hostnames with VCS_RESTRICT_PRIVATE=True, and ensure they are updated to version 2026.8.

Recommended defensive actions

  • Verify Weblate installations and ensure they are updated to version 2026.8
  • Restrict repository hostnames to trusted sources
  • Monitor Weblate logs for suspicious activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is described in the CVE record and NVD entry. Weblate's validation of hostname DNS resolution and external VCS clients' separate DNS lookup allow for DNS rebinding attacks. The issue is fixed in version 2026.8.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-77573 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-77573

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-77573 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-77573

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.