CVE-2021-30560

Use after free in Blink XSLT in Google Chrome prior to 91.0.4472.164 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Published: 2021-08-03 Last update: 2025-05-05 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2021-30560 is rated Moderate Risk (43.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.09%). 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-2021-30560

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 2025-11-21 0.99% 0.09% -0.90%
2 2025-11-18 0.07% 0.99% +0.92%
3 2025-03-30 0.07%

Full EPSS history (19 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-30560

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.
2.8 5.9 [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.
2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
8.6 6.4 [email protected]

Weakness enumeration for CVE-2021-30560

GitHub Security Advisory for CVE-2021-30560

GHSA-59gp-qqm7-cw4j · Severity: high · Ecosystem: rubygems — Nokogiri has vulnerable dependencies on libxml2 and libxslt

OS Trackers for CVE-2021-30560

vendor priority summary link
alpine CVE-2021-30560: 3 source package rows (chromium, libxslt, qt5-qtwebengine); 22 state rows across 15 repos (3.12-main, 3.17-community, 3.17-main, 3.18-community, 3.18-main, 3.19-community, 3.19-main, 3.20-community, 3.20-main, 3.21-community, 3.21-main, 3.22-community, 3.22-main, edge-community, edge-main); fixed 22, open 0. https://security.alpinelinux.org/vuln/CVE-2021-30560
debian not yet assigned CVE-2021-30560 not yet assigned priority: Debian including 2 source packages (chromium, libxslt), 10 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 10. https://security-tracker.debian.org/tracker/CVE-2021-30560
gentoo high CVE-2021-30560: 2 GLSA(s) (202107-49, 202310-23), 3 atom(s) (dev-libs/libxslt, www-client/chromium, www-client/google-chrome); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2021-30560
suse high CVE-2021-30560 severity important: SUSE including 321 source package names (0.3.32-3.4:libxslt1-1.1.34-150400.3.3.1, 0.58.0.17.187:libxslt1-1.1.34-150400.3.3.1, …), 740 product×package rows across 355 product lines (Container bci/kiwi, Container containers/apache-tomcat, … (355 product lines)): Fixed 509, Known Affected 231. https://www.suse.com/security/cve/CVE-2021-30560/
ubuntu medium CVE-2021-30560 medium priority: Ubuntu including 2 source packages (chromium-browser, libxslt), 17 status rows across 10 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, trusty, upstream, xenial): released 8, not-affected 6, DNE 2, ignored 1. https://ubuntu.com/security/CVE-2021-30560

Affected software / configurations for CVE-2021-30560

Vendor Product Version Raw CPE
google chrome < 91.0.4472.164 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
xmlsoft libxslt < 1.1.35 cpe:2.3:a:xmlsoft:libxslt:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*
splunk universal_forwarder >= 8.2.0, < 8.2.12 cpe:2.3:a:splunk:universal_forwarder:*:*:*:*:*:*:*:*
splunk universal_forwarder >= 9.0.0, < 9.0.6 cpe:2.3:a:splunk:universal_forwarder:*:*:*:*:*:*:*:*
splunk universal_forwarder 9.1.0 cpe:2.3:a:splunk:universal_forwarder:9.1.0:*:*:*:*:*:*:*

References for CVE-2021-30560

cvelogic Threat Intelligence