<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 13 Oct 2026 00:51:30 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-357513</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-357513</link>
      <description>EUVD-2026-357513</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-357513</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55703</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55703</link>
      <description>&lt;p&gt;Snipe-IT is an IT asset/license management system. Prior to 8.6.3, any activated account can request /maintenances/{id} and read maintenance records for assets in the same company without asset or maintenance permission. app/Http/Controllers/MaintenancesController.php show() renders the record without authorize(), while company-scoped route-model binding only prevents access to other companies. Disclosed fields include asset tags, suppliers, purchase costs, notes, and dates. This issue is fixed in version 8.6.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Snipe-IT is an IT asset/license management system. Prior to 8.6.3, any activated account can request /maintenances/{id} and read maintenance records for assets in the same company without asset or maintenance permission. app/Http/Controllers/MaintenancesController.php show() renders the record without authorize(), while company-scoped route-model binding only prevents access to other companies. Disclosed fields include asset tags, suppliers, purchase costs, notes, and dates. This issue is fixed in version 8.6.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55703</guid>
    </item>
    <item>
      <title>GHSA-r9r3-g9fp-3q4q — Snipe-IT: Maintenance Record Disclosure via Missing Authorization on GET</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r9r3-g9fp-3q4q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: snipe/snipe-it&lt;/p&gt;
&lt;p&gt;### Impact
Any activated account in a company can read every maintenance record for that company (asset tag, supplier, purchase cost, free-text notes, dates) without holding any asset or maintenance permission.&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`MaintenancesController::show()` renders a maintenance record without any authorization check. Every other action in the controller authorizes against the asset; `show()` does not. Any user in the asset&amp;#39;s company can read maintenance detail (asset tag, supplier, purchase cost, notes, dates) by visiting `/maintenances/{id}`, regardless of permissions.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;```php
public function show(Maintenance $maintenance): View|RedirectResponse
{
    return view(&amp;#39;maintenances.view&amp;#39;)-&amp;gt;with(&amp;#39;maintenance&amp;#39;, $maintenance);
}
```&lt;/p&gt;
&lt;p&gt;No `authorize()` call. The sibling actions all gate on the asset: `index()` calls `authorize(&amp;#39;view&amp;#39;, Asset::class)` (line 33), and `edit()`/`update()`/`destroy()` call `authorize(&amp;#39;update&amp;#39;, $maintenance-&amp;gt;asset)` (lines 139, 166, 286). The route is registered with only the auth guard:&lt;/p&gt;
&lt;p&gt;```php
Route::resource(&amp;#39;maintenances&amp;#39;, MaintenancesController::class, [&amp;#39;middleware&amp;#39; =&amp;gt; [&amp;#39;auth&amp;#39;]]);
```&lt;/p&gt;
&lt;p&gt;(`routes/web/hardware.php:185`). Route-model binding still applies the company scope, so the read is bounded to the caller&amp;#39;s company; the absent permission gate is the defect. Maintenance IDs are sequential and visible in the record URL.&lt;/p&gt;
&lt;p&gt;## Proof of concept&lt;/p&gt;
&lt;p&gt;1. As an administrator, create an asset in a company (here, `CompanyA`). Open the asset, choose Maint…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: snipe/snipe-it&lt;/p&gt;
&lt;p&gt;### Impact
Any activated account in a company can read every maintenance record for that company (asset tag, supplier, purchase cost, free-text notes, dates) without holding any asset or maintenance permission.&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`MaintenancesController::show()` renders a maintenance record without any authorization check. Every other action in the controller authorizes against the asset; `show()` does not. Any user in the asset&amp;#39;s company can read maintenance detail (asset tag, supplier, purchase cost, notes, dates) by visiting `/maintenances/{id}`, regardless of permissions.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;```php
public function show(Maintenance $maintenance): View|RedirectResponse
{
    return view(&amp;#39;maintenances.view&amp;#39;)-&amp;gt;with(&amp;#39;maintenance&amp;#39;, $maintenance);
}
```&lt;/p&gt;
&lt;p&gt;No `authorize()` call. The sibling actions all gate on the asset: `index()` calls `authorize(&amp;#39;view&amp;#39;, Asset::class)` (line 33), and `edit()`/`update()`/`destroy()` call `authorize(&amp;#39;update&amp;#39;, $maintenance-&amp;gt;asset)` (lines 139, 166, 286). The route is registered with only the auth guard:&lt;/p&gt;
&lt;p&gt;```php
Route::resource(&amp;#39;maintenances&amp;#39;, MaintenancesController::class, [&amp;#39;middleware&amp;#39; =&amp;gt; [&amp;#39;auth&amp;#39;]]);
```&lt;/p&gt;
&lt;p&gt;(`routes/web/hardware.php:185`). Route-model binding still applies the company scope, so the read is bounded to the caller&amp;#39;s company; the absent permission gate is the defect. Maintenance IDs are sequential and visible in the record URL.&lt;/p&gt;
&lt;p&gt;## Proof of concept&lt;/p&gt;
&lt;p&gt;1. As an administrator, create an asset in a company (here, `CompanyA`). Open the asset, choose Maint…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r9r3-g9fp-3q4q</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2792 — Snipe-IT: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2792</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Snipe-IT ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder möglicherweise einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Snipe-IT ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder möglicherweise einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2792</guid>
    </item>
  </channel>
</rss>
