{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-77573 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77573 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-77573 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-77573 in the wild and no public exploit code.\n\nAffected product: WeblateOrg weblate. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-77573/ (Markdown: https://insights.sbomify.com/CVE-2026-77573/index.md)","id":"CVE-2026-77573","markdown":"https://insights.sbomify.com/CVE-2026-77573/index.md","name":"CVE-2026-77573","record":{"aliases":["GHSA-45m9-pf98-8jmq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Weblate localization platform","requires_auth":"low_privilege","summary":"Attackers can exploit DNS rebinding in Weblate VCS operations to access internal services and expose private repository contents.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Weblate: DNS rebinding in VCS operations allows server-side request forgery","id":"CVE-2026-77573","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"BentoPDF: SSRF in cors-proxy-worker.js via DNS-based hostname allowlist bypass","id":"CVE-2026-77581"},"packages":[],"prev":{"headline":"Information disclosure in VeraCrypt","id":"CVE-2026-77572"},"products":["weblate"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["WeblateOrg"]},"summary":"Attackers can exploit DNS rebinding in Weblate VCS operations to access internal services and expose private repository contents.","url":"https://insights.sbomify.com/CVE-2026-77573/"}