<?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-11-18T13:33:43.233876+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/cve-2026-123352</id>
    <title>CVE-2026-123352 — HomeBox: API keys are not revoked on password change and never expire by default, so a leaked key survives full credent…</title>
    <updated>2026-11-18T13:33:43.235048+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> sysadminsmedia homebox</p>
<p>HomeBox is a home inventory and organization system. Prior to 0.27.0, a HomeBox password change revokes the user's other session tokens but does not revoke the user's API keys, and API keys have no default API-key expiration. An attacker who has obtained an API key can therefore retain full API-level access after the account owner changes the password and can keep that access indefinitely unless the owner discovers and manually deletes the key by ID. Because the password change terminates other sessions, the surviving API credential can evade the owner's expected containment and detection. This issue is fixed in version 0.27.0.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-123352"/>
  </entry>
</feed>
