<?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>Mon, 12 Oct 2026 21:54:03 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1165 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1165</link>
      <description>certfr-2026-avi-1165</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1165</guid>
    </item>
    <item>
      <title>cnvd-2018-20787</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2018-20787</link>
      <description>cnvd-2018-20787</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2018-20787</guid>
    </item>
    <item>
      <title>EUVD-2026-165013</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-165013</link>
      <description>EUVD-2026-165013</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-165013</guid>
    </item>
    <item>
      <title>fkie_cve-2018-8023</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2018-8023</link>
      <description>&lt;p&gt;Apache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT). In Apache Mesos versions pre-1.4.2, 1.5.0, 1.5.1, 1.6.0 the comparison of the generated HMAC value against the provided signature in the JWT implementation used is vulnerable to a timing attack because instead of a constant-time string comparison routine a standard `==` operator has been used. A malicious actor can therefore abuse the timing difference of when the JWT validation function returns to reveal the correct HMAC value.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Apache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT). In Apache Mesos versions pre-1.4.2, 1.5.0, 1.5.1, 1.6.0 the comparison of the generated HMAC value against the provided signature in the JWT implementation used is vulnerable to a timing attack because instead of a constant-time string comparison routine a standard `==` operator has been used. A malicious actor can therefore abuse the timing difference of when the JWT validation function returns to reveal the correct HMAC value.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2018-8023</guid>
    </item>
    <item>
      <title>GHSA-c8cc-p3j7-4c7f — Moderate severity vulnerability that affects org.apache.mesos:mesos</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c8cc-p3j7-4c7f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.mesos:mesos&lt;/p&gt;
&lt;p&gt;Apache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT). In Apache Mesos versions pre-1.4.2, 1.5.0, 1.5.1, 1.6.0 the comparison of the generated HMAC value against the provided signature in the JWT implementation used is vulnerable to a timing attack because instead of a constant-time string comparison routine a standard `==` operator has been used. A malicious actor can therefore abuse the timing difference of when the JWT validation function returns to reveal the correct HMAC value.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.mesos:mesos&lt;/p&gt;
&lt;p&gt;Apache Mesos can be configured to require authentication to call the Executor HTTP API using JSON Web Token (JWT). In Apache Mesos versions pre-1.4.2, 1.5.0, 1.5.1, 1.6.0 the comparison of the generated HMAC value against the provided signature in the JWT implementation used is vulnerable to a timing attack because instead of a constant-time string comparison routine a standard `==` operator has been used. A malicious actor can therefore abuse the timing difference of when the JWT validation function returns to reveal the correct HMAC value.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c8cc-p3j7-4c7f</guid>
    </item>
    <item>
      <title>gsd-2018-8023</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2018-8023</link>
      <description>gsd-2018-8023</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2018-8023</guid>
    </item>
  </channel>
</rss>
