EUVD-2026-14819
2026-03-24
mozilla
9.8
CVSS 3.1
Share
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
Lifecycle Timeline
4
Patch Released
Mar 31, 2026 - 21:13 nvd
Patch available
Analysis Generated
Mar 24, 2026 - 12:45 vuln.today
EUVD ID Assigned
Mar 24, 2026 - 12:45 euvd
EUVD-2026-14819
CVE Published
Mar 24, 2026 - 12:30 nvd
CRITICAL 9.8
Description
Use-after-free in the JavaScript Engine component. This vulnerability affects Firefox < 149 and Firefox ESR < 140.9.
Analysis
Mozilla Firefox versions below 149 (and ESR versions below 140.9) contain a use-after-free vulnerability in the JavaScript Engine that enables unauthenticated remote attackers to achieve arbitrary code execution without user interaction. The memory corruption flaw allows complete compromise of affected systems through network-based attacks. …
Sign in for full analysis, threat intelligence, and remediation guidance.
Remediation
Within 24 hours: Identify all affected systems and apply vendor patches immediately. If patching is delayed, consider network segmentation to limit exposure.
Sign in for detailed remediation steps.
Priority Score
49
Low
Medium
High
Critical
KEV: 0
EPSS: +0.0
CVSS: +49
POC: 0
Vendor Status
Debian
firefox
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| sid | vulnerable | 148.0.2-1 | - |
| (unstable) | fixed | (unfixed) | - |
firefox-esr
| Release | Status | Fixed Version | Urgency |
|---|---|---|---|
| bullseye | vulnerable | 115.14.0esr-1~deb11u1 | - |
| bullseye (security) | vulnerable | 140.8.0esr-1~deb11u1 | - |
| bookworm | vulnerable | 128.14.0esr-1~deb12u1 | - |
| bookworm (security) | vulnerable | 140.8.0esr-1~deb12u1 | - |
| trixie (security), trixie | vulnerable | 140.8.0esr-1~deb13u1 | - |
| forky, sid | vulnerable | 140.8.0esr-1 | - |
| (unstable) | fixed | (unfixed) | - |
Share
External POC / Exploit Code
Leaving vuln.today
Destination URL
POC code from unknown sources may be malicious, contain backdoors, or be fake.
Always review and test exploit code in a safe, isolated environment (VM/sandbox).
Verify the source reputation and cross-reference with known databases (Exploit-DB, GitHub Security).