CVE-2019-12981

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.3% (69th percentile of EPSS-scored CVEs). 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
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Ming (aka libming) 0.4.8 has an "fill overflow" vulnerability in the function SWFShape_setLeftFillStyle in blocks/shape.c.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
45
EG Risk 45/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
1.3%
EPSS %ILE
70th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

June 26, 2019

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Aug 24, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 6e76e8c71cb5 (libming/libming)

Fix landed in libming/libming commit 6e76e8c71cb5 — awaiting tagged release

https://github.com/libming/libming/commit/6e76e8c71cb51c8ba0aa9737a636b9ac3029887f

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 24× 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.

Showing the most recent 100 of 159 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-12981?
CVE-2019-12981 is a high vulnerability published on June 26, 2019. Ming (aka libming) 0.4.8 has an "fill overflow" vulnerability in the function SWFShape_setLeftFillStyle in blocks/shape.c.
When was CVE-2019-12981 disclosed?
CVE-2019-12981 was first published on June 26, 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-12981 actively exploited?
CVE-2019-12981 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-12981?
CVE-2019-12981 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2019-12981?
An upstream fix for CVE-2019-12981 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-12981

Explore →

Is Your Infrastructure Affected by CVE-2019-12981?

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

Book a Demo →Browse All CVEs