CVE-2025-3608 | Race condition in nsHttpTransaction could lead to memory corruption

A race condition existed in nsHttpTransaction that could have been exploited to cause memory corruption, potentially leading to an exploitable condition. This vulnerability was fixed in Firefox 137.0.2.

Published: 2025-04-15 Last update: 2026-04-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-3608 is rated Moderate Risk (40.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.18%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-3608

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-09 0.05% 0.18% +0.13%
2 2026-01-30 0.03% 0.05% +0.03%
3 2025-11-21 — 0.03% —

Full EPSS history (5 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-3608

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 4.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-3608

OS Trackers for CVE-2025-3608

vendor priority summary link
alpine — CVE-2025-3608: 1 source package rows (firefox); 140 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 140. https://security.alpinelinux.org/vuln/CVE-2025-3608
debian not yet assigned CVE-2025-3608 not yet assigned priority: Debian including 1 source packages (firefox), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-3608
redhat high — https://access.redhat.com/security/cve/CVE-2025-3608
suse high CVE-2025-3608 severity important: SUSE including 11 source package names (MozillaFirefox, MozillaFirefox-137.0.2-1.1, …), 80 product×package rows across 23 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (23 product lines)): Known Not Affected 75, Fixed 5. https://www.suse.com/security/cve/CVE-2025-3608/
ubuntu medium CVE-2025-3608 medium priority: Ubuntu including 9 source packages (firefox, mozjs102, …), 65 status rows across 8 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream): DNE 35, not-affected 11, ignored 10, needs-triage 8, released 1. https://ubuntu.com/security/CVE-2025-3608

Affected software / configurations for CVE-2025-3608

Vendor Product Version Raw CPE
mozilla firefox < 137.0.2 cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:*

References for CVE-2025-3608

cvelogic Threat Intelligence