<?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-20T21:44:51.776738+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-65308</id>
    <title>EUVD-2026-65308</title>
    <updated>2026-10-20T21:44:51.779738+00:00</updated>
    <content>EUVD-2026-65308</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-65308"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2018-11537</id>
    <title>fkie_cve-2018-11537</title>
    <updated>2026-10-20T21:44:51.779780+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Auth0 angular-jwt before 0.1.10 treats whiteListedDomains entries as regular expressions, which allows remote attackers with knowledge of the jwtInterceptorProvider.whiteListedDomains setting to bypass the domain whitelist filter via a crafted domain.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2018-11537"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-vm2p-f5j4-mj6g</id>
    <title>GHSA-vm2p-f5j4-mj6g — Auth0 angular-jwt misinterprets allowlist as regex</title>
    <updated>2026-10-20T21:44:51.779821+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: angular-jwt</p>
<p>Auth0 angular-jwt before 0.1.10 treats whiteListedDomains entries as regular expressions, which allows remote attackers with knowledge of the `jwtInterceptorProvider.whiteListedDomains` setting to bypass the domain allowlist filter via a crafted domain.</p>
<p>For example, if the setting is initialized with:</p>
<p>`jwtInterceptorProvider.whiteListedDomains = ['whitelisted.Example.com'];`</p>
<p>An attacker can set up a domain `whitelistedXexample.com` that will pass the allow list filter, as it considers the `.` separator to be a regex whildcard which matches any character.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-vm2p-f5j4-mj6g"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2018-11537</id>
    <title>gsd-2018-11537</title>
    <updated>2026-10-20T21:44:51.779863+00:00</updated>
    <content>gsd-2018-11537</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2018-11537"/>
  </entry>
</feed>
