Is io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.17 vulnerable?
Maven · 3 releases from 0.17.0 to 0.17.2 · latest io.prometheus.jmx:jmx_prometheus_httpserver_java6 is 0.18.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.17.2, the last 0.17 release, is affected by 1 known security advisory (1 medium), including CVE-2022-38749. At least one has no fixed release yet.
Is your project on an affected io.prometheus.jmx:jmx_prometheus_httpserver_java6?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.17.2
snakeYAML before 1.31 vulnerable to Denial of Service due to Out-of-bounds Write
- Affected
- <=0.18.0
- Fixed in
- No fix released
Every io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.17.x release
Affected: 0.17.0 to 0.17.2. Latest io.prometheus.jmx:jmx_prometheus_httpserver_java6: 0.18.0.
| Version | Known advisories |
|---|---|
| io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.17.2 | CVE-2022-38749 |
| io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.17.1 | CVE-2022-38749 |
| io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.17.0 | CVE-2022-38749 |
Which of your client projects are still on io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.17?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact io.prometheus.jmx:jmx_prometheus_httpserver_java6 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other io.prometheus.jmx:jmx_prometheus_httpserver_java6 versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.