GHSA-9jjc-grg5-67gj is a critical-severity (CVSS 9.1) SQL Injection vulnerability in github.com/layer5io/meshery. A fix is available for github.com/layer5io/meshery — see the affected versions and patch details below.
SQL injection vulnerability in Meshery
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.
How urgent is this, really
GHSA-9jjc-grg5-67gj plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/layer5io/mesheryReal-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
A SQL injection vulnerability exists in Meshery prior to version v0.6.179, enabling a remote attacker to retrieve sensitive information and execute arbitrary code through the “order” parameter
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/layer5io/meshery | all versions | 0.6.179go get github.com/layer5io/meshery@v0.6.179 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/layer5io/meshery, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/layer5io/meshery to 0.6.179 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jjc-grg5-67gj 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9jjc-grg5-67gj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9jjc-grg5-67gj. 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-9jjc-grg5-67gj in your dependencies?
O3 Security finds GHSA-9jjc-grg5-67gj across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.