<?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://vulnerability.circl.lu</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>Sun, 11 Oct 2026 21:40:36 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-108258</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-108258</link>
      <description>&lt;p&gt;Shiny for Python is a framework for building interactive web applications in Python. From 1.4.0 until 1.6.4, bookmark restore accepts a client-supplied state_id and joins it into the server-side shiny_bookmarks directory without validating that it is a single safe path segment. An unauthenticated request can use parent-directory segments or an absolute path to make the server open input.json and values.json outside the bookmark store, even when bookmark_store is set to disable. In applications configured with bookmark_store set to server and using ui.input_file(), the restore handler can additionally copy and expose an attacker-selected file from an attacker-selected directory. This issue is fixed in version 1.6.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Shiny for Python is a framework for building interactive web applications in Python. From 1.4.0 until 1.6.4, bookmark restore accepts a client-supplied state_id and joins it into the server-side shiny_bookmarks directory without validating that it is a single safe path segment. An unauthenticated request can use parent-directory segments or an absolute path to make the server open input.json and values.json outside the bookmark store, even when bookmark_store is set to disable. In applications configured with bookmark_store set to server and using ui.input_file(), the restore handler can additionally copy and expose an attacker-selected file from an attacker-selected directory. This issue is fixed in version 1.6.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-108258</guid>
    </item>
    <item>
      <title>GHSA-47c3-hpmg-7j6p — Shiny for Python has path traversal in bookmark restore</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-47c3-hpmg-7j6p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: shiny&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Shiny for Python&amp;#39;s bookmark-restore path accepted a client-supplied `_state_id_`
query-string value and joined it into the server-side bookmark directory
(`&amp;lt;cwd&amp;gt;/shiny_bookmarks/&amp;lt;id&amp;gt;`) without validating it. A value containing `..`
path segments, or an absolute path, could therefore cause the server to open and
parse `input.json` and `values.json` from a directory outside the bookmark store.&lt;/p&gt;
&lt;p&gt;On a default application the restore was attempted whenever the client supplied a
URL query string — including when bookmarking was disabled
(`bookmark_store=&amp;#34;disable&amp;#34;`) — so no opt-in configuration was required. For such
applications the impact is an unauthenticated, server-side probe for the
existence and JSON-validity of attacker-chosen paths, constrained to those two
file names.&lt;/p&gt;
&lt;p&gt;Applications configured with `bookmark_store=&amp;#34;server&amp;#34;` **and** using
`ui.input_file()` are affected more seriously. The file-input restore handler
copies files out of the restore directory, so the contents of an
attacker-selected file name within an attacker-selected directory could be read
into the application.&lt;/p&gt;
&lt;p&gt;### Affected versions&lt;/p&gt;
&lt;p&gt;1.4.0 through 1.6.3. Bookmarking was introduced in 1.4.0; earlier releases do
not contain the affected code path and are not affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in **1.6.4**. Upgrade with:&lt;/p&gt;
&lt;p&gt;```
pip install --upgrade shiny
```&lt;/p&gt;
&lt;p&gt;The fix validates bookmark IDs against an allowlist — a single path segment
matching `[A-Za-z0-9_-]+`, which cannot express a path separator, a `…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: shiny&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Shiny for Python&amp;#39;s bookmark-restore path accepted a client-supplied `_state_id_`
query-string value and joined it into the server-side bookmark directory
(`&amp;lt;cwd&amp;gt;/shiny_bookmarks/&amp;lt;id&amp;gt;`) without validating it. A value containing `..`
path segments, or an absolute path, could therefore cause the server to open and
parse `input.json` and `values.json` from a directory outside the bookmark store.&lt;/p&gt;
&lt;p&gt;On a default application the restore was attempted whenever the client supplied a
URL query string — including when bookmarking was disabled
(`bookmark_store=&amp;#34;disable&amp;#34;`) — so no opt-in configuration was required. For such
applications the impact is an unauthenticated, server-side probe for the
existence and JSON-validity of attacker-chosen paths, constrained to those two
file names.&lt;/p&gt;
&lt;p&gt;Applications configured with `bookmark_store=&amp;#34;server&amp;#34;` **and** using
`ui.input_file()` are affected more seriously. The file-input restore handler
copies files out of the restore directory, so the contents of an
attacker-selected file name within an attacker-selected directory could be read
into the application.&lt;/p&gt;
&lt;p&gt;### Affected versions&lt;/p&gt;
&lt;p&gt;1.4.0 through 1.6.3. Bookmarking was introduced in 1.4.0; earlier releases do
not contain the affected code path and are not affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in **1.6.4**. Upgrade with:&lt;/p&gt;
&lt;p&gt;```
pip install --upgrade shiny
```&lt;/p&gt;
&lt;p&gt;The fix validates bookmark IDs against an allowlist — a single path segment
matching `[A-Za-z0-9_-]+`, which cannot express a path separator, a `…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-47c3-hpmg-7j6p</guid>
    </item>
  </channel>
</rss>
