How severe is GHSA-q3cc-rr2c-87r6?

GHSA-q3cc-rr2c-87r6 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q3cc-rr2c-87r6?

GHSA-q3cc-rr2c-87r6 affects the following packages: hex_core (Hex). Ecosystems affected: Hex.

How do I fix GHSA-q3cc-rr2c-87r6?

Update hex_core to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3cc-rr2c-87r6 is resolved across your whole dependency graph.

How do I detect GHSA-q3cc-rr2c-87r6 in my Hex dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hex_core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q3cc-rr2c-87r6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-q3cc-rr2c-87r6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q3cc-rr2c-87r6 can be triaged on real exposure rather than presence alone.

Is GHSA-q3cc-rr2c-87r6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q3cc-rr2c-87r6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q3cc-rr2c-87r6?

GHSA-q3cc-rr2c-87r6 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-q3cc-rr2c-87r6 published, and has it been updated?

GHSA-q3cc-rr2c-87r6 was published on May 13, 2022 and was last updated on December 10, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💧

💧 Hex

Not in CISA KEV

HIGH severity

GHSA-q3cc-rr2c-87r6 — hex_core

HIGHFix: hexpm/hex_core#48

GHSA-q3cc-rr2c-87r6 is a high-severity (CVSS 8.8) remote code execution vulnerability in hex_core. A fix is available for hex_core — see the affected versions and patch details below.

Hex authenticity of signed packages not validated

Also known asCVE-2019-1000013

Published

May 13, 2022

Updated

Dec 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-q3cc-rr2c-87r6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected

💧hex_core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Hex packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💧Hex	`hex_core`	all versions	0.4.0`mix deps.update hex_core`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hex_core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hex_core to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3cc-rr2c-87r6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q3cc-rr2c-87r6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-q3cc-rr2c-87r6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-q3cc-rr2c-87r6 in your dependencies?

O3 Security finds GHSA-q3cc-rr2c-87r6 across Hex dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works