EUVD-2026-14831
2026-03-24
mozilla
7.5
CVSS 3.1
Share
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
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-14831
CVE Published
Mar 24, 2026 - 12:30 nvd
HIGH 7.5
Description
Incorrect boundary conditions in the Graphics component. This vulnerability affects Firefox < 149 and Firefox ESR < 140.9.
Analysis
A boundary condition error in Firefox's Graphics component allows information disclosure through improper memory access validation. This vulnerability affects Firefox versions below 149 and Firefox ESR versions below 140.9, enabling attackers to read sensitive memory contents from the graphics processing context. …
Sign in for full analysis, threat intelligence, and remediation guidance.
Remediation
Within 7 days: Identify all affected systems and apply vendor patches promptly. Monitor vendor channels for patch availability.
Sign in for detailed remediation steps.
Priority Score
38
Low
Medium
High
Critical
KEV: 0
EPSS: +0.0
CVSS: +38
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).