An unauthorized user with key vault write access may cause an authorized client to issue arbitrary authenticated Google Cloud KMS API calls under the authorized user's identity, escalating database-level access into cloud key control and defeating client-side encryption.
CVE-2026-84962
This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.2
- EG Score
- 4.2(medium)
- EG Risk
- 19(Track)EG Risk 19/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity42% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
September 3, 2026
Last Modified
September 17, 2026
Advisory Details (1)
Auto-updated Sep 3, 2026Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libmongocrypt | 1.10.0-1 ... 1.9.1-1 (23 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libmongocrypt | 1.13.2-1 ... 1.20.4-1 (13 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libmongocrypt | 1.13.2-1 ... 1.20.1-1 (10 versions) | 1.20.2-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 25× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 12:37 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 13:20 UTCEG score recompute
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 18:35 UTCEG score recompute
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 19:14 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-13 20:39 UTCEG score recompute
- 2026-09-12 21:22 UTCEG score recompute
- 2026-09-11 22:05 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-10 22:45 UTCEG score recompute
- 2026-09-08 23:08 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-06 14:28 UTCEG score recompute
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-04 15:50 UTCEG score recompute
- 2026-09-03 16:33 UTCEG score recompute
- 2026-09-03 15:46 UTCEG score recompute
- 2026-09-03 15:24 UTCEG score recompute
- 2026-09-03 15:23 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-84962?
When was CVE-2026-84962 disclosed?
Is CVE-2026-84962 actively exploited?
What is the CVSS score of CVE-2026-84962?
How do I remediate CVE-2026-84962?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84962
Is Your Infrastructure Affected by CVE-2026-84962?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.