# libpmi0 17.11.2-1ubuntu0.1~esm3: libpmi0 17.11.2-1ubuntu0.1~esm3 for Ubuntu 18.04.6 LTS (bionic)

libpmi0 17.11.2-1ubuntu0.1~esm3, released January 31, 2019, fixes 3 CVEs in libpmi0. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.

- Web page: https://patchblox.com/security/fix/linux/ubuntu-bionic-libpmi0-17.11.2-1ubuntu0.1-esm3
- Platform: Linux
- Released: Jan 31, 2019
- Priority: Routine (Closes 3 CVEs, none high severity)
- CVEs: 3, exploited: 0, on CISA KEV: 0

## Applies to

| Product | Release | Fixed in |
|---|---|---|
| [libpmi0](https://patchblox.com/security/data/product/linux/libpmi0.md) | Ubuntu 18.04.6 LTS (bionic) | 17.11.2-1ubuntu0.1~esm3 |

## CVEs this fix closes

| CVE | Priority | Title | CVSS | EPSS | Exploitation |
|---|---|---|---:|---:|---|
| [CVE-2019-6438](https://patchblox.com/security/data/cve/CVE-2019-6438.md) | Routine | sview: SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems. | n/a | 0.0233 |  |
| [CVE-2018-7033](https://patchblox.com/security/data/cve/CVE-2018-7033.md) | Routine | libpam-slurm: SchedMD Slurm before 17.02.10 and 17.11.x before 17.11.5 allows SQL Injection attacks against SlurmDBD. | n/a | 0.0188 |  |
| [CVE-2018-10995](https://patchblox.com/security/data/cve/CVE-2018-10995.md) | Routine | slurm-client: SchedMD Slurm before 17.02.11 and 17.1x.x before 17.11.7 mishandles user names (aka user_name fields) and group ids (... | n/a | 0.0168 |  |

---

Data as of 2026-11-12T07:53:35Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.