<?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 16:18:05 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-02270</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-02270</link>
      <description>bdu:2023-02270</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-02270</guid>
    </item>
    <item>
      <title>EUVD-2026-214070</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-214070</link>
      <description>EUVD-2026-214070</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-214070</guid>
    </item>
    <item>
      <title>fkie_cve-2023-29193</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-29193</link>
      <description>&lt;p&gt;SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. The `spicedb serve` command contains a flag named `--grpc-preshared-key` which is used to protect the gRPC API from being accessed by unauthorized requests. The values of this flag are to be considered sensitive, secret data. The `/debug/pprof/cmdline` endpoint served by the metrics service (defaulting running on port `9090`) reveals the command-line flags provided for debugging purposes. If a password is set via the `--grpc-preshared-key` then the key is revealed by this endpoint along with any other flags provided to the SpiceDB binary. This issue has been fixed in version 1.19.1.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All deployments abiding by the recommended best practices for production usage are **NOT affected**:
- Authzed&amp;#39;s SpiceDB Serverless
- Authzed&amp;#39;s SpiceDB Dedicated
- SpiceDB Operator&lt;/p&gt;
&lt;p&gt;Users configuring SpiceDB via environment variables are **NOT affected**.&lt;/p&gt;
&lt;p&gt;Users **MAY be affected** if they expose their metrics port to an untrusted network and are configuring `--grpc-preshared-key` via command-line flag.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;TODO&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;To workaround this issue you can do one of the following:&lt;/p&gt;
&lt;p&gt;- Configure the preshared key via an environment variable (e.g. `SPICEDB_GRPC_PRESHARED_KEY=yoursecret spicedb serve`)
- Reconfigure the `--metrics-addr` flag to bind to a trusted network (e.g. `--metrics-addr=localhost:9090`)
- Disable the metrics servic…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions. The `spicedb serve` command contains a flag named `--grpc-preshared-key` which is used to protect the gRPC API from being accessed by unauthorized requests. The values of this flag are to be considered sensitive, secret data. The `/debug/pprof/cmdline` endpoint served by the metrics service (defaulting running on port `9090`) reveals the command-line flags provided for debugging purposes. If a password is set via the `--grpc-preshared-key` then the key is revealed by this endpoint along with any other flags provided to the SpiceDB binary. This issue has been fixed in version 1.19.1.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All deployments abiding by the recommended best practices for production usage are **NOT affected**:
- Authzed&amp;#39;s SpiceDB Serverless
- Authzed&amp;#39;s SpiceDB Dedicated
- SpiceDB Operator&lt;/p&gt;
&lt;p&gt;Users configuring SpiceDB via environment variables are **NOT affected**.&lt;/p&gt;
&lt;p&gt;Users **MAY be affected** if they expose their metrics port to an untrusted network and are configuring `--grpc-preshared-key` via command-line flag.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;TODO&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;To workaround this issue you can do one of the following:&lt;/p&gt;
&lt;p&gt;- Configure the preshared key via an environment variable (e.g. `SPICEDB_GRPC_PRESHARED_KEY=yoursecret spicedb serve`)
- Reconfigure the `--metrics-addr` flag to bind to a trusted network (e.g. `--metrics-addr=localhost:9090`)
- Disable the metrics servic…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-29193</guid>
    </item>
    <item>
      <title>GHSA-cjr9-mr35-7xh6 — SpiceDB binding metrics port to untrusted networks and can leak command-line flags</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cjr9-mr35-7xh6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/authzed/spicedb&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;The `spicedb serve` command contains a flag named `--grpc-preshared-key` which is used to protect the gRPC API from being accessed by unauthorized requests. The values of this flag are to be considered sensitive, secret data.&lt;/p&gt;
&lt;p&gt;The `/debug/pprof/cmdline` endpoint served by the metrics service (defaulting running on port `9090`) reveals the command-line flags provided for debugging purposes. If a password is set via the `--grpc-preshared-key` then the key is revealed by this endpoint along with any other flags provided to the SpiceDB binary.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All deployments abiding by the recommended best practices for production usage are **NOT affected**:
- Authzed&amp;#39;s SpiceDB Serverless
- Authzed&amp;#39;s SpiceDB Dedicated
- SpiceDB Operator&lt;/p&gt;
&lt;p&gt;Users configuring SpiceDB via environment variables are **NOT affected**.&lt;/p&gt;
&lt;p&gt;Users **MAY be affected** if they expose their metrics port to an untrusted network and are configuring `--grpc-preshared-key` via command-line flag.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;To workaround this issue you can do one of the following:&lt;/p&gt;
&lt;p&gt;- Configure the preshared key via an environment variable (e.g. `SPICEDB_GRPC_PRESHARED_KEY=yoursecret spicedb serve`)
- Reconfigure the `--metrics-addr` flag to bind to a trusted network (e.g. `--metrics-addr=localhost:9090`)
- Disable the metrics service via the flag (e.g. `--metrics-enabled=false`)
- Adopt one of the recommended deployment models: [Authzed&amp;#39;s managed services](https://authzed.com/pricing) or the [SpiceDB Operator](htt…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/authzed/spicedb&lt;/p&gt;
&lt;p&gt;### Background&lt;/p&gt;
&lt;p&gt;The `spicedb serve` command contains a flag named `--grpc-preshared-key` which is used to protect the gRPC API from being accessed by unauthorized requests. The values of this flag are to be considered sensitive, secret data.&lt;/p&gt;
&lt;p&gt;The `/debug/pprof/cmdline` endpoint served by the metrics service (defaulting running on port `9090`) reveals the command-line flags provided for debugging purposes. If a password is set via the `--grpc-preshared-key` then the key is revealed by this endpoint along with any other flags provided to the SpiceDB binary.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;All deployments abiding by the recommended best practices for production usage are **NOT affected**:
- Authzed&amp;#39;s SpiceDB Serverless
- Authzed&amp;#39;s SpiceDB Dedicated
- SpiceDB Operator&lt;/p&gt;
&lt;p&gt;Users configuring SpiceDB via environment variables are **NOT affected**.&lt;/p&gt;
&lt;p&gt;Users **MAY be affected** if they expose their metrics port to an untrusted network and are configuring `--grpc-preshared-key` via command-line flag.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;To workaround this issue you can do one of the following:&lt;/p&gt;
&lt;p&gt;- Configure the preshared key via an environment variable (e.g. `SPICEDB_GRPC_PRESHARED_KEY=yoursecret spicedb serve`)
- Reconfigure the `--metrics-addr` flag to bind to a trusted network (e.g. `--metrics-addr=localhost:9090`)
- Disable the metrics service via the flag (e.g. `--metrics-enabled=false`)
- Adopt one of the recommended deployment models: [Authzed&amp;#39;s managed services](https://authzed.com/pricing) or the [SpiceDB Operator](htt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cjr9-mr35-7xh6</guid>
    </item>
    <item>
      <title>gsd-2023-29193</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-29193</link>
      <description>gsd-2023-29193</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-29193</guid>
    </item>
  </channel>
</rss>
