CVE-2013-6662

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2022-05-17. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Google Chrome caches TLS sessions before certificate validation occurs.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

April 13, 2017

Last Modified

June 17, 2026

References (2)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:43 UTCEPSS rescore
  2. 2026-08-23 00:13 UTCEPSS rescore
  3. 2026-08-21 23:44 UTCEPSS rescore
  4. 2026-08-20 22:50 UTCEPSS rescore
  5. 2026-08-19 16:59 UTCEPSS rescore
  6. 2026-08-18 13:43 UTCEPSS rescore
  7. 2026-08-16 14:50 UTCEPSS rescore
  8. 2026-08-16 02:09 UTCEPSS rescore
  9. 2026-08-15 01:25 UTCEPSS rescore
  10. 2026-08-09 13:42 UTCEPSS rescore
  11. 2026-08-08 16:31 UTCEPSS rescore
  12. 2026-08-07 16:21 UTCEPSS rescore
  13. 2026-08-06 13:42 UTCEPSS rescore
  14. 2026-08-05 19:12 UTCEPSS rescore
  15. 2026-08-04 15:04 UTCEPSS rescore
  16. 2026-08-01 04:11 UTCEPSS rescore
  17. 2026-07-30 16:23 UTCEPSS rescore
  18. 2026-07-30 01:26 UTCEPSS rescore
  19. 2026-07-28 15:31 UTCEPSS rescore
  20. 2026-07-27 13:03 UTCEG score recompute
  21. 2026-07-27 13:02 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2013-6662?
CVE-2013-6662 is a medium vulnerability published on April 13, 2017. Google Chrome caches TLS sessions before certificate validation occurs.
When was CVE-2013-6662 disclosed?
CVE-2013-6662 was first published in the National Vulnerability Database on April 13, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-6662 actively exploited?
CVE-2013-6662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.7% of all scored CVEs.
What is the CVSS score of CVE-2013-6662?
CVE-2013-6662 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2013-6662?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-6662, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2013-6662

Explore →

Is Your Infrastructure Affected by CVE-2013-6662?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs