CVE-2019-20394

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory published 2022-05-24. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

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%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
86%
KEV
Not listed

Published

January 22, 2020

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Aug 14, 2026
Patch available. Sources: redhat, github_commit.
generic Patch Available

[SECURITY] [DLA 3572-1] libyang security update

https://lists.debian.org/debian-lts-announce/2023/09/msg00019.html
generic

Issue · GitHub

https://github.com/CESNET/libyang/issues/769
generic

Comparing v1.0-r2...v1.0-r3 · CESNET/libyang · GitHub

https://github.com/CESNET/libyang/compare/v1.0-r2...v1.0-r3
github_commit Patch Available

commit 6cc51b1757df (CESNET/libyang)

Patch available: CESNET/libyang v1.0.167 (contains commit 6cc51b1757df)

https://github.com/CESNET/libyang/commit/6cc51b1757dfbb7cff92de074ada65e8523289a6
redhat Patch Available

1793932 – (CVE-2019-20394) CVE-2019-20394 libyang: double-free in yyparse() when a type statement is used in a notification statement

https://bugzilla.redhat.com/show_bug.cgi?id=1793932

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibyang-0:1.0.184-1.el82021-05-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:10(1)
PackageVulnerable rangeFixed inDependents
libyang0.16.105-1, 0.16.105-1+deb10u1, 0.16.105-2, 0.16.105-30.16.105+really1.0-0+deb10u1—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libyang—1.0.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libyang—1.0.176-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libyang—1.0.176-1—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 25× 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 145 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2019-20394?
CVE-2019-20394 is a high vulnerability published on January 22, 2020. A double-free is present in libyang before v1.0-r3 in the function yyparse() when a type statement in used in a notification statement. Applications that use libyang to parse untrusted input yang files may be vulnerable to this flaw, which would cause a crash or potentially code execution.
When was CVE-2019-20394 disclosed?
CVE-2019-20394 was first published in the National Vulnerability Database on January 22, 2020, 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-20394 actively exploited?
CVE-2019-20394 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 14.2% of all scored CVEs.
What is the CVSS score of CVE-2019-20394?
CVE-2019-20394 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2019-20394?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-20394, 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-20394

Explore →

Is Your Infrastructure Affected by CVE-2019-20394?

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

Start Free Scan →Browse All CVEs