CVE-2009-2071

What it is

Google Chrome before 1.0.154.53 displays a cached certificate for a (1) 4xx or (2) 5xx CONNECT response page returned by a proxy server, which allows man-in-the-middle attackers to spoof an arbitrary https site by letting a browser obtain a valid certificate from this site during one request, and then sending the browser a crafted 502 response page upon a subsequent request.

At a glance

Exploitability

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

Exploit odds

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

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2009-06-15 19:30 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:08 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.0% in the next 30 days (EPSS).
• Severity: 6.8 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2009-06-15 19:30 UTC

Last modified

2026-06-16 23:08 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-287 · Improper authentication

Record status

Modified

Affected

• Google Chrome ≤ 1.0.154.52
• Google Chrome 0.2.149.29
• Google Chrome 0.2.149.30
• Google Chrome 0.2.152.1
• Google Chrome 0.2.153.1
• Google Chrome 0.3.154.0
• Google Chrome 0.3.154.3
• Google Chrome 0.4.154.18

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-2009-2071.md and follow it. Check whether this project is affected by CVE-2009-2071. 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