Skip to content
Fencer Vulns
high 7.5

CVE-2019-12269 json

Enigmail before 2.0.11 allows PGP signature spoofing: for an inline PGP message, an attacker can cause the product to display a "correctly…

published 2019-05-21 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-3911

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

Enigmail before 2.0.11 allows PGP signature spoofing: for an inline PGP message, an attacker can cause the product to display a "correctly signed" message indication, but display different unauthenticated text.

Patch / fix

  • enigmail enigmail 2.0.11
  • enigmail Debian 11 2:2.0.11+ds1-1

debian advisories DEBIAN-CVE-2019-12269

  • enigmail SLE Workstation Extension 15 SP1, SLE Workstation Extension 15 2.0.11-3.16.1

suse advisories SUSE-SU-2019:1576-1

  • enigmail openSUSE Tumbleweed 2.2.4-1.4
  • enigmail Package Hub 12, openSUSE Leap 15.1, openSUSE Leap 15.0 2.0.11-31.1

opensuse advisories openSUSE-SU-2024:10736-1openSUSE-SU-2019:1612-1

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-2019-12269 updated cvss 4.3

thunderbird-enigmail: signature spoofing in inline PGP message

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

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

Exploits and checks

  • sourceforge.net https://sourceforge.net/p/enigmail/bugs/983/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Vulns 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.