weblate is vulnerable to Server-Side Request Forgery (SSRF)
35
Low Risk
Weblate validates a repository hostname's DNS resolution when a component repository URL is saved, but the external Git and other VCS clients perform their own DNS lookup when connecting. A user allowed to manage repository URLs can supply a hostname that first resolves to a public address and later resolves to a private or internal address, bypassing the validation. Protected VCS operations such as clone, fetch, or push can then reach internal VCS-compatible services and expose private repository contents. The fix binds protected Git HTTPS and SSH operations to the addresses approved during validation and disables transports that cannot enforce that binding.
You are affected if you are using a version that falls within the vulnerable range and you allow untrusted users to configure component repository URLs for protected VCS connections.
weblate is vulnerable to Server-Side Request Forgery (SSRF) in versions 0.0.1 - 2026.7.1.
Upgrade the weblate library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant