A flaw has been found in nextlevelbuilder GoClaw up to 3.13.2. Affected by this vulnerability is the function ExecTool.Execute of the file goclaw/internal/http/tools_invoke.go of the component jq Handler. Executing a manipulation can lead to information disclosure. The attack can be launched remotely. The exploit has been published and may be used. This patch is called 1230. It is advisable to implement a patch to correct this issue.
CVE-2026-18038
Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-07-28. a secondary CVSS source baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 13%
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 28, 2026
Advisory Details (3)
Auto-updated Jul 28, 2026GitHub - nextlevelbuilder/goclaw: GoClaw - GoClaw is OpenClaw rebuilt in Go — with multi-tenant isolation, 5-layer security, and native concurrency. Deploy AI agent teams at scale without compromising on safety. · GitHub
https://github.com/nextlevelbuilder/goclaw/Sync digitop dev changes into upstream dev
Patch available: nextlevelbuilder/goclaw v3.15.0-beta.149 (PR #1230 merged 2026-06-15)
https://github.com/nextlevelbuilder/goclaw/pull/1230[Security] Authenticated operator can exfiltrate `GOCLAW_GATEWAY_TOKEN` through auto-approved `jq` execution · Issue #1226 · nextlevelbuilder/goclaw · GitHub
https://github.com/nextlevelbuilder/goclaw/issues/1226Vendor Advisories for CVE-2026-18038(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 21:27 UTCGHSA enrichment
- 2026-07-28 20:45 UTCGHSA enrichment
- 2026-07-28 20:27 UTCEG score recompute
- 2026-07-28 20:27 UTCGHSA enrichment
- 2026-07-28 20:24 UTCNVD updateCVSS v4 → 2.1
- 2026-07-28 19:31 UTCEG score recompute
- 2026-07-28 19:30 UTCGHSA enrichment
- 2026-07-28 19:27 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-07-28 13:33 UTCEG score recompute
- 2026-07-28 13:31 UTCNVD updateCVSS v4 → 2.1
- 2026-07-28 13:05 UTCEG score recompute
- 2026-07-28 13:03 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-18038?
When was CVE-2026-18038 disclosed?
Is CVE-2026-18038 actively exploited?
What is the CVSS score of CVE-2026-18038?
How do I remediate CVE-2026-18038?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18038
Is Your Infrastructure Affected by CVE-2026-18038?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.