<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-16T13:58:19.305731+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/bit-gitea-2026-20883</id>
    <title>BIT-gitea-2026-20883 — Gitea Stopwatch API Missing Authorization Check Leads to Post-Revocation Information Disclosure</title>
    <updated>2026-10-16T13:58:19.309015+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: gitea</p>
<p>Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-gitea-2026-20883"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-266521</id>
    <title>EUVD-2026-266521</title>
    <updated>2026-10-16T13:58:19.309061+00:00</updated>
    <content>EUVD-2026-266521</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-266521"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-20883</id>
    <title>fkie_cve-2026-20883</title>
    <updated>2026-10-16T13:58:19.309077+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-20883"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-j8xr-c56q-m8jj</id>
    <title>GHSA-j8xr-c56q-m8jj — Gitea improperly exposes issue titles and repository names through previously started stopwatches</title>
    <updated>2026-10-16T13:58:19.309099+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/go-gitea/gitea</p>
<p>Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-j8xr-c56q-m8jj"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0200</id>
    <title>WID-SEC-W-2026-0200 — Gitea: Mehrere Schwachstellen</title>
    <updated>2026-10-16T13:58:19.309120+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0200"/>
  </entry>
</feed>
