Skip to content
Fencer Vulns
medium 5.6

CVE-2021-20066 json

Withdrawn Advisory: Insufficient Granularity of Access Control in JSDom

published 2021-02-16 5 y ago modified 2026-09-10 1 mo ago also GHSA-f4c9-cqv8-9v98 , EUVD-2022-3683

cvss
5.6
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

JSDom improperly allows the loading of local resources, which allows for local files to be manipulated by a malicious web page when script execution is enabled.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-20066 updated cvss 5.6

jsdom: improper loading of local resources

  • Red Hat OpenShift Service Mesh 2.0 servicemesh-grafana, servicemesh-prometheus, servicemesh-grafana-prometheus Red Hat OpenShift Container Platform 4 openshift4/ose-grafana, openshift4/ose-prometheus, openshift4/ose-thanos-rhel8
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Service Mesh 2.0 kiali Red Hat Advanced Cluster Management for Kubernetes 2 search-api
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.39% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • tenable.com https://www.tenable.com/security/research/tra-2021-05 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/jsdom/jsdom/issues/3124#issuecomment-783502951 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • n/a JSDom

References

Sources

Fencer Vulns 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.