How severe is CVE-2026-6987?

No CVSS score has been assigned to CVE-2026-6987 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-6987?

CVE-2026-6987 affects the following packages: github.com/sipeed/picoclaw (Go). Ecosystems affected: Go.

How do I fix CVE-2026-6987?

The records we use list no patched version of github.com/sipeed/picoclaw for CVE-2026-6987. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2026-6987 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/sipeed/picoclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-6987 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2026-6987 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-6987 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-6987?

CVE-2026-6987 has an EPSS (Exploit Prediction Scoring System) score of 3.4%, placing it in the 89th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-6987?

CVE-2026-6987 is classified as CWE-74 (CWE-74), CWE-77 (CWE-77). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-6987 published, and has it been updated?

CVE-2026-6987 was published on April 25, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-6987 — picoclaw

CVE-2026-6987 is a CWE-74 vulnerability in github.com/sipeed/picoclaw. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

PicoClaw Web Launcher Management Plane restart command injection

Also known asGHSA-6r3x-h84w-fhxxGO-2026-5187

Published

Apr 25, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-6987.

EPSS Exploitation Probability

via FIRST.org ↗

3.4%probability of exploitation in next 30 days

Lower Risk-1.22%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/sipeed/picoclaw

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability was detected in PicoClaw up to 0.2.4. Impacted is an unknown function of the file /api/gateway/restart of the component Web Launcher Management Plane. Performing a manipulation results in command injection. It is possible to initiate the attack remotely. The project was informed of the problem early through an issue report but has not responded yet.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/sipeed/picoclaw`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

picoclawsipeed

≤ 0.2.4

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/sipeed/picoclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/sipeed/picoclaw for CVE-2026-6987. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-6987 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works