Home
» Security vulnerabilities
» CVE-2020-7768
The package grpc before 1.24.4; the package @grpc/grpc-js before 1.1.8 are vulnerable to Prototype Pollution via loadPackageDefinition.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2020-7768
Conclusion & alert: CVE-2020-7768 is rated Moderate Risk (58/100) : CVSS High severity, with medium exploitation likelihood (EPSS 1.32%).Mandatory action: Review affected assets and schedule remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2020-7768
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-02-01
1.14%
1.32%
+0.18%
2
2025-12-20
1.84%
1.14%
-0.69%
3
2025-11-21
—
1.84%
—
Full EPSS history
(15 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2020-7768
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
7.5
3.1
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9
3.6
[email protected]
9.8
3.1
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9
5.9
[email protected]
5.0
2.0
MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P
Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
10.0
2.9
[email protected]
Weakness enumeration for CVE-2020-7768
GitHub Security Advisory for CVE-2020-7768
GHSA-pp75-xfpw-37g9 · Severity: high · Ecosystem: npm
— Prototype pollution in grpc and @grpc/grpc-js
OS Trackers for CVE-2020-7768
Affected software / configurations for CVE-2020-7768
Vendor
Product
Version
Raw CPE
grpc
grpc
< 1.1.8
cpe:2.3:a:grpc:grpc:*:*:*:*:*:node.js:*:*
grpc
grpc
< 1.24.2
cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*
References for CVE-2020-7768
cvelogic
Threat Intelligence