<?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-03T15:38:26.055442+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/euvd-2026-22095</id>
    <title>EUVD-2026-22095</title>
    <updated>2026-10-03T15:38:26.117450+00:00</updated>
    <content>EUVD-2026-22095</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-22095"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-21291</id>
    <title>fkie_cve-2021-21291</title>
    <updated>2026-10-03T15:38:26.117489+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OAuth2 Proxy is an open-source reverse proxy and static file server that provides authentication using Providers (Google, GitHub, and others) to validate accounts by email, domain or group. In OAuth2 Proxy before version 7.0.0, for users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect. For example, if a whitelist domain was configured for ".example.com", the intention is that subdomains of example.com are allowed. Instead, "example.com" and "badexample.com" could also match. This is fixed in version 7.0.0 onwards. As a workaround, one can disable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-21291"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4mf2-f3wh-gvf2</id>
    <title>GHSA-4mf2-f3wh-gvf2 — Subdomain checking of whitelisted domains could allow unintended redirects in oauth2-proxy</title>
    <updated>2026-10-03T15:38:26.117527+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/oauth2-proxy/oauth2-proxy/v7, Go: github.com/oauth2-proxy/oauth2-proxy</p>
<p>### Impact
_What kind of vulnerability is it? Who is impacted?_
For users that use the whitelist domain feature, a domain that ended in a similar way to the intended domain could have been allowed as a redirect.</p>
<p>For example, if a whitelist domain was configured for `.example.com`, the intention is that subdomains of `example.com` are allowed.
Instead, `example.com` and `badexample.com` could also match.</p>
<p>### Patches
_Has the problem been patched? What versions should users upgrade to?_
This is fixed in version 7.0.0 onwards.</p>
<p>### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
Disable the whitelist domain feature and run separate OAuth2 Proxy instances for each subdomain.</p>
<p># Original Issue Posted by @semoac:</p>
<p>Whitelist Domain feature is not working as expected because is not matching a dot to ensure the redirect is a subdomain.</p>
<p>## Expected Behavior</p>
<p>If whitelist domain is set to `.example.com` , then `hack.alienexample.com`  should be rejected as a valid redirect.</p>
<p>## Current Behavior</p>
<p>The code is removing the `dot`  from `.example.com`  and  only checking if the redirect string end with `example.com`</p>
<p>## Possible Solution
Here
https://github.com/oauth2-proxy/oauth2-proxy/blob/c377466411f2aee180a732187edb638f2f7e57fb/oauthproxy.go#L661</p>
<p>Include the dot when checking the string:
```
strings.HasSuffix(redirectHostname, "." + domainHostname)
```</p>
<p>## Steps to Reproduce (for bugs)</p>
<p>```
package main</p>
<p>import (
	"fmt"
	"strings"
)</p>
<p>f…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4mf2-f3wh-gvf2"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-21291</id>
    <title>gsd-2021-21291</title>
    <updated>2026-10-03T15:38:26.117581+00:00</updated>
    <content>gsd-2021-21291</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-21291"/>
  </entry>
</feed>
