PatchSiren cyber security CVE debrief
CVE-2026-84642 Mozilla CVE debrief
CVE-2026-84642 debrief based on the supplied source corpus. The vulnerability in Mozilla Thunderbird allows unintended hostnames to match and serve remote attachments due to unescaped values in the mail.allowed_attachment_hostnames advanced config setting. This issue was fixed in Thunderbird 155 and Thunderbird 153.2. Defenders should assess exposure and potential impact, focusing on email attachment handling and configuration verification. Users and administrators should verify their versions and consider upgrading to the fixed versions.
- Vendor
- Mozilla
- Product
- Thunderbird
- CVSS
- HIGH 7.5
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-01
- Original CVE updated
- 2026-09-03
- Advisory published
- 2026-09-01
- Advisory updated
- 2026-09-03
Who should care
Thunderbird users and administrators should assess exposure and potential impact, focusing on email attachment handling and configuration verification. Defenders should prioritize verifying exposure and assessing potential impact due to the vulnerability in Mozilla Thunderbird. This includes reviewing configurations, considering upgrades, and verifying email security.
Why it matters
Defenders should prioritize verifying exposure and assessing potential impact due to the vulnerability in Mozilla Thunderbird.
- Verify configuration and potential exposure
- Assess impact on email attachment handling
- Consider upgrading to fixed versions
Technical summary
The values of the mail.allowed_attachment_hostnames advanced config setting in Mozilla Thunderbird were used in a regular expression without escaping. This could allow certain unintended hostnames to match and serve remote attachments, potentially affecting email security. The issue was fixed in Thunderbird 155 and Thunderbird 153.2. Defenders should focus on verifying exposure and assessing potential impact on email attachment handling and configuration verification. Users and administrators should review their configurations and consider upgrading to the fixed versions.
Defensive priority
Defenders should prioritize verifying exposure and assessing potential impact.
Recommended defensive actions
- Verify Thunderbird version and assess exposure
- Review mail.allowed_attachment_hostnames configuration
- Consider upgrading to Thunderbird 155 or 153.2
- Review compensating controls for exposed systems
- Check relevant monitoring, detection, and logs for exposed assets
- Track exceptions and retest remediated assets
- Plan vendor-supported updates or mitigations through normal change control
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but limited information is available on potential exploitation or impact. Defenders should verify exposure and assess potential impact by reviewing configuration and email attachment handling. The vulnerability allows certain unintended hostnames to match and serve remote attachments, potentially affecting email security. Evidence is limited, and further verification is necessary to understand the full scope of the vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-84642 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-84642
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-84642 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-84642
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.mozilla.org/security/advisories/mfsa2026-86/
[email protected] - Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://www.mozilla.org/security/advisories/mfsa2026-88/
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.