<?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-08T19:47:27.330560+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-266349</id>
    <title>EUVD-2026-266349</title>
    <updated>2026-10-08T19:47:27.333200+00:00</updated>
    <content>EUVD-2026-266349</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-266349"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23518</id>
    <title>fkie_cve-2026-23518</title>
    <updated>2026-10-08T19:47:27.333242+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Fleet is open source device management software. In versions prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3, a vulnerability in Fleet's Windows MDM enrollment flow could allow an attacker to submit forged authentication tokens that are not properly validated. Because JWT signatures were not verified, Fleet could accept attacker-controlled identity claims, enabling enrollment of unauthorized devices under arbitrary Azure AD user identities. Versions 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 fix the issue. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-23518"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-63m5-974w-448v</id>
    <title>GHSA-63m5-974w-448v — Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment</title>
    <updated>2026-10-08T19:47:27.333289+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/fleetdm/fleet</p>
<p>### Summary</p>
<p>A vulnerability in Fleet’s Windows MDM enrollment flow could allow an attacker to submit forged authentication tokens that are not properly validated. Because JWT signatures were not verified, Fleet could accept attacker-controlled identity claims, enabling enrollment of unauthorized devices under arbitrary Azure AD user identities.</p>
<p>### Impact</p>
<p>If Windows MDM is enabled, an attacker can enroll rogue devices by submitting a forged JWT containing arbitrary identity claims. Due to missing JWT signature verification, Fleet accepts these claims without validating that the token was issued by Azure AD, allowing enrollment under any Azure AD user identity.</p>
<p>### Patches</p>
<p>- 4.78.3
- 4.77.1
- 4.76.2
- 4.75.2
- 4.53.3</p>
<p>### Workarounds</p>
<p>If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.</p>
<p>### For more information</p>
<p>If you have any questions or comments about this advisory:</p>
<p>Email us at [security@fleetdm.com](mailto:security@fleetdm.com)
Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)</p>
<p>### Credits</p>
<p>We thank @secfox-ai for responsibly reporting this issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-63m5-974w-448v"/>
  </entry>
</feed>
