CVE-2019-11841

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 2.0%, top 21% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 2%CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The "Hash" Armor Header specifies the message digest algorithm(s) used for the signature. However, the Go clearsign package ignores the value of this header, which allows an attacker to spoof it. Consequently, an attacker can lead a victim to believe the signature was generated using a different message digest algorithm than what was actually used. Moreover, since the library skips Armor Header parsing in general, an attacker can not only embed arbitrary Armor Headers, but also prepend arbitrary text to cleartext messages without invalidating the signatures.

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
78.7%
KEV
Not listed

Published

May 22, 2019

Last Modified

November 21, 2024

References (14)

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
golang.org/x/crypto—0.0.0-20190424203555-c05e17bb3b2d—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:19 UTCEG score recompute
  2. 2026-07-22 14:05 UTCEPSS rescore
  3. 2026-07-21 15:22 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-20 16:02 UTCOSV refresh
  7. 2026-07-19 14:28 UTCEPSS rescore
  8. 2026-07-19 14:28 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-19 02:26 UTCEPSS rescore
  11. 2026-07-18 10:01 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-16 16:59 UTCEPSS rescore
  14. 2026-07-15 16:55 UTCEPSS rescore
  15. 2026-07-13 22:27 UTCEPSS rescore
  16. 2026-07-13 06:10 UTCEPSS rescore
  17. 2026-07-13 06:10 UTCEPSS rescore
  18. 2026-07-12 05:43 UTCEPSS rescore
  19. 2026-07-11 08:24 UTCEPSS rescore
  20. 2026-07-09 19:06 UTCEPSS rescore
  21. 2026-07-08 15:11 UTCEPSS rescore
  22. 2026-07-07 13:42 UTCEPSS rescore
  23. 2026-07-06 16:25 UTCEPSS rescore
  24. 2026-07-06 02:20 UTCEPSS rescore
  25. 2026-07-05 02:27 UTCEPSS rescore
Show 69 more
  1. 2026-07-04 06:28 UTCEPSS rescore
  2. 2026-07-04 06:28 UTCEPSS rescore
  3. 2026-07-03 11:26 UTCOSV refresh
  4. 2026-07-02 16:56 UTCEPSS rescore
  5. 2026-07-01 15:03 UTCEPSS rescore
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-06-30 23:20 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-29 14:03 UTCEPSS rescore
  10. 2026-06-28 14:04 UTCEPSS rescore
  11. 2026-06-28 04:54 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-27 03:06 UTCEPSS rescore
  14. 2026-06-27 03:06 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-23 21:30 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:23 UTCEPSS rescore
  22. 2026-06-22 14:23 UTCEPSS rescore
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
  26. 2026-06-21 01:57 UTCEPSS rescore
  27. 2026-06-19 19:23 UTCEPSS rescore
  28. 2026-06-19 19:23 UTCEPSS rescore
  29. 2026-06-18 17:50 UTCEPSS rescore
  30. 2026-06-17 17:50 UTCEPSS rescore
  31. 2026-06-16 17:50 UTCEPSS rescore
  32. 2026-06-15 17:45 UTCEPSS rescore
  33. 2026-06-15 01:43 UTCOSV refresh
  34. 2026-06-14 23:15 UTCEPSS rescore
  35. 2026-06-14 23:15 UTCEPSS rescore
  36. 2026-06-13 22:58 UTCEPSS rescore
  37. 2026-06-12 23:09 UTCEPSS rescore
  38. 2026-06-11 13:58 UTCEPSS rescore
  39. 2026-06-11 13:58 UTCEPSS rescore
  40. 2026-06-10 22:16 UTCEPSS rescore
  41. 2026-06-10 13:19 UTCEPSS rescore
  42. 2026-06-08 14:15 UTCEPSS rescore
  43. 2026-06-08 14:14 UTCEPSS rescore
  44. 2026-06-07 15:23 UTCEPSS rescore
  45. 2026-06-07 15:22 UTCEPSS rescore
  46. 2026-06-06 13:45 UTCEPSS rescore
  47. 2026-06-06 13:45 UTCEPSS rescore
  48. 2026-06-05 22:45 UTCEPSS rescore
  49. 2026-06-05 22:45 UTCEPSS rescore
  50. 2026-06-05 06:08 UTCEPSS rescore
  51. 2026-06-05 06:08 UTCEPSS rescore
  52. 2026-06-04 13:10 UTCEPSS rescore
  53. 2026-06-04 13:10 UTCEPSS rescore
  54. 2026-06-02 20:11 UTCEPSS rescore
  55. 2026-06-01 13:50 UTCEPSS rescore
  56. 2026-06-01 13:50 UTCEPSS rescore
  57. 2026-05-31 22:29 UTCEPSS rescore
  58. 2026-05-31 22:29 UTCEPSS rescore
  59. 2026-05-31 00:14 UTCEPSS rescore
  60. 2026-05-31 00:14 UTCEPSS rescore
  61. 2026-05-29 13:42 UTCEPSS rescore
  62. 2026-05-28 13:43 UTCEPSS rescore
  63. 2026-05-27 19:19 UTCEG score recompute
  64. 2026-05-27 13:38 UTCEPSS rescore
  65. 2026-05-26 13:42 UTCEPSS rescore
  66. 2026-05-26 13:42 UTCEPSS rescore
  67. 2026-05-26 07:17 UTCEPSS rescore
  68. 2026-05-26 07:17 UTCEPSS rescore
  69. 2026-05-25 22:16 UTCOSV refresh

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-11841?
CVE-2019-11841 is a medium vulnerability published on May 22, 2019. A message-forgery issue was discovered in crypto/openpgp/clearsign/clearsign.go in supplementary Go cryptography libraries 2019-03-25. According to the OpenPGP Message Format specification in RFC 4880 chapter 7, a cleartext signed message can contain one or more optional "Hash" Armor Headers. The…
When was CVE-2019-11841 disclosed?
CVE-2019-11841 was first published in the National Vulnerability Database on May 22, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-11841 actively exploited?
CVE-2019-11841 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 78.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-11841?
CVE-2019-11841 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2019-11841?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-11841, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-11841

Explore →

Is Your Infrastructure Affected by CVE-2019-11841?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs