GHSA-6q9c-m9fr-865m
vet MCP Server SSE Transport DNS Rebinding Vulnerability
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/safedep/vetReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
SafeDep vet is vulnerable to a DNS rebinding attack due to lack of HTTP Host and Origin header validation.
To exploit this vulnerability following conditions must be met:
- A
vetscan is executed and reports are saved assqlite3database - A
vetMCP server is running on default port with SSE transport that has access to the report database - The attacker lures the victim to attacker controlled website
- Attacker leverages DNS rebinding to access
vetSSE server on127.0.0.1through the website - Attacker uses MCP tools to read information from report database
Impact
Data from vet scan sqlite3 database may be exposed to remote attackers when vet is used as an MCP server in SSE mode with default ports through the sqlite3 query MCP tool.
Patches
v1.12.5is released that patches the issue withHostandOriginheader allow list and validation
Workarounds
- Use
stdio(default) transport for SSE server
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/safedep/vet | all versions | 1.12.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/safedep/vet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/safedep/vet to 1.12.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6q9c-m9fr-865m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6q9c-m9fr-865m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-6q9c-m9fr-865m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6q9c-m9fr-865m in your dependencies?
O3 detects GHSA-6q9c-m9fr-865m across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.