CVE-2013-6166

What it is

Google Chrome before 29 sends HTTP Cookie headers without first validating that they have the required character-set restrictions, which allows remote attackers to conduct the equivalent of a persistent Logout CSRF attack via a crafted parameter that forces a web application to set a malformed cookie within an HTTP response.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

1.9% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2014-02-15 14:57 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:00 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.9% in the next 30 days (EPSS).
• Severity: 6.8 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2014-02-15 14:57 UTC

Last modified

2026-06-17 00:00 UTC

Exploit probability

1.9% · EPSS, next 30 days

Weakness

CWE-352 · Cross-site request forgery

Record status

Modified

Affected

• Google Chrome ≤ 28.0.1500.95

Attack profile CVSS 2.0 · 6.8

Attack vector

Network

Complexity

Medium

Authentication

None

Confidentiality

Partial

Integrity

Partial

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2013-6166.md and follow it. Check whether this project is affected by CVE-2013-6166. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge