VulnSocial

CVE-2026-6313Disclosure(apple / chrome)

LOWCVSS 3.1 · LOW

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch apple chrome systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

Insufficient policy enforcement in CORS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)

apple CVEsBack to dashboard
1.5/ 10 priority

Sources & remediation

Vendor / third-party advisories
Other references
Weakness type (CWE)
CWE-284

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • chrome
  • linux_kernel
  • macos
  • windows

Threat summary

  • Patch or workaround signal is available
  • 3 mentions across 2 observed days
  • Momentum state: stable

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 3 signals
  • Disclosure: 1 classified signal
  • General: 1 classified signal
  • Peaked 1d ago at 2 mentions (2026-04-16); latest day: 1
  • 3 total mentions across 2 days

Affected systems

Vendors
applegooglelinuxmicrosoft
Products
chromelinux_kernelmacoswindows

1 version affected across 4 products

Deep dive

Activity timeline3 mentions / 2d
01122Mentions · 2026-04-16: 2Mentions · 2026-04-17: 1Patch / Workaround · 2026-04-17: 1Technical Details · 2026-04-16: 2Technical Details · 2026-04-17: 104-1604-17
Signal classification3 categories
Disclosure
133.3%
General
133.3%
Patch
133.3%
Referenced assets3 URLs
Classification over time
DateTotalLabels
2026-04-162
Disclosure1General1
2026-04-171
Patch1
Full discourse3 posts
  • WindowsForum@windowsforum
    Patch

    🪟 CVE-2026-6313 is the perfect “small CORS mistake, big trust meltdown” story. Edge fix arriving after Chrome… because of course Windows needs the patch after the browser déjà vu. https://windowsforum.com/threads/cve-2026-6313-cors-policy-bug-chrome-147-0-7727-101-fix-for-edge.413803/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #MicrosoftEdge #ChromeUpdate #ChromiumSecurity #CorsVulnerability https://t.co/RjexPupx3V

    Post summary

    CVE‑2026‑6313 is a CORS policy bug in Edge, with a patch forthcoming after Chrome’s fix.

    0000043
    1.1K followersView on X
  • CVE@CVEnew
    General

    CVE-2026-6313 Insufficient policy enforcement in CORS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to leak cross-origin… https://www.cve.org/CVERecord?id=CVE-2026-6313

    Post summary

    This entry references CVE-2026-6313, describing a CORS policy enforcement flaw in Google Chrome that could let a remote attacker, once the renderer process is compromised, leak cross‑origin data. No PoC, exploit, active usage, or patch information is provided.

    00000122
    57.2K followersView on X
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-6313 Insufficient CORS Policy Enforcement in Google Chrome Prior to 147.0.7727.101 https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-6313

    Post summary

    The post references CVE-2026-6313, highlighting insufficient CORS enforcement in older Chrome builds, but offers no PoC, exploit, or patch information.

    0000043
    4.0K followersView on X
CPE platform detail4 entries

4 of 4 entries

PartVendorProductVersionTarget SWTarget HW
OSapplemacos---
Appgooglechrome---
OSlinuxlinux_kernel---
OSmicrosoftwindows---

Explore more

Back to dashboardapple CVEsgoogle CVEslinux CVEschrome vulnerabilities