How severe is CVE-2026-10219?

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

Which packages are affected by CVE-2026-10219?

CVE-2026-10219 affects the following packages: github.com/nextlevelbuilder/goclaw (Go). Ecosystems affected: Go.

How do I fix CVE-2026-10219?

The records we use list no patched version of github.com/nextlevelbuilder/goclaw for CVE-2026-10219. 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-10219 in my Go dependencies?

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

How do I mitigate CVE-2026-10219 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-10219 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-10219 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-10219?

CVE-2026-10219 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th 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-10219?

CVE-2026-10219 is classified as CWE-77 (CWE-77), OS Command Injection (CWE-78). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2026-10219 was published on June 1, 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-10219 — goclaw

Fix: nextlevelbuilder/goclaw#1155

CVE-2026-10219 is a CWE-77 vulnerability in github.com/nextlevelbuilder/goclaw. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

nextlevelbuilder GoClaw write_file Tool fsbridge.go FsBridge.WriteFile os command injection

Also known asGHSA-6jm8-4fhr-5w64GO-2026-5951

Published

Jun 1, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% 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/nextlevelbuilder/goclaw

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 found in nextlevelbuilder GoClaw up to 3.11.3. This impacts the function FsBridge.WriteFile of the file internal/sandbox/fsbridge.go of the component write_file Tool. Performing a manipulation results in os command injection. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.

Affected Packages

1 total

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

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/nextlevelbuilder/goclaw, 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/nextlevelbuilder/goclaw for CVE-2026-10219. 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-10219 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works