Default installation of synthetic-monitoring-agent exposes sensitive information

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N · score source

EPSS

• CVE-2022-46156: 0.51% estimated exploitation activity in the next 30 days; percentile 43.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 APITOKEN variable which has been renamed to SMAGENTAPITOKEN. Workarounds With all previous versions, it's recommended that users review the agent settings and set the…

Published by the source

6 Sep 2024, 21:37 UTC

Last modified by the source

18 Nov 2024, 16:27 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9j4f-f249-q5w8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-46156

Advisory: Default installation of `synthetic-monitoring-agent` exposes sensitive information
IDs: CVE-2022-46156, GHSA-9j4f-f249-q5w8
Record: https://patchnext.com/advisories/cve-2022-46156 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent 0.12.0; github.com/grafana/synthetic-monitoring-agent 0.12.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent: affected < 0.12.0; fixed in 0.12.0
- Go github.com/grafana/synthetic-monitoring-agent: affected < 0.12.0; fixed in 0.12.0

## Suggested inspection (read-only)
- Go github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent: check the installed version with your package manager.
- Go github.com/grafana/synthetic-monitoring-agent: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent, github.com/grafana/synthetic-monitoring-agent.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9j4f-f249-q5w8 (GitHub-reviewed advisory GHSA-9j4f-f249-q5w8 lists affected ranges: Go github.com/grafana/synthetic-monitoring-agent/cmd/synthetic-monitoring-agent >=0 =0 <0.12.0)

Commands are suggestions: review each one before running it.