<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 14 Oct 2026 22:34:10 +0000</lastBuildDate>
    <item>
      <title>cnvd-2018-00771</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2018-00771</link>
      <description>cnvd-2018-00771</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2018-00771</guid>
    </item>
    <item>
      <title>EUVD-2026-181091</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-181091</link>
      <description>EUVD-2026-181091</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-181091</guid>
    </item>
    <item>
      <title>fkie_cve-2017-16857</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2017-16857</link>
      <description>&lt;p&gt;It is possible to bypass the bitbucket auto-unapprove plugin via minimal brute-force because it is relying on asynchronous events on the back-end. This allows an attacker to merge any code into unsuspecting repositories. This affects all versions of the auto-unapprove plugin, however since the auto-unapprove plugin is not bundled with Bitbucket Server it does not affect any particular version of Bitbucket.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;It is possible to bypass the bitbucket auto-unapprove plugin via minimal brute-force because it is relying on asynchronous events on the back-end. This allows an attacker to merge any code into unsuspecting repositories. This affects all versions of the auto-unapprove plugin, however since the auto-unapprove plugin is not bundled with Bitbucket Server it does not affect any particular version of Bitbucket.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2017-16857</guid>
    </item>
    <item>
      <title>GHSA-wrg5-4633-4gg8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wrg5-4633-4gg8</link>
      <description>&lt;p&gt;It is possible to bypass the bitbucket auto-unapprove plugin via minimal brute-force because it is relying on asynchronous events on the back-end. This allows an attacker to merge any code into unsuspecting repositories. This affects all versions of the auto-unapprove plugin, however since the auto-unapprove plugin is not bundled with Bitbucket Server it does not affect any particular version of Bitbucket.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;It is possible to bypass the bitbucket auto-unapprove plugin via minimal brute-force because it is relying on asynchronous events on the back-end. This allows an attacker to merge any code into unsuspecting repositories. This affects all versions of the auto-unapprove plugin, however since the auto-unapprove plugin is not bundled with Bitbucket Server it does not affect any particular version of Bitbucket.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wrg5-4633-4gg8</guid>
    </item>
    <item>
      <title>gsd-2017-16857</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2017-16857</link>
      <description>gsd-2017-16857</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2017-16857</guid>
    </item>
  </channel>
</rss>
