CVE-2026-16082Public exploit

Approval bypass via working-directory symlink race

Published Jul 18, 2026 · Updated Jul 18, 2026

A TOCTOU race in Sipeed PicoClaw 0.2.0 through 0.2.9 allows local users to redirect approved shell execution within a workspace. The approval pipeline passes the raw cwd to a hook, then ExecTool.executeRun resolves that path again before launch, so a swapped symlink changes the command's directory. Reachability requires enabled hooks and exec, an attacker-controlled workspace symlink, and the ability to alter it while approval is pending; effects are limited to relative reads, writes, and directory-sensitive command behavior inside the workspace.

CVSS severity5.3
Medium
EPSS probability0.12%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

A TOCTOU race in Sipeed PicoClaw 0.2.0 through 0.2.9 allows local users to redirect approved shell execution within a workspace. The approval pipeline passes the raw cwd to a hook, then ExecTool.executeRun resolves that path again before launch, so a swapped symlink changes the command's directory. Reachability requires enabled hooks and exec, an attacker-controlled workspace symlink, and the ability to alter it while approval is pending; effects are limited to relative reads, writes, and directory-sensitive command behavior inside the workspace.

The record

CVE
CVE-2026-16082
Published
Jul 18, 2026
Updated
Jul 18, 2026
Vendor
Sipeed
Product
PicoClaw
Classifications
CWE-362, CWE-367, T1059
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0.2.0
  2. Affected versionversion=0.2.1
  3. Affected versionversion=0.2.2
  4. Affected versionversion=0.2.3
  5. Affected versionversion=0.2.4
  6. Affected versionversion=0.2.5
  7. Affected versionversion=0.2.6
  8. Affected versionversion=0.2.7
  9. Affected versionversion=0.2.8
  10. Affected versionversion=0.2.9

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Sipeed · PicoClawversion=0.2.0; version=0.2.1; version=0.2.2; version=0.2.3; version=0.2.4; version=0.2.5; version=0.2.6; version=0.2.7; version=0.2.8; version=0.2.9

Published CVSS scores

1.9VulDBCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
5.3VulDBCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
4.3VulDBAV:L/AC:L/Au:S/C:P/I:P/A:P

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
T1059Command and Scripting Interpreter

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo