Is io.prometheus.jmx:jmx_prometheus_httpserver 0.17 vulnerable?

Maven · 3 releases from 0.17.0 to 0.17.2 · latest io.prometheus.jmx:jmx_prometheus_httpserver is 1.0.1 · checked 18 Nov 2026

No known advisories in the last release

io.prometheus.jmx:jmx_prometheus_httpserver 0.17.2, the last 0.17 release, has no known advisories. 1 advisory affects earlier 0.17.x releases, so update to 0.17.2.

Update within 0.17:mvn versions:use-dep-version -Dincludes=io.prometheus.jmx:jmx_prometheus_httpserver -DdepVersion=0.17.2 -DforceVersion=true

Is your project on an affected io.prometheus.jmx:jmx_prometheus_httpserver?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 0.17.x, affecting earlier releases

  • MediumCVE-2022-38749GHSA-c4r9-r8fh-9vj26 Sept 2022

    snakeYAML before 1.31 vulnerable to Denial of Service due to Out-of-bounds Write

    Affected
    0.17.0
    Fixed in
    No fix released

Every io.prometheus.jmx:jmx_prometheus_httpserver 0.17.x release

Affected: 0.17.0. 0.17.1 and later are not affected. Latest io.prometheus.jmx:jmx_prometheus_httpserver: 1.0.1.

VersionKnown advisories
io.prometheus.jmx:jmx_prometheus_httpserver 0.17.2None
io.prometheus.jmx:jmx_prometheus_httpserver 0.17.1None
io.prometheus.jmx:jmx_prometheus_httpserver 0.17.0CVE-2022-38749

Which of your client projects are still on io.prometheus.jmx:jmx_prometheus_httpserver 0.17?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact io.prometheus.jmx:jmx_prometheus_httpserver 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 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.