How severe is CVE-2017-5022?

CVE-2017-5022 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity low, and availability none.

Is CVE-2017-5022 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (65th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-5022?

CVE-2017-5022 affects Google Chrome. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2017-5022?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2017-5022 published?

CVE-2017-5022 was published on 2017-02-17 and last updated on 2026-06-17.

CVE-2017-5022

CVE-2017-5022 is a medium-severity vulnerability in Google Chrome with a CVSS 3.x base score of 4.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 4.3)
CVSS v2: 4.3
EPSS exploit prediction: 1% (65th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Google Chrome
Published: 2017-02-17
Last modified: 2026-06-17

Description

Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to properly enforce unsafe-inline content security policy, which allowed a remote attacker to bypass content security policy via a crafted HTML page.

Frequently asked questions

What is CVE-2017-5022?: Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to properly enforce unsafe-inline content security policy, which allowed a remote attacker to bypass content security policy via a crafted HTML page.
How severe is CVE-2017-5022?: CVE-2017-5022 has a CVSS 3.x base score of 4.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2017-5022 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (65th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-5022?: CVE-2017-5022 affects Google Chrome. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2017-5022?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-5022 published?: CVE-2017-5022 was published on 2017-02-17 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

More vulnerabilities in Google Chrome

CVE-2026-13782 — Critical (CVSS 10.0): Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the…
CVE-2015-8548 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google V8 before 4.7.80.23, as used in Google Chrome before 47.0.2526.80, allow…
CVE-2015-6791 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome before 47.0.2526.80 allow attackers to cause a denial of service…
CVE-2015-6788 — Critical (CVSS 10.0): The ObjectBackedNativeHandler class in extensions/renderer/object_backed_native_handler.cc in the extensions subsystem…
CVE-2015-8480 — Critical (CVSS 10.0): The VideoFramePool::PoolImpl::CreateFrame function in media/base/video_frame_pool.cc in Google Chrome before…
CVE-2015-6787 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome before 47.0.2526.73 allow attackers to cause a denial of service…

All CVEs affecting Google Chrome →