A flaw has been found in zosmaai pi-llm-wiki up to 0.11.7. Affected is an unknown function of the file mcp/index.ts of the component wiki_capture_source MCP tool. Executing a manipulation of the argument url can lead to os command injection. The attack can be executed remotely. The exploit has been published and may be used. Upgrading to version 0.11.8 is able to address this issue. This patch is called 360867034e79175b45c8e04a98e4ca712bbaca35. Upgrading the affected component is advised.
CVE-2026-102911
Score 9.9 from GitHub Security Advisory (severity: HIGH) published 2026-09-30. A secondary CVSS source baseline 9.9; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.9
- EG Score
- 9.9CRITICALhigh confidence
- EG Risk
- 50EG Risk 50/100CISA SSVC
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 computedSeverity99% × 45%Exploitation2% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.8%
- EPSS %ILE
- 77th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 30, 2026
Last Modified
September 30, 2026
Advisory Details (5)
Auto-updated Sep 30, 2026v0.11.8
Patch available: zosmaai/pi-llm-wiki v0.11.8
https://github.com/zosmaai/pi-llm-wiki/releases/tag/v0.11.8fix(source-extractors): prevent OS command injection via sh -c (CWE-78) #185
Patch available: zosmaai/pi-llm-wiki v0.11.8 (PR #186 merged 2026-09-01)
https://github.com/zosmaai/pi-llm-wiki/pull/186Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in pi-llm-wiki · Issue #185 · zosmaai/pi-llm-wiki · GitHub
https://github.com/zosmaai/pi-llm-wiki/issues/185commit 360867034e79 (zosmaai/pi-llm-wiki)
Patch available: zosmaai/pi-llm-wiki v0.11.8 (contains commit 360867034e79)
https://github.com/zosmaai/pi-llm-wiki/commit/360867034e79175b45c8e04a98e4ca712bbaca35GitHub - zosmaai/pi-llm-wiki: Self-maintaining, Obsidian-compatible knowledge base for pi — turn raw sources into an interlinked wiki that compounds. Native Open Knowledge Format (OKF) v0.2. · GitHub
https://github.com/zosmaai/pi-llm-wiki/Vendor Advisories for CVE-2026-102911(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 37× in last 7d / 37× 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-10-04 10:06 UTCGHSA enrichment
- 2026-10-04 05:53 UTCGHSA enrichment
- 2026-10-04 01:41 UTCGHSA enrichment
- 2026-10-03 21:27 UTCGHSA enrichment
- 2026-10-03 17:14 UTCEG score recompute
- 2026-10-03 17:14 UTCGHSA enrichment
- 2026-10-03 14:25 UTCEPSS rescore
- 2026-10-03 13:01 UTCGHSA enrichment
- 2026-10-03 08:45 UTCGHSA enrichment
- 2026-10-03 04:30 UTCGHSA enrichment
- 2026-10-03 00:17 UTCGHSA enrichment
- 2026-10-02 20:04 UTCEG score recompute
- 2026-10-02 20:04 UTCGHSA enrichment
- 2026-10-02 15:48 UTCGHSA enrichment
- 2026-10-02 11:35 UTCGHSA enrichment
- 2026-10-02 07:21 UTCGHSA enrichment
- 2026-10-02 03:08 UTCGHSA enrichment
- 2026-10-01 22:55 UTCEG score recompute
- 2026-10-01 22:55 UTCGHSA enrichment
- 2026-10-01 19:49 UTCEPSS rescore
- 2026-10-01 18:42 UTCGHSA enrichment
- 2026-10-01 14:27 UTCGHSA enrichment
- 2026-10-01 10:15 UTCGHSA enrichment
- 2026-10-01 06:02 UTCGHSA enrichment
- 2026-10-01 01:50 UTCGHSA enrichment
Show 12 moreShow fewer
- 2026-09-30 21:37 UTCGHSA enrichment
- 2026-09-30 17:25 UTCEG score recompute
- 2026-09-30 17:25 UTCGHSA enrichment
- 2026-09-30 15:02 UTCEPSS rescore
- 2026-09-30 14:30 UTCGHSA enrichment
- 2026-09-30 12:15 UTCEG score recompute
- 2026-09-30 12:15 UTCGHSA enrichment
- 2026-09-30 08:46 UTCNVD updateCVSS v4 → 8.6
- 2026-09-30 08:02 UTCEG score recompute
- 2026-09-30 08:02 UTCGHSA enrichment
- 2026-09-30 03:49 UTCEG score recompute
- 2026-09-30 03:49 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-77 · CWE-78
Frequently asked(5)
What is CVE-2026-102911?
When was CVE-2026-102911 disclosed?
Is CVE-2026-102911 actively exploited?
What is the CVSS score of CVE-2026-102911?
How do I remediate CVE-2026-102911?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-102911
Is Your Infrastructure Affected by CVE-2026-102911?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.