Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
MEDIUM severity

CVE-2019-10806 — vega-util

MEDIUMFix: vega/vega@8f33a0b

CVE-2019-10806 is a medium-severity (CVSS 4.3) CWE-1321 vulnerability in vega-util. 1 public exploit reference exists, so weaponization risk is real. A fix is available for vega-util — see the affected versions and patch details below.

Improperly Controlled Modification of Dynamically-Determined Object Attributes in vega-util

Also known asGHSA-6hwh-rqwf-cxxr
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk
0.00%0.54%1.07%1.61%0.3%1.1%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-10806 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

76other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
vega-utilnpm
1.8Mdownloads / week

Description

vega-util prior to 1.13.1 allows manipulation of object prototype. The 'vega.mergeConfig' method within vega-util could be tricked into adding or modifying properties of the Object.prototype.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmvega-utilall versions1.13.1npm install vega-util@1.13.1

Affected Products

1 product · 1 configurations
Application
vegavega_project
< 1.13.1
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update vega-util to 1.13.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10806 is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

vega-util prior to 1.13.1 allows manipulation of object prototype. The 'vega.mergeConfig' method within vega-util could be tricked into adding or modifying properties of the Object.prototype.
O3 Security · Impact-Aware SCA

Is CVE-2019-10806 in your dependencies?

Find it across npm, including transitive dependencies.

CVE-2019-10806: vega-util — Fixed in 1.13.1