<?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>Mon, 12 Oct 2026 04:20:33 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291883</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291883</link>
      <description>EUVD-2026-291883</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291883</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40262</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40262</link>
      <description>&lt;p&gt;Note Mark is an open-source note-taking application. In versions 0.19.1 and prior, the asset delivery handler serves uploaded files inline and relies on magic-byte detection for content type, which does not identify text-based formats such as HTML, SVG, or XHTML. These files are served with an empty Content-Type, no X-Content-Type-Options: nosniff header, and inline disposition, allowing browsers to sniff and render active content. An authenticated user can upload an HTML or SVG file containing JavaScript as a note asset, and when a victim navigates to the asset URL, the script executes under the application&amp;#39;s origin with access to the victim&amp;#39;s authenticated session and API actions. This issue has been fixed in version 0.19.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Note Mark is an open-source note-taking application. In versions 0.19.1 and prior, the asset delivery handler serves uploaded files inline and relies on magic-byte detection for content type, which does not identify text-based formats such as HTML, SVG, or XHTML. These files are served with an empty Content-Type, no X-Content-Type-Options: nosniff header, and inline disposition, allowing browsers to sniff and render active content. An authenticated user can upload an HTML or SVG file containing JavaScript as a note asset, and when a victim navigates to the asset URL, the script executes under the application&amp;#39;s origin with access to the victim&amp;#39;s authenticated session and API actions. This issue has been fixed in version 0.19.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40262</guid>
    </item>
    <item>
      <title>GHSA-9pr4-rf97-79qh — Note Mark has Stored XSS via Unrestricted Asset Upload</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9pr4-rf97-79qh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/enchant97/note-mark/backend&lt;/p&gt;
&lt;p&gt;### Summary
A stored same-origin XSS vulnerability allows any authenticated user to upload an HTML, SVG, or XHTML file as a note asset and have it executed in a victim’s browser under the application’s origin. Because the application serves these files inline without a safe content type and without `nosniff`, browsers can sniff and render active content, giving the attacker access to authenticated Note Mark API actions as the victim.&lt;/p&gt;
&lt;p&gt;### Details
This issue results from three compounding flaws in the asset handling and delivery path.&lt;/p&gt;
&lt;p&gt;#### 1. Asset delivery can be used as an attack vector
The asset delivery route can be used to deliver attacker-controlled uploaded content directly to a victim by URL.&lt;/p&gt;
&lt;p&gt;Relevant route:
- `handlers/assets.go:40`&lt;/p&gt;
&lt;p&gt;```go
huma.Get(api, &amp;#34;/api/notes/{noteID}/assets/{assetID}&amp;#34;, h.GetNoteAssetContentByID)
```&lt;/p&gt;
&lt;p&gt;This makes the uploaded asset reachable by direct navigation, which provides the delivery mechanism for the payload.&lt;/p&gt;
&lt;p&gt;#### 2. Text-based active content is served with an empty `Content-Type`
The asset handler relies on `h2non/filetype` for content-type detection:&lt;/p&gt;
&lt;p&gt;- `handlers/assets.go:147`&lt;/p&gt;
&lt;p&gt;```go
kind, _ := filetype.Match(buf)
if kind != filetype.Unknown {
    contentType = kind.MIME.Value
}
```&lt;/p&gt;
&lt;p&gt;The detection library uses magic-byte matching and does not identify text-based formats such as HTML, SVG, JavaScript, XML, or XHTML. For those files, `filetype.Match` returns `Unknown`, leaving `Content-Type` unset or empty.&lt;/p&gt;
&lt;p&gt;As a result, uploaded act…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/enchant97/note-mark/backend&lt;/p&gt;
&lt;p&gt;### Summary
A stored same-origin XSS vulnerability allows any authenticated user to upload an HTML, SVG, or XHTML file as a note asset and have it executed in a victim’s browser under the application’s origin. Because the application serves these files inline without a safe content type and without `nosniff`, browsers can sniff and render active content, giving the attacker access to authenticated Note Mark API actions as the victim.&lt;/p&gt;
&lt;p&gt;### Details
This issue results from three compounding flaws in the asset handling and delivery path.&lt;/p&gt;
&lt;p&gt;#### 1. Asset delivery can be used as an attack vector
The asset delivery route can be used to deliver attacker-controlled uploaded content directly to a victim by URL.&lt;/p&gt;
&lt;p&gt;Relevant route:
- `handlers/assets.go:40`&lt;/p&gt;
&lt;p&gt;```go
huma.Get(api, &amp;#34;/api/notes/{noteID}/assets/{assetID}&amp;#34;, h.GetNoteAssetContentByID)
```&lt;/p&gt;
&lt;p&gt;This makes the uploaded asset reachable by direct navigation, which provides the delivery mechanism for the payload.&lt;/p&gt;
&lt;p&gt;#### 2. Text-based active content is served with an empty `Content-Type`
The asset handler relies on `h2non/filetype` for content-type detection:&lt;/p&gt;
&lt;p&gt;- `handlers/assets.go:147`&lt;/p&gt;
&lt;p&gt;```go
kind, _ := filetype.Match(buf)
if kind != filetype.Unknown {
    contentType = kind.MIME.Value
}
```&lt;/p&gt;
&lt;p&gt;The detection library uses magic-byte matching and does not identify text-based formats such as HTML, SVG, JavaScript, XML, or XHTML. For those files, `filetype.Match` returns `Unknown`, leaving `Content-Type` unset or empty.&lt;/p&gt;
&lt;p&gt;As a result, uploaded act…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9pr4-rf97-79qh</guid>
    </item>
  </channel>
</rss>
