Grafana Alloy on Windows has Unquoted Search Path or Element vulnerabilityGHSA-chqx-36rm-rf8h
HIGHFix: grafana/alloy@88e7798GHSA-chqx-36rm-rf8h is a high-severity (CVSS 7.3) CWE-428 vulnerability in github.com/grafana/alloy. A fix is available for github.com/grafana/alloy — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-chqx-36rm-rf8h.
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/grafana/alloy🐹github.com/grafana/alloyReal-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
Unquoted Search Path or Element vulnerability in Grafana Alloy on Windows allows Privilege Escalation from Local User to SYSTEM. This issue affects Alloy: before 1.3.4, from 1.4.0-rc.0 and prior to 1.4.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/grafana/alloy | all versions | 1.3.4go get github.com/grafana/alloy@v1.3.4 |
| 🐹Go | github.com/grafana/alloy | ≥ 1.4.0-rc.0&&< 1.4.1 | 1.4.1go get github.com/grafana/alloy@v1.4.1 |
Affected Products
alloygrafanaDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/alloy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/alloy to 1.3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chqx-36rm-rf8h is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-chqx-36rm-rf8h in your dependencies?
Find it across Go, including transitive dependencies.