<?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-02T17:19:01.530650+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/bdu:2025-08603</id>
    <title>bdu:2025-08603</title>
    <updated>2026-10-02T17:19:01.538226+00:00</updated>
    <content>bdu:2025-08603</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-08603"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-openbao-2024-7594</id>
    <title>BIT-openbao-2024-7594 — Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default</title>
    <updated>2026-10-02T17:19:01.538258+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: openbao</p>
<p>Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. If the valid_principals and default_user fields of the SSH secrets engine configuration are not set, an SSH certificate requested by an authorized user to Vault’s SSH secrets engine could be used to authenticate as any user on the host. Fixed in Vault Community Edition 1.17.6, and in Vault Enterprise 1.17.6, 1.16.10, and 1.15.15.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-openbao-2024-7594"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-209956</id>
    <title>EUVD-2026-209956</title>
    <updated>2026-10-02T17:19:01.538292+00:00</updated>
    <content>EUVD-2026-209956</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-209956"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-7594</id>
    <title>fkie_cve-2024-7594</title>
    <updated>2026-10-02T17:19:01.538305+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. If the valid_principals and default_user fields of the SSH secrets engine configuration are not set, an SSH certificate requested by an authorized user to Vault’s SSH secrets engine could be used to authenticate as any user on the host. Fixed in Vault Community Edition 1.17.6, and in Vault Enterprise 1.17.6, 1.16.10, and 1.15.15.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-7594"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-jg74-mwgw-v6x3</id>
    <title>GHSA-jg74-mwgw-v6x3 — Vault SSH Secrets Engine Configuration Did Not Restrict Valid Principals By Default</title>
    <updated>2026-10-02T17:19:01.538328+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/hashicorp/vault, Go: github.com/openbao/openbao</p>
<p>Vault’s SSH secrets engine did not require the valid_principals list to contain a value by default. If the valid_principals and default_user fields of the SSH secrets engine configuration are not set, an SSH certificate requested by an authorized user to Vault’s SSH secrets engine could be used to authenticate as any user on the host. Fixed in Vault Community Edition 1.17.6, and in Vault Enterprise 1.17.6, 1.16.10, and 1.15.15.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-jg74-mwgw-v6x3"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-1</id>
    <title>openSUSE-SU-2024:0350-1 — Security update for govulncheck-vulndb</title>
    <updated>2026-10-02T17:19:01.538352+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for govulncheck-vulndb</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2024:3911-1</id>
    <title>SUSE-SU-2024:3911-1 — Security update for govulncheck-vulndb</title>
    <updated>2026-10-02T17:19:01.538379+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for govulncheck-vulndb</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2024:3911-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2239</id>
    <title>WID-SEC-W-2024-2239 — Hashicorp Vault: Schwachstelle ermöglicht Privilegieneskalation</title>
    <updated>2026-10-02T17:19:01.538400+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Hashicorp Vault ausnutzen, um seine Privilegien zu erhöhen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2239"/>
  </entry>
</feed>
