<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T20:54:49.182213+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-94381</id>
    <title>CVE-2026-94381 — MISP Privilege Escalation: Read-Only API Key User Can Regain Full Role via updateLoginTime</title>
    <updated>2026-09-28T20:54:49.184415+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> MISP</p>
<p>MISP has a security issue that can let a user gain more access than their API key is supposed to allow.</p>
<p>A read-only API key should only let someone view information. However, after logging in with such a key, a specific MISP function could accidentally restore the user’s normal account permissions. This means someone with a read-only API key could potentially gain write, delete, or even administrator access if their underlying account has those permissions.</p>
<p>Exploiting the issue requires a valid read-only API key and a single request to the affected function.</p>
<p>The main impact is that MISP’s API key restrictions can be bypassed, allowing actions that the API key was specifically meant to prevent.</p>
<p>Version affected: &lt;2.5.47</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-94381"/>
  </entry>
</feed>
