How severe is CVE-2022-46156?

CVE-2022-46156 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

How do I fix CVE-2022-46156?

Update github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent to 0.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-46156 is resolved across your whole dependency graph.

How do I mitigate CVE-2022-46156 if there is no patch (or I can't update yet)?

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.

Is CVE-2022-46156 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-46156 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-46156?

CVE-2022-46156 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-46156?

CVE-2022-46156 is classified as CWE-489 (CWE-489), CWE-749 (CWE-749). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-46156 published, and has it been updated?

CVE-2022-46156 was published on November 30, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2022-46156 — synthetic-monitoring-agent

HIGHFix: grafana/synthetic-monitoring-agent@d8dc7f9

CVE-2022-46156 is a high-severity (CVSS 7.2) CWE-489 vulnerability in github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent. A fix is available for github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent — see the affected versions and patch details below.

Grafana's default installation of `synthetic-monitoring-agent` exposes sensitive information

Also known asGHSA-9j4f-f249-q5w8GO-2022-1132

Published

Nov 30, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

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

2 pkgs affected

🐹github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent🐹github.com/grafana/synthetic-monitoring-agent

Real-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

Impact

Users running the Synthetic Monitoring agent in their local network are impacted. The authentication token used to communicate with the Synthetic Monitoring API is exposed thru a debugging endpoint. This token can be used to retrieve the Synthetic Monitoring checks created by the user and assigned to the agent identified with that token. The Synthetic Monitoring API will reject connections from already-connected agents, so access to the token does not guarantee access to the checks.

Patches

Fixed version is v0.12.0

Users are advised to rotate the agent tokens.

After upgrading to version v0.12.0 or later, it's recommended that user's of distribution packages (e.g. Debian or RedHat and their derivatives) review the configuration stored in /etc/synthetic-monitoring/synthetic-monitoring-agent.conf, specifically the API_TOKEN variable which has been renamed to SM_AGENT_API_TOKEN.

Workarounds

With all previous versions, it's recommended that users review the agent settings and set the HTTP listening address in a manner that limits the exposure, for example, localhost or a non-routed network, by using the command line parameter -listen-address, e.g. -listen-address localhost:4050.

References

The following changes have been made to address this issue:

For more information

If you have any questions or comments about this advisory:

You can use the Synthetic Monitoring Agent discussions.
Issues should be reported in the Synthetic Monitoring Agent issues.
Email us at [email protected].

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent`	all versions	0.12.0`go get github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent@v0.12.0`
🐹Go	`github.com/grafana/synthetic-monitoring-agent`	all versions	0.12.0`go get github.com/grafana/synthetic-monitoring-agent@v0.12.0`

Affected Products

1 product · 1 configurations

Application

synthetic monitoring agentgrafana

< 0.12.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent to 0.12.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-46156 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.

Frequently Asked Questions

### Impact Users running the Synthetic Monitoring agent in their local network are impacted. The authentication token used to communicate with the Synthetic Monitoring API is exposed thru a debugging endpoint. This token can be used to retrieve the Synthetic Monitoring checks created by the user and assigned to the agent identified with that token. The Synthetic Monitoring API will reject connections from already-connected agents, so access to the token does not guarantee access to the checks. ### Patches Fixed version is v0.12.0 Users are advised to rotate the agent tokens. After upgradi