Hex authenticity of signed packages not validated

published 2019-02-04 7y ago modified 2026-06-17 4mo ago also GHSA-q3cc-rr2c-87r6 , EUVD-2022-4868

cvss: 8.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits: 0; none known

Hex package manager hex_core version 0.3.0 and earlier contains a Signing oracle vulnerability in Package registry verification that can result in Package modifications not detected, allowing code execution. This attack appears to be exploitable via victim fetches packages from malicious/compromised mirror. This vulnerability appears to have been fixed in 0.4.0.

Patch / fix

fixed in 1 links 2

hex hex_core 0.4.0

github.com/hexpm/hex_core#51 pull request
github.com/hexpm/hex_core#48 pull request

Is CVE-2019-1000013 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

Exploit prediction

0.88% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD	2.0	6.8	AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
hex	hex_core	<0.4.0	0.4.0

Classification

Weakness

CWE-345 Insufficient Verification of Data Authenticity

References

github.com /hexpm/hex_core/pull/51
web, patch, third-party-advisory
github.com /hexpm/hex_core/pull/48
web, patch, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2019-1000013
advisory
github.com /hexpm/hex_core
package

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.