<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>File Uploads on Nalar</title>
    <link>https://nalar.dev/tags/file-uploads/</link>
    <description>Recent content in File Uploads on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/file-uploads/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Treat File Uploads as Untrusted Content</title>
      <link>https://nalar.dev/treat-file-uploads-as-untrusted-content/</link>
      <pubDate>Mon, 07 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/treat-file-uploads-as-untrusted-content/</guid>
      <description>&lt;p&gt;A file-upload feature can appear simple: accept bytes, save them, and let another user download them later. The security problem is that the uploaded file crosses several trust boundaries. Its name, declared type, contents, and eventual delivery behavior are all influenced by the uploader.&lt;/p&gt;&#xA;&lt;p&gt;If the application treats any of those properties as trustworthy, an ordinary upload can become an unintended way to consume excessive resources, overwrite data, feed dangerous content into a parser, or make a browser handle attacker-controlled bytes in a more powerful context than intended.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
