Is io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.18 vulnerable?

Maven · 1 release from 0.18.0 to 0.18.0 · 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.18.0, the last 0.18 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?

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

Advisories affecting io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.18.0

  • 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.18.0
    Fixed in
    No fix released

Which of your client projects are still on io.prometheus.jmx:jmx_prometheus_httpserver_java6 0.18?

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.