<?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-12T15:46:35.768062+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-ejbca-2021-40088</id>
    <title>BIT-ejbca-2021-40088</title>
    <updated>2026-10-12T15:46:35.771495+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: ejbca</p>
<p>An issue was discovered in PrimeKey EJBCA before 7.6.0. CMP RA Mode can be configured to use a known client certificate to authenticate enrolling clients. The same RA client certificate is used for revocation requests as well. While enrollment enforces multi tenancy constraints (by verifying that the client certificate has access to the CA and Profiles being enrolled against), this check was not performed when authenticating revocation operations, allowing a known tenant to revoke a certificate belonging to another tenant.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-ejbca-2021-40088"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-31062</id>
    <title>EUVD-2026-31062</title>
    <updated>2026-10-12T15:46:35.771539+00:00</updated>
    <content>EUVD-2026-31062</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-31062"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-40088</id>
    <title>fkie_cve-2021-40088</title>
    <updated>2026-10-12T15:46:35.771555+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in PrimeKey EJBCA before 7.6.0. CMP RA Mode can be configured to use a known client certificate to authenticate enrolling clients. The same RA client certificate is used for revocation requests as well. While enrollment enforces multi tenancy constraints (by verifying that the client certificate has access to the CA and Profiles being enrolled against), this check was not performed when authenticating revocation operations, allowing a known tenant to revoke a certificate belonging to another tenant.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-40088"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vw75-3c43-6g3p</id>
    <title>GHSA-vw75-3c43-6g3p</title>
    <updated>2026-10-12T15:46:35.771578+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in PrimeKey EJBCA before 7.6.0. CMP RA Mode can be configured to use a known client certificate to authenticate enrolling clients. The same RA client certificate is used for revocation requests as well. While enrollment enforces multi tenancy constraints (by verifying that the client certificate has access to the CA and Profiles being enrolled against), this check was not performed when authenticating revocation operations, allowing a known tenant to revoke a certificate belonging to another tenant.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vw75-3c43-6g3p"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-40088</id>
    <title>gsd-2021-40088</title>
    <updated>2026-10-12T15:46:35.771594+00:00</updated>
    <content>gsd-2021-40088</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-40088"/>
  </entry>
</feed>
