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.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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 |
Affected Products
mesherylayer5Detection & 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
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is GHSA-9jjc-grg5-67gj in your dependencies?
Find it across Go, including transitive dependencies.