Skip to content
Fencer Intel
no cvss —

CVE-2026-126132 json

Attachments could be replaced with local file content when forwarding

published yesterday modified yesterday also EUVD-2026-122686

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

When a message was forwarded inline, edited as new, or had an attachment dragged into a compose window, a specially crafted link attachment (a .desktop file on Linux, or a .url or .lnk file on Windows) was replaced with the content of the file or URL it pointed to when the message was saved or sent. This could disclose local files, or content from the user's network, to the message recipients or to the mail provider. This bug only affects Thunderbird on Linux and Windows. Other operating systems are unaffected. This vulnerability was fixed in Thunderbird 160 and Thunderbird 153.7.

Is CVE-2026-126132 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-126132 updated cvss 7.5

thunderbird: Attachments could be replaced with local file content when forwarding

  • Red Hat Enterprise Linux 6 thunderbird Red Hat Enterprise Linux 7 thunderbird
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 thunderbird Red Hat Enterprise Linux 9 thunderbird Red Hat Enterprise Linux 10 thunderbird, rhel10/thunderbird-flatpak
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).

Affected products

  • Mozilla Thunderbird

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.