<?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, 17 Nov 2026 05:03:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-396815</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-396815</link>
      <description>EUVD-2026-396815</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-396815</guid>
    </item>
    <item>
      <title>fkie_cve-2026-119298</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-119298</link>
      <description>&lt;p&gt;croc is a tool that allows any two computers to simply and securely transfer files and folders. Prior to 11.5.2, the receive-side file-readiness loop in src/croc/croc.go treats any sender-controlled basename beginning with croc-stdin- as a trusted text-transfer artifact even when SendingText is false. This skips askReceiveOverwrite and rename handling for a predictable exact-name collision in the receiver&amp;#39;s working directory, allowing a remote sender whose transfer the user accepts to overwrite or truncate a matching regular file through recipientInitializeFile, or to remove and replace a matching destination with an empty file or an in-directory symlink through createEmptyFileAndFinish, without confirmation. The impact is limited to pre-existing names in the croc-stdin- namespace that the sender can predict; other filenames retain the prompt, dotfiles outside that namespace are not reachable, and symlink targets remain confined to the receive directory. This issue is fixed in version 11.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;croc is a tool that allows any two computers to simply and securely transfer files and folders. Prior to 11.5.2, the receive-side file-readiness loop in src/croc/croc.go treats any sender-controlled basename beginning with croc-stdin- as a trusted text-transfer artifact even when SendingText is false. This skips askReceiveOverwrite and rename handling for a predictable exact-name collision in the receiver&amp;#39;s working directory, allowing a remote sender whose transfer the user accepts to overwrite or truncate a matching regular file through recipientInitializeFile, or to remove and replace a matching destination with an empty file or an in-directory symlink through createEmptyFileAndFinish, without confirmation. The impact is limited to pre-existing names in the croc-stdin- namespace that the sender can predict; other filenames retain the prompt, dotfiles outside that namespace are not reachable, and symlink targets remain confined to the receive directory. This issue is fixed in version 11.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-119298</guid>
    </item>
    <item>
      <title>GHSA-x89h-7h96-v88f — croc: Overwrite-confirmation bypass via a crafted "croc-stdin-" filename on receive</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x89h-7h96-v88f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/schollz/croc/v11, Go: github.com/schollz/croc/v10, Go: github.com/schollz/croc/v9, Go: github.com/schollz/croc/v8, Go: github.com/schollz/croc/v6, Go: github.com/schollz/croc&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;croc is an end-to-end encrypted peer-to-peer file transfer tool. On the receiving side, the confirmation that normally protects an existing file from being overwritten or resumed is skipped whenever the received file&amp;#39;s name starts with `croc-stdin-`, regardless of whether the incoming transfer is actually a text transfer. A sender can therefore name a file `croc-stdin-&amp;lt;existing-name&amp;gt;` and silently overwrite, truncate, or replace an existing file of that name in the receiver&amp;#39;s working directory - including removing the existing file and substituting a symlink - without the `Overwrite?` prompt that the standard path requires. The exemption was introduced to keep croc&amp;#39;s internal text-transfer artifacts from triggering prompts, but it is keyed on the filename prefix rather than on the transfer type, so any ordinary file transfer can claim the exemption.&lt;/p&gt;
&lt;p&gt;## Vulnerability Details&lt;/p&gt;
&lt;p&gt;Affected code at commit `b6f27da9401f2c3647c1adb6b77a46bb8c0923d2` (HEAD, v11.5.1+1):&lt;/p&gt;
&lt;p&gt;The receive-side file-readiness loop in `src/croc/croc.go` decides whether to prompt before overwriting or resuming an existing destination file. The decision is made around line 3413:&lt;/p&gt;
&lt;p&gt;```go
isStdinName := strings.HasPrefix(path.Base(fileInfo.Name), &amp;#34;croc-stdin-&amp;#34;)
...
if destinationExists &amp;amp;&amp;amp; !c.Options.Overwrite &amp;amp;&amp;amp; !c.Options.Rename &amp;amp;&amp;amp; !isStdinName {
    resumable := fileInfo.Size &amp;gt; 0 &amp;amp;&amp;amp; fileInfo.Symlink == &amp;#34;&amp;#34; &amp;amp;&amp;amp; recipientFileInfo.Mode().IsRegular()
    overwrite, promptErr := askReceiveOverwrite(c.client…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/schollz/croc/v11, Go: github.com/schollz/croc/v10, Go: github.com/schollz/croc/v9, Go: github.com/schollz/croc/v8, Go: github.com/schollz/croc/v6, Go: github.com/schollz/croc&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;croc is an end-to-end encrypted peer-to-peer file transfer tool. On the receiving side, the confirmation that normally protects an existing file from being overwritten or resumed is skipped whenever the received file&amp;#39;s name starts with `croc-stdin-`, regardless of whether the incoming transfer is actually a text transfer. A sender can therefore name a file `croc-stdin-&amp;lt;existing-name&amp;gt;` and silently overwrite, truncate, or replace an existing file of that name in the receiver&amp;#39;s working directory - including removing the existing file and substituting a symlink - without the `Overwrite?` prompt that the standard path requires. The exemption was introduced to keep croc&amp;#39;s internal text-transfer artifacts from triggering prompts, but it is keyed on the filename prefix rather than on the transfer type, so any ordinary file transfer can claim the exemption.&lt;/p&gt;
&lt;p&gt;## Vulnerability Details&lt;/p&gt;
&lt;p&gt;Affected code at commit `b6f27da9401f2c3647c1adb6b77a46bb8c0923d2` (HEAD, v11.5.1+1):&lt;/p&gt;
&lt;p&gt;The receive-side file-readiness loop in `src/croc/croc.go` decides whether to prompt before overwriting or resuming an existing destination file. The decision is made around line 3413:&lt;/p&gt;
&lt;p&gt;```go
isStdinName := strings.HasPrefix(path.Base(fileInfo.Name), &amp;#34;croc-stdin-&amp;#34;)
...
if destinationExists &amp;amp;&amp;amp; !c.Options.Overwrite &amp;amp;&amp;amp; !c.Options.Rename &amp;amp;&amp;amp; !isStdinName {
    resumable := fileInfo.Size &amp;gt; 0 &amp;amp;&amp;amp; fileInfo.Symlink == &amp;#34;&amp;#34; &amp;amp;&amp;amp; recipientFileInfo.Mode().IsRegular()
    overwrite, promptErr := askReceiveOverwrite(c.client…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x89h-7h96-v88f</guid>
    </item>
  </channel>
</rss>
