<?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, 19 Oct 2026 12:36:27 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-76686</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-76686</link>
      <description>EUVD-2026-76686</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-76686</guid>
    </item>
    <item>
      <title>fkie_cve-2024-27918</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-27918</link>
      <description>&lt;p&gt;Coder allows oragnizations to provision remote development environments via Terraform. Prior to versions 2.6.1, 2.7.3, and 2.8.4, a vulnerability in Coder&amp;#39;s OIDC authentication could allow an attacker to bypass the `CODER_OIDC_EMAIL_DOMAIN` verification and create an account with an email not in the allowlist. Deployments are only affected if the OIDC provider allows users to create accounts on the provider. During OIDC registration, the user&amp;#39;s email was improperly validated against the allowed `CODER_OIDC_EMAIL_DOMAIN`s. This could allow a user with a domain that only partially matched an allowed domain to successfully login or register. An attacker could register a domain name that exploited this vulnerability and register on a Coder instance with a public OIDC provider.&lt;/p&gt;
&lt;p&gt;Coder instances with OIDC enabled and protected by the `CODER_OIDC_EMAIL_DOMAIN` configuration are affected. Coder instances using a private OIDC provider are not affected, as arbitrary users cannot register through a private OIDC provider without first having an account on the provider. Public OIDC providers are impacted. GitHub authentication and external authentication are not impacted. This vulnerability is remedied in versions 2.8.4, 2.7.3, and 2.6.1 All versions prior to these patches are affected by the vulnerability.*It is recommended that customers upgrade their deployments as soon as possible if they are utilizing OIDC authentication with the `CODER_OIDC_EMAIL_DOMAIN` setting.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Coder allows oragnizations to provision remote development environments via Terraform. Prior to versions 2.6.1, 2.7.3, and 2.8.4, a vulnerability in Coder&amp;#39;s OIDC authentication could allow an attacker to bypass the `CODER_OIDC_EMAIL_DOMAIN` verification and create an account with an email not in the allowlist. Deployments are only affected if the OIDC provider allows users to create accounts on the provider. During OIDC registration, the user&amp;#39;s email was improperly validated against the allowed `CODER_OIDC_EMAIL_DOMAIN`s. This could allow a user with a domain that only partially matched an allowed domain to successfully login or register. An attacker could register a domain name that exploited this vulnerability and register on a Coder instance with a public OIDC provider.&lt;/p&gt;
&lt;p&gt;Coder instances with OIDC enabled and protected by the `CODER_OIDC_EMAIL_DOMAIN` configuration are affected. Coder instances using a private OIDC provider are not affected, as arbitrary users cannot register through a private OIDC provider without first having an account on the provider. Public OIDC providers are impacted. GitHub authentication and external authentication are not impacted. This vulnerability is remedied in versions 2.8.4, 2.7.3, and 2.6.1 All versions prior to these patches are affected by the vulnerability.*It is recommended that customers upgrade their deployments as soon as possible if they are utilizing OIDC authentication with the `CODER_OIDC_EMAIL_DOMAIN` setting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-27918</guid>
    </item>
    <item>
      <title>GHSA-7cc2-r658-7xpf — Coder's OIDC authentication allows email with partially matching domain to register</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7cc2-r658-7xpf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/coder/coder/v2, Go: github.com/coder/coder&lt;/p&gt;
&lt;p&gt;### Summary
A vulnerability in Coder&amp;#39;s OIDC authentication could allow an attacker to bypass the `CODER_OIDC_EMAIL_DOMAIN` verification and create an account with an email not in the allowlist. Deployments are only affected if the OIDC provider allows users to create accounts on the provider (such as public providers like `google.com`).&lt;/p&gt;
&lt;p&gt;### Details
During OIDC registration, the user&amp;#39;s email was improperly validated against the allowed `CODER_OIDC_EMAIL_DOMAIN`s. This could allow a user with a domain that only partially matched an allowed domain to successfully login or register (e.g. `user@exploitcorp.com` would match the allowed domain `corp.com`).&lt;/p&gt;
&lt;p&gt;An attacker could register a domain name that exploited this vulnerability and register on a Coder instance with a public OIDC provider.&lt;/p&gt;
&lt;p&gt;### Impact
Coder instances with OIDC enabled and protected by the `CODER_OIDC_EMAIL_DOMAIN` configuration.&lt;/p&gt;
&lt;p&gt;Coder instances using a private OIDC provider are not affected, as arbitrary users cannot register through a private OIDC provider without first having an account on the provider.&lt;/p&gt;
&lt;p&gt;Public OIDC providers (such as `google.com` without permitted domains set on the OAuth2 App) are impacted.&lt;/p&gt;
&lt;p&gt;GitHub authentication and external authentication are not impacted.&lt;/p&gt;
&lt;p&gt;### Was my deployment impacted?
To check if your deployment was exploited:
- View the audit log on your deployment for unexpected registered users (using the `action:register` filter)
- Check the users list for unexpected users
    - U…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/coder/coder/v2, Go: github.com/coder/coder&lt;/p&gt;
&lt;p&gt;### Summary
A vulnerability in Coder&amp;#39;s OIDC authentication could allow an attacker to bypass the `CODER_OIDC_EMAIL_DOMAIN` verification and create an account with an email not in the allowlist. Deployments are only affected if the OIDC provider allows users to create accounts on the provider (such as public providers like `google.com`).&lt;/p&gt;
&lt;p&gt;### Details
During OIDC registration, the user&amp;#39;s email was improperly validated against the allowed `CODER_OIDC_EMAIL_DOMAIN`s. This could allow a user with a domain that only partially matched an allowed domain to successfully login or register (e.g. `user@exploitcorp.com` would match the allowed domain `corp.com`).&lt;/p&gt;
&lt;p&gt;An attacker could register a domain name that exploited this vulnerability and register on a Coder instance with a public OIDC provider.&lt;/p&gt;
&lt;p&gt;### Impact
Coder instances with OIDC enabled and protected by the `CODER_OIDC_EMAIL_DOMAIN` configuration.&lt;/p&gt;
&lt;p&gt;Coder instances using a private OIDC provider are not affected, as arbitrary users cannot register through a private OIDC provider without first having an account on the provider.&lt;/p&gt;
&lt;p&gt;Public OIDC providers (such as `google.com` without permitted domains set on the OAuth2 App) are impacted.&lt;/p&gt;
&lt;p&gt;GitHub authentication and external authentication are not impacted.&lt;/p&gt;
&lt;p&gt;### Was my deployment impacted?
To check if your deployment was exploited:
- View the audit log on your deployment for unexpected registered users (using the `action:register` filter)
- Check the users list for unexpected users
    - U…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7cc2-r658-7xpf</guid>
    </item>
    <item>
      <title>gsd-2024-27918</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-27918</link>
      <description>gsd-2024-27918</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-27918</guid>
    </item>
  </channel>
</rss>
