GHSA-4V48-4Q5M-8VX4

Workarounds

There is no workaround but attacker must have access to the hashed password, stored in disk, to bypass the authentication.

Credit

We want to thank Lei Wan for reporting this security issue.

Prometheus 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.

GHSA-4V48-4Q5M-8VX4 has a CVSS score of 7.2 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.37.4, 2.40.4); upgrading removes the vulnerable code path.

Kodem intelligence

Prometheus 2.37.4 (LTS) and 2.40.4 have been released to address this issue.

1. What is GHSA-4V48-4Q5M-8VX4? GHSA-4V48-4Q5M-8VX4 is a high-severity security vulnerability in github.com/prometheus/prometheus (go), affecting versions >= 2.24.1, < 2.37.4. It is fixed in 2.37.4, 2.40.4.
2. How severe is GHSA-4V48-4Q5M-8VX4? GHSA-4V48-4Q5M-8VX4 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by GHSA-4V48-4Q5M-8VX4?
   • github.com/prometheus/prometheus (go) (versions >= 2.24.1, < 2.37.4)
   • github.com/prometheus/prometheus/v2 (go) (versions >= 2.24.1, < 2.37.4)
4. Is there a fix for GHSA-4V48-4Q5M-8VX4? Yes. GHSA-4V48-4Q5M-8VX4 is fixed in 2.37.4, 2.40.4. Upgrade to this version or later.
5. Is GHSA-4V48-4Q5M-8VX4 exploitable, and should I be worried? Whether GHSA-4V48-4Q5M-8VX4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-4V48-4Q5M-8VX4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-4V48-4Q5M-8VX4?
   • Upgrade github.com/prometheus/prometheus to 2.37.4 or later
   • Upgrade github.com/prometheus/prometheus to 2.40.4 or later
   • Upgrade github.com/prometheus/prometheus/v2 to 2.37.4 or later
   • Upgrade github.com/prometheus/prometheus/v2 to 2.40.4 or later