CVE-2026-119298

croc: Overwrite-confirmation bypass via a crafted "croc-stdin-" filename on receive

Published Oct 30, 2026 CVSS 3.1 · 4.2 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

croc allows direct file transfers. Prior to v11.5.2, the receive side treats any filename starting with croc-stdin- as a trusted artifact even when the transfer is not text. This bypasses confirmation prompts and enables a sender to overwrite or truncate existing files in the receiver's working directory that match that pattern, without the user’s awareness. The vulnerability allows an attacker who can send a file to a victim to remove or replace a specific file, potentially leading to data loss.

Affected Systems

The vulnerability affects the croc tool provided by schollz, specifically versions earlier than 11.5.2.

Risk and Exploitability

CVSS 4.2 indicates a medium severity. EPSS is less than 1%, and the vulnerability is not listed in the CISA KEV catalog. Exposures require a network connection from the attacker to the victim's croc instance and user acceptance of the transfer, making it a remote attack that can overwrite local files. Given the lack of public exploitation data, the risk remains moderate but still warrants attention, especially in environments where critical files could be targeted.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade croc to version 11.5.2 or later to apply the patch that enforces overwrite confirmation for croc-stdin- artifacts.
  • Avoid accepting file transfers from untrusted senders, especially those that use filenames beginning with croc-stdin-.
  • If an upgrade is not possible, isolate the receiver's working directory from critical system files or use an alternate directory for croc transfers to limit the impact area.

Generated by OpenCVE AI on November 6, 2026 at 01:59 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-x89h-7h96-v88f croc: Overwrite-confirmation bypass via a crafted "croc-stdin-" filename on receive
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Schollz
Schollz croc
Vendors & Products Schollz
Schollz croc
Type Values Removed Values Added
Description 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.
Title croc: Overwrite-confirmation bypass via a crafted "croc-stdin-" filename on receive
Weaknesses CWE-73
References
Metrics cvssV3_1

{'score': 4.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L'}

Weaknesses
  • CWE-73

    External Control of File Name or Path

  • CWE-807

    Reliance on Untrusted Inputs in a Security Decision

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 6:35 PM
Reserved
Oct 29, 2026, 6:50 PM
Status
Deferred
Published
Oct 30, 2026, 5:17 PM
Modified
Oct 30, 2026, 7:39 PM
Severity
Moderate
Public date
Oct 30, 2026, 4:12 PM