VulnerabilityPublished 10 Nov 2026

CVE-2026-124950: Same-origin Policy Bypass

Source GCVE Database

Compare

Authoritative record:CVE-2026-124950· High

Not known to be exploited.

Data as of 10 Nov 2026, 17:20 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-g2m3-vrpf-c93g

What to do

AI-suggested

This vulnerability has been fixed in Firefox 160. Users and administrators should update to Firefox 160 or later to mitigate this issue. No additional mitigation actions are required beyond applying the official update.

Description

CVE-2026-124950 is a same-origin policy bypass vulnerability in the CSS Parsing and Computation component of Firefox. This security flaw allows bypassing the browser's same-origin policy, which is critical for web security. The issue was addressed and fixed in Firefox version 160. No public exploit or in-the-wild exploitation has been reported. The vulnerability is considered high impact due to the potential security implications of same-origin policy bypasses.

Impact

The impact of this vulnerability is high because bypassing the same-origin policy can allow malicious web content to access or manipulate resources from other origins, potentially leading to data leakage or unauthorized actions within the browser context. However, no active exploitation in the wild has been reported.

Summary

This vulnerability involves a bypass of the same-origin policy within Firefox's CSS Parsing and Computation component. The same-origin policy is a fundamental security mechanism that restricts how documents or scripts loaded from one origin can interact with resources from another origin. Bypassing this policy can lead to unauthorized access to sensitive information or cross-origin interactions that violate security boundaries. Mozilla fixed this issue in Firefox 160 as part of a broader security update addressing multiple high-impact vulnerabilities.

References

Community reviews

Loading reviews…