Skip to content
Fencer Intel
medium —

GHSA-w8f5-6m3h-r453 json

Standalone pnpm executables embed Node versions that still trust the compromised eMudhra intermediates

published 15d ago modified 15d ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository pnpm/pnpm. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of pnpm/pnpm for @pnpm/exe: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Patch / fix

  • npm @pnpm/exe >=10.34.8 <11.0.0, >=11.28.8 <12.0.0

Is GHSA-w8f5-6m3h-r453 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm @pnpm/exe
<10.34.8
>=11.0.0 <11.28.8
>=10.34.8 <11.0.0
>=11.28.8 <12.0.0

Classification

Weakness
  • CWE-295 Improper Certificate Validation
  • CWE-1395 Dependency on Vulnerable Third-Party Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of pnpm/pnpm published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.