What is GHSA-PGCR-7WM4-MCV6?

GHSA-PGCR-7WM4-MCV6 is a critical-severity security vulnerability in pem (npm), affecting versions < 1.13.2. It is fixed in 1.13.2.

How severe is GHSA-PGCR-7WM4-MCV6?

GHSA-PGCR-7WM4-MCV6 has a CVSS score of 7.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of pem are affected by GHSA-PGCR-7WM4-MCV6?

pem (npm) versions < 1.13.2 is affected.

Is there a fix for GHSA-PGCR-7WM4-MCV6?

Yes. GHSA-PGCR-7WM4-MCV6 is fixed in 1.13.2. Upgrade to this version or later.

Is GHSA-PGCR-7WM4-MCV6 exploitable, and should I be worried?

Whether GHSA-PGCR-7WM4-MCV6 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-PGCR-7WM4-MCV6 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-PGCR-7WM4-MCV6?

Upgrade pem to 1.13.2 or later.

GHSA-PGCR-7WM4-MCV6 in pem

Q: How severe is GHSA-PGCR-7WM4-MCV6?

GHSA-PGCR-7WM4-MCV6 has a CVSS score of 7.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of pem are affected by GHSA-PGCR-7WM4-MCV6?

pem (npm) versions < 1.13.2 is affected.

Q: Is there a fix for GHSA-PGCR-7WM4-MCV6?

Yes. GHSA-PGCR-7WM4-MCV6 is fixed in 1.13.2. Upgrade to this version or later.

Q: Is GHSA-PGCR-7WM4-MCV6 exploitable, and should I be worried?

Whether GHSA-PGCR-7WM4-MCV6 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-PGCR-7WM4-MCV6 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-PGCR-7WM4-MCV6?

Upgrade pem to 1.13.2 or later.

Summary

Sensitive Data Exposure in pem

Versions of pem before 1.13.2 expose sensitive data when the readPkcs12 is used.

The readPkcs12 function reads the certificate and key data from a pkcs12 file using the encryption password. As part of this process it creates a globally readable file with a filename of 20 random 0-f characters in the temporary directory containing the password which is then read by OpenSSL. The file containing the password is never cleaned up after it is used giving access to the pkcs12 password to any other users with access to read files from the system.

Impact

GHSA-PGCR-7WM4-MCV6 has a CVSS score of 7.5 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.13.2); upgrading removes the vulnerable code path.

Affected versions

pem (< 1.13.2)

Security releases

pem → 1.13.2 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Update to version 1.13.2 or later.

Frequently Asked Questions

What is GHSA-PGCR-7WM4-MCV6? GHSA-PGCR-7WM4-MCV6 is a critical-severity security vulnerability in pem (npm), affecting versions < 1.13.2. It is fixed in 1.13.2.
How severe is GHSA-PGCR-7WM4-MCV6? GHSA-PGCR-7WM4-MCV6 has a CVSS score of 7.5 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of pem are affected by GHSA-PGCR-7WM4-MCV6? pem (npm) versions < 1.13.2 is affected.
Is there a fix for GHSA-PGCR-7WM4-MCV6? Yes. GHSA-PGCR-7WM4-MCV6 is fixed in 1.13.2. Upgrade to this version or later.
Is GHSA-PGCR-7WM4-MCV6 exploitable, and should I be worried? Whether GHSA-PGCR-7WM4-MCV6 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-PGCR-7WM4-MCV6 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-PGCR-7WM4-MCV6? Upgrade pem to 1.13.2 or later.