Prometheus Exporter-Toolkit is vulnerable to authentication bypass

Exploitation

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

CVSS

6.2 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2022-46146: 1.26% estimated exploitation activity in the next 30 days; percentile 69.69 (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 Prometheus and its exporters can be secured by a web.yml file that specifies usernames and hashed passwords for basic authentication. Passwords are hashed with bcrypt, which means that even if you have access to the hash, it is very hard to find the original password back. However, a flaw in the way this mechanism was implemented in the exporter toolkit makes it possible with people who know the hashed password to authenticate against Prometheus. A request can be forged by an attacker to poison the internal cache used to cache the computation of hashes and make subsequent requests successful. This cache is used in both happy and unhappy scenarios in order to limit side channel attacks that could tell an attacker if a user is present in the file or not. Patches The exporter-toolkit v0.7.3 and v0.8.2 have been released to address this issue. Workarounds There is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication.…

Published by the source

2 Dec 2022, 22:25 UTC

Last modified by the source

23 Jan 2024, 19:36 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7rg2-cxvp-9p7p

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

# Patch Next advisory brief: CVE-2022-46146

Advisory: Prometheus Exporter-Toolkit is vulnerable to authentication bypass
IDs: CVE-2022-46146, GHSA-7rg2-cxvp-9p7p
Record: https://patchnext.com/advisories/cve-2022-46146 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/prometheus/exporter-toolkit 0.8.2, 0.7.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/prometheus/exporter-toolkit: affected >= 0.8.0, < 0.8.2; < 0.7.2; fixed in 0.8.2, 0.7.2

## Suggested inspection (read-only)
- Go github.com/prometheus/exporter-toolkit: 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/prometheus/exporter-toolkit.
- 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-7rg2-cxvp-9p7p (GitHub-reviewed advisory GHSA-7rg2-cxvp-9p7p lists affected ranges: Go github.com/prometheus/exporter-toolkit >=0.8.0 =0 <0.7.2)

Commands are suggestions: review each one before running it.