<?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-06T10:14:37.720322+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-336429</id>
    <title>EUVD-2026-336429</title>
    <updated>2026-10-06T10:14:37.796076+00:00</updated>
    <content>EUVD-2026-336429</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-336429"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55516</id>
    <title>fkie_cve-2026-55516</title>
    <updated>2026-10-06T10:14:37.796117+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Snipe-IT is an IT asset/license management system. Prior to 8.6.2, PATCH or PUT /api/v1/maintenances/{maintenance_id} checks access to the current maintenance record and asset but then fills attacker-controlled fields including asset_id without re-authorizing the newly supplied asset, allowing an authorized user to move a maintenance record onto an asset outside their company scope. This issue is fixed in version 8.6.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-55516"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-575r-357h-fhch</id>
    <title>GHSA-575r-357h-fhch — Snipe-IT vulnerable to cross-company asset maintenance re-parenting via API update</title>
    <updated>2026-10-06T10:14:37.796153+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: snipe/snipe-it</p>
<p>### Impact
The API endpoint for updating asset maintenance records allows an authorized user to change the asset_id of an existing maintenance record to an asset outside their company scope.</p>
<p>In a Full Multiple Company Support / multi-company deployment, this allows a user from Company A to attach or move a maintenance record onto an asset belonging to Company B. The endpoint appears to authorize access to the existing maintenance record’s asset, but does not re-authorize the newly supplied asset_id before saving the update.</p>
<p>###  Affected endpoint
`PATCH /api/v1/maintenances/{maintenance_id}`</p>
<p>Also likely affected:</p>
<p>`PUT /api/v1/maintenances/{maintenance_id}`</p>
<p>### Preconditions
The attacker needs:
- A valid authenticated API token.
- Permission to update asset maintenance records.
- Access to a maintenance record currently attached to an asset in their own company.</p>
<p>The attacker does not need access to the target asset’s company.</p>
<p>### Root cause
In the API maintenance update flow, the application checks access to the current maintenance record / current asset, then accepts attacker-controlled fields including `asset_id`.</p>
<p>The vulnerable behavior is that the new asset_id is not checked against the current user’s company scope before being saved.</p>
<p>### Relevant code path:
`app/Http/Controllers/Api/MaintenancesController.php`</p>
<p>The update method loads the maintenance, checks access to the existing $maintenance-&gt;asset, then calls:
```php
$maintenance-&gt;fill($request-&gt;all());
$main…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-575r-357h-fhch"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2073</id>
    <title>WID-SEC-W-2026-2073 — Snipe-IT: Mehrere Schwachstellen</title>
    <updated>2026-10-06T10:14:37.796208+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Snipe-IT ausnutzen, um Dateien zu manipulieren, um Sicherheitsvorkehrungen zu umgehen, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2073"/>
  </entry>
</feed>
