Live › vulnerability › CVE-2026-119298
croc, a tool for sending files between two computers, skips its overwrite prompt for files whose names start with croc-stdin- even when the transfer is a normal file transfer. A remote sender whose transfer the user accepted can then overwrite, truncate, or replace a matching file in the receiver's working directory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 17:31 UTC. All times on this page are UTC.
Anyone who runs croc to receive files from another computer before version 11.5.2. The impact is limited to pre-existing files whose names start with croc-stdin- in the receiving directory; other filenames still get the overwrite prompt, and symlink targets stay inside the receive directory.
No product ranges from the sources yet.
croc --version; versions below 11.5.2 are affected.croc-stdin-* in the directories where you receive transfers.11.5.2 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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'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.
This page as .md · .json · in your agent: get_signal("CVE-2026-119298")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.