github.com/prometheus/prometheus vulnerabilities
- Registry
- Go
- Latest
- 0.316.0
9 known advisories
The latest version, 0.316.0, is not affected by any of them. Projects on older versions may be.
go get github.com/prometheus/prometheus@v0.316.0Is your project on an affected github.com/prometheus/prometheus?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/prometheus/prometheus
Prometheus has Stored XSS via metric names and label values in Prometheus web UI in github.com/prometheus/prometheus
- Affected
- <0.311.2-0.20260410083055-07c6232d159b
- Fixed in
- 0.311.2-0.20260410083055-07c6232d159b
Prometheus Azure AD remote write OAuth client secret exposed via config API in github.com/prometheus/prometheus
- Affected
- >=0.45.2 <0.311.3
- Fixed in
- 0.311.3
Prometheus vulnerable to stored XSS via crafted histogram bucket label values in the old web UI heatmap display in github.com/prometheus/prometheus
- Affected
- <0.311.3
- Fixed in
- 0.311.3
Prometheus: Remote read endpoint allows denial of service via crafted snappy payload in github.com/prometheus/prometheus
- Affected
- <0.305.2 · >=0.306.0 <0.311.3 · >=1.0.0-rc.0
- Fixed in
- 0.305.2, 0.311.3
Prometheus vulnerable to stored XSS via crafted histogram bucket label values in the old web UI heatmap display
- Affected
- <0.311.3
- Fixed in
- 0.311.3
Prometheus: Remote read endpoint allows denial of service via crafted snappy payload
- Affected
- >=0.306.0 <0.311.3 · <0.305.2 · >=1.0.0-rc.0 <=2.5.0
- Fixed in
- 0.305.2, 0.311.3
Prometheus Azure AD remote write OAuth client secret exposed via config API
- Affected
- >=0.45.2 <0.311.3
- Fixed in
- 0.311.3
Prometheus has Stored XSS via metric names and label values in Prometheus web UI tooltips and metrics explorer
- Affected
- >=3.0.0 <3.5.2 · >=3.6.0 <3.11.2 · <0.311.2-0.20260410083055-07c6232d159b
- Fixed in
- 0.311.2-0.20260410083055-07c6232d159b, 3.5.2, 3.11.2
Prometheus vulnerable to basic authentication bypass
- Affected
- >=2.24.1 <2.37.4 · >=2.38.0 <2.40.4
- Fixed in
- 2.37.4, 2.40.4
Is your github.com/prometheus/prometheus version vulnerable?
- github.com/prometheus/prometheus 2.52 advisories in 2.5.0
- github.com/prometheus/prometheus 2.42 advisories in 2.4.3
- github.com/prometheus/prometheus 2.32 advisories in 2.3.2
- github.com/prometheus/prometheus 2.22 advisories in 2.2.1
- github.com/prometheus/prometheus 2.12 advisories in 2.1.0
- github.com/prometheus/prometheus 2.02 advisories in 2.0.0
- github.com/prometheus/prometheus 1.992 advisories in 1.99.0
- github.com/prometheus/prometheus 1.82 advisories in 1.8.2
- github.com/prometheus/prometheus 1.72 advisories in 1.7.2
- github.com/prometheus/prometheus 1.62 advisories in 1.6.3
- github.com/prometheus/prometheus 1.52 advisories in 1.5.3
- github.com/prometheus/prometheus 1.42 advisories in 1.4.1
- github.com/prometheus/prometheus 0.316No known advisories in 0.316.0
- github.com/prometheus/prometheus 0.315No known advisories in 0.315.1
- github.com/prometheus/prometheus 0.314No known advisories in 0.314.0
- github.com/prometheus/prometheus 0.313No known advisories in 0.313.5
- github.com/prometheus/prometheus 0.312No known advisories in 0.312.0
- github.com/prometheus/prometheus 0.311No known advisories in 0.311.3
Which of your client projects still run an old github.com/prometheus/prometheus?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.