CVE-2016-1000030

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 2%CVSS: 9.8Exploit: NoneExposed: 0

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

Pidgin version <2.11.0 contains a vulnerability in X.509 Certificates imports specifically due to improper check of return values from gnutls_x509_crt_init() and gnutls_x509_crt_import() that can result in code execution. This attack appear to be exploitable via custom X.509 certificate from another client. This vulnerability appears to have been fixed in 2.11.0.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
76.6%
KEV
Not listed

Published

September 5, 2018

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jun 23, 2026
Patch available. Sources: redhat.
generic

CVE-2016-1000030 Common Vulnerabilities and Exposures | SUSE

https://www.suse.com/pt-br/security/cve/CVE-2016-1000030/
generic

Pidgin: Multiple vulnerabilities (GLSA 201701-38) — Gentoo security

https://security.gentoo.org/glsa/201701-38
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/cve-2016-1000030

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 43× 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-15 16:54 UTCEPSS rescore
  2. 2026-07-15 16:54 UTCEPSS rescore
  3. 2026-07-15 01:56 UTCEPSS rescore
  4. 2026-07-13 22:26 UTCEPSS rescore
  5. 2026-07-13 22:26 UTCEPSS rescore
  6. 2026-07-12 05:42 UTCEPSS rescore
  7. 2026-07-11 08:23 UTCEPSS rescore
  8. 2026-07-09 19:05 UTCEPSS rescore
  9. 2026-07-09 19:05 UTCEPSS rescore
  10. 2026-07-08 15:10 UTCEPSS rescore
  11. 2026-07-07 13:42 UTCEPSS rescore
  12. 2026-07-07 13:42 UTCEPSS rescore
  13. 2026-07-06 16:24 UTCEPSS rescore
  14. 2026-07-06 02:20 UTCEPSS rescore
  15. 2026-07-05 02:26 UTCEPSS rescore
  16. 2026-07-04 06:28 UTCEPSS rescore
  17. 2026-07-04 01:26 UTCOSV refresh
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-06-30 23:19 UTCEPSS rescore
  20. 2026-06-30 23:19 UTCEPSS rescore
  21. 2026-06-29 14:03 UTCEPSS rescore
  22. 2026-06-29 14:03 UTCEPSS rescore
  23. 2026-06-28 14:04 UTCEPSS rescore
  24. 2026-06-28 04:53 UTCEPSS rescore
  25. 2026-06-27 03:05 UTCEPSS rescore
Show 54 more
  1. 2026-06-25 13:47 UTCEPSS rescore
  2. 2026-06-25 13:47 UTCEPSS rescore
  3. 2026-06-24 14:02 UTCEPSS rescore
  4. 2026-06-24 14:02 UTCEPSS rescore
  5. 2026-06-23 21:30 UTCEPSS rescore
  6. 2026-06-22 14:23 UTCEPSS rescore
  7. 2026-06-22 14:23 UTCEPSS rescore
  8. 2026-06-21 14:54 UTCEPSS rescore
  9. 2026-06-21 14:54 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-21 01:57 UTCEPSS rescore
  12. 2026-06-19 19:23 UTCEPSS rescore
  13. 2026-06-19 19:23 UTCEPSS rescore
  14. 2026-06-18 17:50 UTCEPSS rescore
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-17 17:49 UTCEPSS rescore
  17. 2026-06-16 17:50 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-15 17:45 UTCEPSS rescore
  20. 2026-06-15 13:43 UTCOSV refresh
  21. 2026-06-14 23:14 UTCEPSS rescore
  22. 2026-06-13 22:57 UTCEPSS rescore
  23. 2026-06-12 23:09 UTCEPSS rescore
  24. 2026-06-12 23:09 UTCEPSS rescore
  25. 2026-06-11 13:57 UTCEPSS rescore
  26. 2026-06-11 13:57 UTCEPSS rescore
  27. 2026-06-10 22:15 UTCEPSS rescore
  28. 2026-06-10 13:18 UTCEPSS rescore
  29. 2026-06-08 14:14 UTCEPSS rescore
  30. 2026-06-07 15:22 UTCEPSS rescore
  31. 2026-06-06 13:45 UTCEPSS rescore
  32. 2026-06-05 22:44 UTCEPSS rescore
  33. 2026-06-05 06:08 UTCEPSS rescore
  34. 2026-06-05 06:08 UTCEPSS rescore
  35. 2026-06-04 13:10 UTCEPSS rescore
  36. 2026-06-04 13:10 UTCEPSS rescore
  37. 2026-06-02 20:10 UTCEPSS rescore
  38. 2026-06-01 13:49 UTCEPSS rescore
  39. 2026-06-01 13:49 UTCEPSS rescore
  40. 2026-05-31 22:28 UTCEPSS rescore
  41. 2026-05-31 22:28 UTCEPSS rescore
  42. 2026-05-31 00:14 UTCEPSS rescore
  43. 2026-05-29 13:41 UTCEPSS rescore
  44. 2026-05-28 13:42 UTCEPSS rescore
  45. 2026-05-28 13:42 UTCEPSS rescore
  46. 2026-05-28 03:31 UTCEG score recompute
  47. 2026-05-28 03:31 UTCGHSA enrichment
  48. 2026-05-27 21:05 UTCOSV refresh
  49. 2026-05-27 13:38 UTCEPSS rescore
  50. 2026-05-27 13:38 UTCEPSS rescore
  51. 2026-05-26 13:41 UTCEPSS rescore
  52. 2026-05-26 07:16 UTCEPSS rescore
  53. 2026-05-26 07:16 UTCEPSS rescore
  54. 2026-05-24 16:43 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2016-1000030?
CVE-2016-1000030 is a critical vulnerability published on September 5, 2018. Pidgin version <2.11.0 contains a vulnerability in X.509 Certificates imports specifically due to improper check of return values from gnutlsx509crtinit() and gnutlsx509crtimport() that can result in code execution. This attack appear to be exploitable via custom X.509 certificate from another…
When was CVE-2016-1000030 disclosed?
CVE-2016-1000030 was first published in the National Vulnerability Database on September 5, 2018, 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-2016-1000030 actively exploited?
CVE-2016-1000030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 76.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-1000030?
CVE-2016-1000030 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-1000030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-1000030, 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

Explore the affected products and dependency analysis for CVE-2016-1000030

Explore →

Is Your Infrastructure Affected by CVE-2016-1000030?

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

Start Free Scan →Browse All CVEs