Google CVE-2026-6361

We need to generate a comprehensive JSON analysis for CVE-2026-6361. Use all provided data: description, CVSS, CWE, EPSS, KEV status (not mentioned, so assume no KEV), patch availability, CPE, tags, SSVC, affected versions, references. The CVE is a heap buffer overflow in PDFium in Google Chrome on Windows. CVSS 8.3, vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS 0.01% (low). SSVC: Exploitation none, Automatable yes, Technical Impact partial. Patch available from vendor. CPE: cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*. No KEV mention, so exploitation status: no public exploit identified, but there's a POC? Not mentioned, so none. In summary, actively exploited? No KEV, so "no public exploit identified at time of analysis". But tag says Microsoft, RCE, Heap Overflow, Buffer Overflow, Google. SSVC says automatable yes, but exploitation none. So POC not confirmed.

Fields required: product_name (1-3 words): Google Chrome on Windows? The description says "PDFium in Google Chrome on Windows". So product_name: "Google Chrome on Windows" (3 words). Or "Google Chrome" (2 words). The CPE is just for chrome, so maybe "Google Chrome". I'll go with "Google Chrome" but note Windows platform in summary. product_name: "Google Chrome". That's the main product. Affected version <147.0.7727.101. So Chrome. Good.

summary: Not copy description, original synthesis. Must start with impact verb and product. "Remote code execution in Google Chrome on Windows version prior to 147.0.7727.101 allows a remote attacker to execute arbitrary code inside the sandbox via a crafted PDF file." Add EPSS, KEV. EPSS low, no active exploitation. Mention High severity from Chromium. Be concise, 2-3 sentences.

technical_context: Underlying technology: PDFium is the PDF rendering library in Chromium, used for PDF display. Heap buffer overflow, CWE-122. Affected products from CPE: Google Chrome on Windows (because description says Windows, but CPE doesn't specify OS; possibly Chrome on any platform? Actuall