<?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>Wed, 07 Oct 2026 23:38:09 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-338387</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338387</link>
      <description>EUVD-2026-338387</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338387</guid>
    </item>
    <item>
      <title>fkie_cve-2026-49998</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49998</link>
      <description>&lt;p&gt;Centrifugo is an open-source scalable real-time messaging server. Prior to 6.8.1, Centrifugo dynamic JWKS endpoint verification could reuse a key for one allowed issuer to verify a JWT for another allowed issuer because the JWKS cache and singleflight lookup were keyed only by JWT header kid, not by the resolved JWKS endpoint, issuer, audience, or trust-domain namespace, affecting client.token.jwks_public_endpoint, client.subscription_token.jwks_public_endpoint, internal/jwks/cache.go, and internal/jwks/manager.go. This issue is fixed in version 6.8.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Centrifugo is an open-source scalable real-time messaging server. Prior to 6.8.1, Centrifugo dynamic JWKS endpoint verification could reuse a key for one allowed issuer to verify a JWT for another allowed issuer because the JWKS cache and singleflight lookup were keyed only by JWT header kid, not by the resolved JWKS endpoint, issuer, audience, or trust-domain namespace, affecting client.token.jwks_public_endpoint, client.subscription_token.jwks_public_endpoint, internal/jwks/cache.go, and internal/jwks/manager.go. This issue is fixed in version 6.8.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-49998</guid>
    </item>
    <item>
      <title>GHSA-g6vg-wj8f-48cj — Centrifugo's dynamic JWKS key cache keyed only by `kid` allows cross-issuer JWT authentication bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-g6vg-wj8f-48cj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/centrifugal/centrifugo/v6, Go: github.com/centrifugal/centrifugo/v5, Go: github.com/centrifugal/centrifugo/v4, Go: github.com/centrifugal/centrifugo/v3, Go: github.com/centrifugal/centrifugo&lt;/p&gt;
&lt;p&gt;#### Summary&lt;/p&gt;
&lt;p&gt;Centrifugo&amp;#39;s dynamic JWKS endpoint feature can verify a JWT for one allowed issuer using a public key cached from another allowed issuer. The JWKS cache and `singleflight` lookup are keyed only by the JWT header `kid`, not by the resolved JWKS endpoint, issuer, audience, or other trust-domain namespace.&lt;/p&gt;
&lt;p&gt;In a documented multi-issuer dynamic JWKS configuration, an attacker who can obtain or mint a valid token for issuer/tenant A can authenticate as issuer/tenant B if both JWKS documents use the same `kid` value and tenant A&amp;#39;s key is cached first. This affects connection token verification and subscription token verification because both paths use the same JWKS verification manager.&lt;/p&gt;
&lt;p&gt;#### Details&lt;/p&gt;
&lt;p&gt;The vulnerable path is reachable when either of these shipped configuration options is set to a templated JWKS URL using values derived from JWT `iss` or `aud` claims:&lt;/p&gt;
&lt;p&gt;- `client.token.jwks_public_endpoint`
- `client.subscription_token.jwks_public_endpoint`&lt;/p&gt;
&lt;p&gt;Relevant shipped config fields are defined in `internal/configtypes/types.go:59-65`, mapped into verifier configuration in `internal/confighelpers/jwt.go:36-41`, and exposed in the generated config schema at `internal/cli/configdoc/schema.json:3927`, `3947`, `3967`, `3987`, `4069`, `4089`, `4109`, and `4129`. Dynamic JWKS endpoints based on `iss` and `aud` are documented in the project changelog at `CHANGELOG.md:107`.&lt;/p&gt;
&lt;p&gt;External clients control JWT connection and subscription tokens:&lt;/p&gt;
&lt;p&gt;- Connection tokens reach `Verif…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/centrifugal/centrifugo/v6, Go: github.com/centrifugal/centrifugo/v5, Go: github.com/centrifugal/centrifugo/v4, Go: github.com/centrifugal/centrifugo/v3, Go: github.com/centrifugal/centrifugo&lt;/p&gt;
&lt;p&gt;#### Summary&lt;/p&gt;
&lt;p&gt;Centrifugo&amp;#39;s dynamic JWKS endpoint feature can verify a JWT for one allowed issuer using a public key cached from another allowed issuer. The JWKS cache and `singleflight` lookup are keyed only by the JWT header `kid`, not by the resolved JWKS endpoint, issuer, audience, or other trust-domain namespace.&lt;/p&gt;
&lt;p&gt;In a documented multi-issuer dynamic JWKS configuration, an attacker who can obtain or mint a valid token for issuer/tenant A can authenticate as issuer/tenant B if both JWKS documents use the same `kid` value and tenant A&amp;#39;s key is cached first. This affects connection token verification and subscription token verification because both paths use the same JWKS verification manager.&lt;/p&gt;
&lt;p&gt;#### Details&lt;/p&gt;
&lt;p&gt;The vulnerable path is reachable when either of these shipped configuration options is set to a templated JWKS URL using values derived from JWT `iss` or `aud` claims:&lt;/p&gt;
&lt;p&gt;- `client.token.jwks_public_endpoint`
- `client.subscription_token.jwks_public_endpoint`&lt;/p&gt;
&lt;p&gt;Relevant shipped config fields are defined in `internal/configtypes/types.go:59-65`, mapped into verifier configuration in `internal/confighelpers/jwt.go:36-41`, and exposed in the generated config schema at `internal/cli/configdoc/schema.json:3927`, `3947`, `3967`, `3987`, `4069`, `4089`, `4109`, and `4129`. Dynamic JWKS endpoints based on `iss` and `aud` are documented in the project changelog at `CHANGELOG.md:107`.&lt;/p&gt;
&lt;p&gt;External clients control JWT connection and subscription tokens:&lt;/p&gt;
&lt;p&gt;- Connection tokens reach `Verif…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-g6vg-wj8f-48cj</guid>
    </item>
  </channel>
</rss>
