GCVE - cpe:2.3:a:sharp_project:sharp:*:*:*:*:*:node.js:*:*

Approved changes feed: RSS · Atom

cpe:2.3:a:sharp_project:sharp:*:*:*:*:*:node.js:*:*

part: a version: * update: *

Vendor	Sharp Project (`f49c48e3-29c5-5e07-b6d2-6ba4e5be3ba4`)
Product	Sharp (`383613bb-8eba-5970-94da-7f31750567d3`)
Edition	*
Language	*
Software edition	*
Target software	node.js
Target hardware	*
Other	*

Notes

Imported from purl2cpe mapping

PURL	Source	Last updated
`pkg:github/lovell/sharp`	purl2cpe	2026-06-01 10:14:50.194272
`pkg:maven/org.webjars.npm/sharp`	purl2cpe	2026-06-01 10:14:50.194274
`pkg:npm/sharp`	purl2cpe	2026-06-01 10:14:50.194275
`pkg:sourceforge/sharp.mirror`	purl2cpe	2026-06-01 10:14:50.194277

Identifier	cpeApplicability	Submitted	db.gcve.eu details	Rationale
`CVE:CVE-2022-29256`	vulnerable	2026-06-08 05:42:47.445653	Possible vulnerability at 'npm install' time in sharp if an attacker has control over build environment MEDIUM (6.5) sharp is an application for Node.js image processing. Prior to version 0.30.5, there is a possible vulnerability in logic that is run only at `npm install` time when installing versions of `sharp` prior to the latest v0.30.5. If an attacker has the ability to set the value of the `PKG_CONFIG_PATH` environment variable in a build environment then they might be able to use this to inject an arbitrary command at `npm install` time. This is not part of any runtime code, does not affect Windows users at all, and is unlikely to affect anyone that already cares about the security of their build environment. This problem is fixed in version 0.30.5. Published: 2022-05-25T21:20:12.000Z Updated: 2025-04-23T18:21:26.238Z Open on db.gcve.eu Reference links https://github.com/lovell/sharp/security/advisories/GHSA-gp95-ppv5-3jc5 https://github.com/lovell/sharp/commit/a6aeef612be50f5868a77481848b1de674216f0c	Imported from gcve-enriched-dumps CVE data

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.