<?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://db.gcve.eu</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, 06 Oct 2026 18:10:03 +0000</lastBuildDate>
    <item>
      <title>GHSA-xf4j-xp2r-rqqx — Hono: Path traversal in toSSG() allows writing files outside the output directory</title>
      <link>https://db.gcve.eu/vuln/ghsa-xf4j-xp2r-rqqx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: hono&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;A path traversal issue in `toSSG()` allows files to be written outside the configured output directory during static site generation. When using dynamic route parameters via `ssgParams`, specially crafted values can cause generated file paths to escape the intended output directory.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The static site generation process creates output files based on route paths derived from application routes and parameters. When `ssgParams` is used to provide values for dynamic routes, those values are used to construct output file paths. If these values contain traversal sequences (e.g. `..`), the resulting output path may resolve outside the configured output directory. As a result, files may be written to unintended locations instead of being confined within the specified output directory.&lt;/p&gt;
&lt;p&gt;For example:
 
```ts
import { Hono } from &amp;#39;hono&amp;#39;
import { toSSG, ssgParams } from &amp;#39;hono/ssg&amp;#39;&lt;/p&gt;
&lt;p&gt;const app = new Hono()&lt;/p&gt;
&lt;p&gt;app.get(&amp;#39;/:id&amp;#39;, ssgParams([{ id: &amp;#39;../pwned&amp;#39; }]), (c) =&amp;gt; {
  return c.text(&amp;#39;pwned&amp;#39;)
})&lt;/p&gt;
&lt;p&gt;toSSG(app, fs, { dir: &amp;#39;./static&amp;#39; })
```&lt;/p&gt;
&lt;p&gt;In this case, the generated output path may resolve outside `./static`, resulting in a file being written outside the intended output directory.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can influence values passed to `ssgParams` during the build process may be able to write files outside the intended output directory.&lt;/p&gt;
&lt;p&gt;Depending on the build and deployment environment, this may:&lt;/p&gt;
&lt;p&gt;* overwrite unintended files
* affect generated artifacts
* impact deplo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: hono&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;A path traversal issue in `toSSG()` allows files to be written outside the configured output directory during static site generation. When using dynamic route parameters via `ssgParams`, specially crafted values can cause generated file paths to escape the intended output directory.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The static site generation process creates output files based on route paths derived from application routes and parameters. When `ssgParams` is used to provide values for dynamic routes, those values are used to construct output file paths. If these values contain traversal sequences (e.g. `..`), the resulting output path may resolve outside the configured output directory. As a result, files may be written to unintended locations instead of being confined within the specified output directory.&lt;/p&gt;
&lt;p&gt;For example:
 
```ts
import { Hono } from &amp;#39;hono&amp;#39;
import { toSSG, ssgParams } from &amp;#39;hono/ssg&amp;#39;&lt;/p&gt;
&lt;p&gt;const app = new Hono()&lt;/p&gt;
&lt;p&gt;app.get(&amp;#39;/:id&amp;#39;, ssgParams([{ id: &amp;#39;../pwned&amp;#39; }]), (c) =&amp;gt; {
  return c.text(&amp;#39;pwned&amp;#39;)
})&lt;/p&gt;
&lt;p&gt;toSSG(app, fs, { dir: &amp;#39;./static&amp;#39; })
```&lt;/p&gt;
&lt;p&gt;In this case, the generated output path may resolve outside `./static`, resulting in a file being written outside the intended output directory.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;An attacker who can influence values passed to `ssgParams` during the build process may be able to write files outside the intended output directory.&lt;/p&gt;
&lt;p&gt;Depending on the build and deployment environment, this may:&lt;/p&gt;
&lt;p&gt;* overwrite unintended files
* affect generated artifacts
* impact deplo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-xf4j-xp2r-rqqx</guid>
    </item>
  </channel>
</rss>
