Context7 through 2.1.2 contains a prompt injection vulnerability that allows attackers to execute malicious instructions in connected AI coding agents by injecting unsanitized content through the Custom AI Instructions feature served via the MCP server. Attackers can poison the custom instructions to exfiltrate credentials from environment files to an attacker-controlled service and perform destructive file deletion on the victim's machine when the agent makes a routine library documentation request.
CVE-2026-75130
Score 9.0 from GitHub Security Advisory published 2026-08-18. a secondary CVSS source baseline 9.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.0
- EG Score
- 9.0(high)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity90% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 19, 2026
Advisory Details (3)
Auto-updated Aug 18, 2026Context7 2.1.2 Prompt Injection via Custom AI Instructions | Advisories | VulnCheck
https://www.vulncheck.com/advisories/context7-prompt-injection-via-custom-ai-instructionsContext7 Security: AI Agent Vulnerability Mitigation | Upstash posted on the topic | LinkedIn
https://www.linkedin.com/posts/upstash_mcp-server-vulnerability-in-context-7-activity-7435686676049387520-PBVo/ContextCrush: The Context7 MCP Server Vulnerability Hiding in Plain Sight - Noma Security
https://noma.security/blog/contextcrush-context7-the-mcp-server-vulnerability/Vendor Advisories for CVE-2026-75130(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 17× in last 7d / 17× 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-08-20 09:08 UTCGHSA enrichment
- 2026-08-20 04:58 UTCGHSA enrichment
- 2026-08-20 00:47 UTCGHSA enrichment
- 2026-08-19 20:36 UTCEG score recompute
- 2026-08-19 20:36 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:26 UTCEG score recompute
- 2026-08-19 16:26 UTCGHSA enrichment
- 2026-08-19 15:19 UTCGHSA enrichment
- 2026-08-19 11:05 UTCGHSA enrichment
- 2026-08-19 06:55 UTCGHSA enrichment
- 2026-08-19 02:45 UTCGHSA enrichment
- 2026-08-18 22:32 UTCEG score recompute
- 2026-08-18 22:32 UTCGHSA enrichment
- 2026-08-18 18:22 UTCEG score recompute
- 2026-08-18 18:15 UTCEG score recompute
- 2026-08-18 18:14 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-75130?
When was CVE-2026-75130 disclosed?
Is CVE-2026-75130 actively exploited?
What is the CVSS score of CVE-2026-75130?
How do I remediate CVE-2026-75130?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75130
Is Your Infrastructure Affected by CVE-2026-75130?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.