<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T22:15:34.786927+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-55227</id>
    <title>CVE-2026-55227 — Observable object existence disclosure in private Weblate projects via globally scoped object lookups</title>
    <updated>2026-09-29T22:15:35.158386+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> WeblateOrg weblate</p>
<p>Weblate is a web-based localization tool. In versions prior to 2026.7, several endpoints look up objects in a globally scoped manner rather than restricting the lookup to projects the user can access, so they return HTTP 403 (Forbidden) instead of 404 (Not Found) when a user requests an object they are not authorized to see. This difference lets unauthorized users infer whether a given object exists in a private Weblate project. The issue has been fixed in version 2026.7.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-55227"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-3941</id>
    <title>PYSEC-2026-3941 — Private Weblate projects vulnerable to observable object existence disclosure via globally scoped object lookups</title>
    <updated>2026-09-29T22:15:35.158505+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: weblate</p>
<p>### Impact
The several endpoints could leak object existence information to users who had no access to it by HTTP status code 403 instead of 404.</p>
<p>### Patches
* https://github.com/WeblateOrg/weblate/pull/19971</p>
<p>### References
Thanks to Yaohui Wang for reporting this via GitHub.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-3941"/>
  </entry>
</feed>
