A security vulnerability has been detected in cosmicstack-labs mercury-agent up to 1.2.0. This impacts the function checkShellCommand of the file src/capabilities/permissions.ts of the component Shell Command Permission. The manipulation leads to incorrect privilege assignment. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-90812
Score 4.3 from GitHub Security Advisory (severity: LOW) published 2026-09-14. 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
September 14, 2026
Last Modified
September 16, 2026
Advisory Details (2)
Auto-updated Sep 14, 2026[Security] Mercury Agent safe-read shell approval bypass allows environment variable disclosure via `echo $VAR` · Issue #80 · cosmicstack-labs/mercury-agent · GitHub
https://github.com/cosmicstack-labs/mercury-agent/issues/80GitHub - cosmicstack-labs/mercury-agent: Soul-driven AI agent with permission-hardened tools, token budgets, and multi-channel access. Runs 24/7 from CLI or Telegram. · GitHub
https://github.com/cosmicstack-labs/mercury-agent/Vendor Advisories for CVE-2026-90812(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 19× in last 7d / 19× 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-09-19 18:57 UTCEG score recompute
- 2026-09-19 18:57 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:15 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEG score recompute
- 2026-09-17 19:32 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 17:51 UTCEG score recompute
- 2026-09-16 17:51 UTCGHSA enrichment
- 2026-09-16 17:21 UTCNVD updateCVSS v4 → 2.1
- 2026-09-16 16:55 UTCEG score recompute
- 2026-09-16 16:55 UTCGHSA enrichment
- 2026-09-16 16:19 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 20:47 UTCEG score recompute
- 2026-09-15 20:47 UTCGHSA enrichment
- 2026-09-14 19:19 UTCEG score recompute
- 2026-09-14 19:18 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-266
Frequently asked(5)
What is CVE-2026-90812?
When was CVE-2026-90812 disclosed?
Is CVE-2026-90812 actively exploited?
What is the CVSS score of CVE-2026-90812?
How do I remediate CVE-2026-90812?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-90812
Is Your Infrastructure Affected by CVE-2026-90812?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.