CVE-2026-108839 thClaws CVE debrief

Who should care

Defenders responsible for thClaws installations, especially those with authenticated API access, should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify and remediate this vulnerability to prevent potential unauthorized file writes or data corruption.

Why it matters

This vulnerability allows attackers to write or truncate files outside the workspace with daemon privileges, potentially leading to unauthorized data changes or corruption. Defenders should prioritize verifying and remediating this vulnerability in thClaws installations, especially in environments where authenticated access to the API is possible. The impact is currently limited by the lack of information on exploitation or specific affected versions.

• Potential for unauthorized file writes outside the workspace
• Possible data truncation or corruption
• Need for verification of affected versions and remediation
• Importance of monitoring API activity for suspicious behavior

Technical summary

The post_inputs handler of the v1 API POST /v1/inputs endpoint in thClaws through 0.141.0 does not properly handle symlinks, allowing attackers to write or truncate files outside the workspace with daemon privileges by planting a symlink under the allowed inputs/ prefix. This vulnerability can lead to unauthorized data changes or corruption. Defenders should prioritize verifying and remediating this vulnerability in thClaws installations, especially in environments where authenticated access to the API is possible.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in thClaws installations, especially in environments where authenticated access to the API is possible.

Recommended defensive actions

• Verify thClaws installations for version 0.141.0 or earlier
• Assess exposure in environments with authenticated API access
• Consider upgrading to a patched version if available
• Monitor for suspicious API activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, additional information on exploitation or impact is limited. Defenders should verify thClaws installations, especially in environments with authenticated API access, and monitor for suspicious activity. The lack of information on specific affected versions or exploitation history makes it crucial to assess exposure and prioritize remediation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.