CVE-2025-8037

Mozilla Firefox vulnerability

9.1 CRITICALEPSS 0.23%

Published22 Jul 2025

Description

Setting a nameless cookie with an equals sign in the value shadowed other cookies. Even if the nameless cookie was set over HTTP and the shadowed cookie included the `Secure` attribute. This vulnerability was fixed in Firefox 141, Firefox ESR 140.1, Thunderbird 141, and Thunderbird 140.1.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Mozilla Firefox< 141.0 · < 140.1

Mozilla Thunderbird< 141.0 · < 140.1

Remediation

Fixed in

Mozilla Firefox≥ 141.0

Mozilla Thunderbird≥ 141.0

Patch & vendor advisories

References

https://bugzilla.mozilla.org/show_bug.cgi?id=1964767Permissions Required
https://www.mozilla.org/security/advisories/mfsa2025-56/Vendor Advisory
https://www.mozilla.org/security/advisories/mfsa2025-59/Vendor Advisory
https://www.mozilla.org/security/advisories/mfsa2025-61/Vendor Advisory
https://www.mozilla.org/security/advisories/mfsa2025-63/Vendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-8037 being actively exploited?

CVE-2025-8037 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.23%.

How severe is CVE-2025-8037?

CVE-2025-8037 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.23% probability of exploitation.

Which products are affected by CVE-2025-8037?

Affected products include Mozilla Firefox, Mozilla Thunderbird.

How do I fix CVE-2025-8037?

Upgrade affected software to a fixed version, for example Mozilla Firefox 141.0, Mozilla Thunderbird 141.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-8037 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.