A vulnerability was identified in nearai ironclaw up to 0.29.1. The affected element is the function validate_path of the file src/tools/builtin/path_utils.rs of the component write_file. The manipulation leads to link following. Local access is required to approach this attack. The exploit is publicly available and might be used. The identifier of the patch is 369ff3d240cf3c0787b50e1e9f182e1a06c71255. It is recommended to apply a patch to fix this issue.
CVE-2026-16130
Score 4.4 from GitHub Security Advisory (severity: LOW) published 2026-07-18. a secondary CVSS source baseline 4.4; 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.4
- EG Score
- 4.4(high)
- EG Risk
- 36(Track)EG Risk 36/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 computedSeverity44% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 3.6%
- KEV
- Not listed
Published
July 18, 2026
Last Modified
July 20, 2026
Advisory Details (4)
Auto-updated Jul 18, 2026GitHub - nearai/ironclaw: IronClaw is an Agent OS focused on privacy, security and extensibility · GitHub
https://github.com/nearai/ironclaw/commit 369ff3d240cf (nearai/ironclaw)
Fix landed in nearai/ironclaw commit 369ff3d240cf — awaiting tagged release
https://github.com/nearai/ironclaw/commit/369ff3d240cf3c0787b50e1e9f182e1a06c71255fix(security): tool boundary checks
Fix merged in nearai/ironclaw PR #4869 on 2026-06-16 — awaiting tagged release
https://github.com/nearai/ironclaw/pull/4869[Security] `write_file` sandbox can be escaped through a dangling final symlink in IronClaw · Issue #4797 · nearai/ironclaw · GitHub
https://github.com/nearai/ironclaw/issues/4797Vendor Advisories for CVE-2026-16130(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× 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-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 18:40 UTCNVD updateCVSS v4 → 1.9
- 2026-07-20 17:52 UTCEG score recompute
- 2026-07-20 17:52 UTCGHSA enrichment
- 2026-07-20 17:09 UTCMITRE cvelistV5CVSS v4 → 4.8
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 20:05 UTCEG score recompute
- 2026-07-18 20:05 UTCGHSA enrichment
- 2026-07-18 20:04 UTCNVD updateCVSS v4 → 1.9
- 2026-07-18 17:39 UTCEG score recompute
- 2026-07-18 17:39 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-16130?
When was CVE-2026-16130 disclosed?
Is CVE-2026-16130 actively exploited?
What is the CVSS score of CVE-2026-16130?
How do I remediate CVE-2026-16130?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16130
Is Your Infrastructure Affected by CVE-2026-16130?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.