Claude Code v2.1.281 ·
upload_asset refuses network paths and unvettable link chains
upload_asset now refuses network paths, device paths and symlinks it cannot fully check
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ChromeArea: what it touches
ImprovementsKind: in v2.1.281,
ImprovementsSection of the release
Unclear The finding does not say how upload_asset is reached or whether the 256 depth constant is the symlink limit.
What
upload_asset now refuses a file path when it:
- Is a Windows network share (UNC path)
- Is under a
/net automount
- Is a device-style path
- Reaches one of these through a symlink, which is a file that points to another location
- Has a part that could not be examined
A separate ELOOP error covers chains of symlinks too long to check. The refusal message says upload_asset reads only local files.
Why
Only files actually on your machine can be uploaded, so a path cannot quietly send something from a network location.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe finding does not say how `upload_asset` is reached or whether the 256 depth constant is the symlink limit.
See this entry in the whole of v2.1.281 →
