<?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>Sat, 03 Oct 2026 21:35:25 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-233518</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233518</link>
      <description>EUVD-2026-233518</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233518</guid>
    </item>
    <item>
      <title>fkie_cve-2022-39308</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-39308</link>
      <description>&lt;p&gt;GoCD is a continuous delivery server. GoCD helps you automate and streamline the build-test-release cycle for continuous delivery of your product. GoCD versions from 19.2.0 to 19.10.0 (inclusive) are subject to a timing attack in validation of access tokens due to use of regular string comparison for validation of the token rather than a constant time algorithm. This could allow a brute force attack on GoCD server API calls to observe timing differences in validations in order to guess an access token generated by a user for API access. This issue is fixed in GoCD version 19.11.0. As a workaround, users can apply rate limiting or insert random delays to API calls made to GoCD Server via a reverse proxy or other fronting web server. Another workaround, users may disallow use of access tokens by users by having an administrator revoke all access tokens through the &amp;#34;Access Token Management&amp;#34; admin function.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;GoCD is a continuous delivery server. GoCD helps you automate and streamline the build-test-release cycle for continuous delivery of your product. GoCD versions from 19.2.0 to 19.10.0 (inclusive) are subject to a timing attack in validation of access tokens due to use of regular string comparison for validation of the token rather than a constant time algorithm. This could allow a brute force attack on GoCD server API calls to observe timing differences in validations in order to guess an access token generated by a user for API access. This issue is fixed in GoCD version 19.11.0. As a workaround, users can apply rate limiting or insert random delays to API calls made to GoCD Server via a reverse proxy or other fronting web server. Another workaround, users may disallow use of access tokens by users by having an administrator revoke all access tokens through the &amp;#34;Access Token Management&amp;#34; admin function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-39308</guid>
    </item>
    <item>
      <title>gsd-2022-39308</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-39308</link>
      <description>gsd-2022-39308</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-39308</guid>
    </item>
  </channel>
</rss>
