CVE-2013-6656: Information Disclosure in Chrome Blink XSSAuditor Redirect Handling
- Vendor
CVE-2013-6656 is an information disclosure vulnerability in Blink's XSSAuditor implementation in Google Chrome prior to 33.0.1750.117. The flaw is in the XSSAuditor::init function in core/html/parser/XSSAuditor.cpp when processing POST requests that involve redirection. Instead of correlating the POST body with the redirect target, the auditor incorrectly uses the body of the redirecting page. This request/response mismatch can cause the browser-side XSS filter to make security decisions based on the wrong request context. A remote attacker can abuse this behavior to trigger detectable filter behavior and infer sensitive information, including POST parameter values, through unspecified vectors.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows cross-origin disclosure of sensitive information by abusing browser XSS filter behavior rather than a direct flaw in the target web application. The vulnerability can enable an attacker to infer or recover secret values associated with POST requests, undermining origin boundaries and exposing data that should not be readable by an attacker-controlled site.
Mitigation
If you can’t patch tonight, do this now.
Where immediate patching is not possible, reduce exposure by disabling or avoiding reliance on browser XSS filtering behavior in sensitive workflows, and prefer application-layer defenses such as robust server-side output encoding and Content Security Policy. Limiting cross-origin framing and minimizing exposure of sensitive low-entropy values in contexts that can be reflected into XSS filter matching logic may also reduce exploitability, but these are compensating controls rather than complete fixes.
Remediation
Patch, then assume compromise.
Upgrade Google Chrome to version 33.0.1750.117 or later, where the XSSAuditor redirect-handling issue was fixed. Applying the vendor-provided browser update is the primary remediation.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2013-6656 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2013-6656 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2013-6656?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2013-6656.
- Is there a patch for CVE-2013-6656?
- Upgrade Google Chrome to version 33.0.1750.117 or later, where the XSSAuditor redirect-handling issue was fixed. Applying the vendor-provided browser update is the primary remediation.
- What products are affected by CVE-2013-6656?
- Google Chrome.
- How severe is CVE-2013-6656?
- CVE-2013-6656 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 1.2% (68th percentile) as of Oct 16, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.