How severe is CVE-2012-2821?

CVE-2012-2821 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2012-2821 being actively exploited?

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

What products are affected by CVE-2012-2821?

CVE-2012-2821 primarily affects Google Chrome. In total, 43 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2012-2821?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2012-2821 published?

CVE-2012-2821 was published on 2012-06-27 and last updated on 2026-06-16.

CVE-2012-2821

CVE-2012-2821 is a high-severity vulnerability in Google Chrome with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 1% (53rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Google Chrome
Published: 2012-06-27
Last modified: 2026-06-16

Description

The autofill implementation in Google Chrome before 20.0.1132.43 does not properly display text, which has unspecified impact and remote attack vectors.

Frequently asked questions

What is CVE-2012-2821?: The autofill implementation in Google Chrome before 20.0.1132.43 does not properly display text, which has unspecified impact and remote attack vectors.
How severe is CVE-2012-2821?: CVE-2012-2821 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2012-2821 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2012-2821?: CVE-2012-2821 primarily affects Google Chrome. In total, 43 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2012-2821?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2012-2821 published?: CVE-2012-2821 was published on 2012-06-27 and last updated on 2026-06-16.

References

Affected products (43)

cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.0:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.1:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.2:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.3:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.4:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.5:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.6:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.7:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.8:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.9:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.10:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.11:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.12:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.13:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.14:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.15:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.16:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.17:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.18:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.19:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.20:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.21:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.22:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.23:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.24:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.25:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.26:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.27:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.28:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.29:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.30:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.31:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.32:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.33:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.34:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.35:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.36:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.37:*:*:*:*:*:*:*
cpe:2.3:a:google:chrome:20.0.1132.38:*:*:*:*:*:*:*

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 →