Google Chrome before 3.0 does not properly handle XML documents, which allows remote attackers to obtain sensitive information via a crafte…

published 2020-02-06 6y ago modified 2026-06-16 4mo ago also EUVD-2010-3895

cvss: 6.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

Google Chrome before 3.0 does not properly handle XML documents, which allows remote attackers to obtain sensitive information via a crafted web site.

Patch / fix

fixed in 1

google chrome 3.0

Is CVE-2010-3917 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected products

Google Chrome

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

Technology feeds

Google Chrome rss critical rss

References

jvn.jp /en/jp/JVN36765384/index.html
third-party-advisory
jvndb.jvn.jp /en/contents/2010/JVNDB-2010-000056.html
third-party-advisory, vdb-entry

Sources

CVE List CVE-2010-3917
NVD CVE-2010-3917

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