thClaws EUVD-2026-97000

Exploitation requires two preconditions working together: (1) the attacker must be able to plant a symbolic link under the allowed inputs/ prefix pointing outside the workspace, and (2) a subsequent AUTHENTICATED upload to the v1 API POST /v1/inputs endpoint must target that path so the post_inputs handler follows the symlink. The damaging write/truncation only occurs on that later authenticated upload and executes with daemon privileges. Limiting factors: affected only in thClaws versions through 0.141.0; needs the pre-staged symlink plus a real authenticated upload event (reflected as AT:P and UI:P in the vendor vector), so a single unauthenticated request cannot trigger it; impact is confined to writing/truncating files (integrity/availability), with no confidentiality disclosure.

This is a genuinely low-priority issue by all available signals, and they agree with each other rather than conflict. The vendor-supplied CVSS 4.0 vector (CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:L) yields a base score of only 2.3, driven down by the attack requirement (AT:P) and required passive user interaction (UI:P): the flaw is not a single-shot remote exploit but a two-stage chain requiring a pre-planted symlink plus a later legitimate authenticated upload. Impact is limited to Low integrity and Low availability (file write/truncation outside the workspace) with no confidentiality exposure (VC:N), so this is a sandbox/path-escape and data-corruption bug, not a code-execution or data-theft bug - despite running with daemon privileges. No EPSS score was provided, there is no CISA KEV listing, and no public proof-of-concept is referenced, so exploitation status is 'no public exploit identified at time of analysis.' CONFLICT TO NOTE: the input Tag 'Information Disclosure' directly contradicts the CVSS impact profile (VC:N, with integrity/availability impact only) and the CWE-59 link-following classification - this is a file-write/symlink-escape weakness, not an information-disclosure one, and the tag appears mislabeled. Net: a real but low-severity hardening bug affecting an obscure product; not an urgent patch priority absent a specific threat to a thClaws deployment.

An attacker first plants a symbolic link under the allowed inputs/ prefix pointing to a sensitive path outside the workspace (e.g. a daemon config or data file). Later, when a legitimate authenticated user uploads to POST /v1/inputs and the handler follows that symlink, the daemon writes or truncates the targeted out-of-workspace file with its own privileges, corrupting or destroying data. No public exploit code is identified at time of analysis, and the attack depends on the pre-planted symlink plus a subsequent authenticated upload actually occurring.