CVE-2026-44673

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 58% 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, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

libyang is a YANG data modeling language library. Prior to SO 5.2.15, lyb_read_string() in src/parser_lyb.c contains an integer overflow that results in a heap buffer overflow when parsing a maliciously crafted LYB binary blob. An attacker who can supply LYB data to any libyang consumer (NETCONF server, sysrepo, etc.) can trigger a crash or potential heap corruption. This vulnerability is fixed in SO 5.2.15.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

May 14, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated May 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

lyb_read_string() integer overflow → heap buffer overflow (CWE-190/CWE-122) · Advisory · CESNET/libyang · GitHub

https://github.com/CESNET/libyang/security/advisories/GHSA-vw2p-pq79-92xh

Vendor Advisories for CVE-2026-44673(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibyang-0:2.1.148-1.el9_6.12026-09-08redhat
redhatlibyang-0:2.1.148-1.el9_4.12026-09-08redhat
redhatlibyang-0:2.1.148-1.el9_2.12026-09-08redhat
redhatlibyang-0:1.0.184-1.el8_8.12026-08-06redhat
redhatlibyang-0:1.0.184-1.el8_4.12026-08-06redhat
redhatlibyang-0:1.0.184-1.el8_6.12026-08-06redhat
redhatlibyang-0:2.1.148-2.el10_0.12026-08-03redhat
redhatlibyang-0:2.1.148-1.el9_8.12026-06-10redhat
redhatlibyang-0:2.1.148-4.el10_22026-06-09redhat
redhatlibyang-0:1.0.184-2.el8_102026-06-08redhat

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:11(1)
PackageVulnerable rangeFixed inDependents
libyang1.0.225-1.1 ... 6.1.4-1 (29 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libyang22.1.148-0.1, 2.1.148-0.2, 2.1.30-2, 2.1.30-2.1, 2.1.30-2.1~exp1——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libyang3.12.2-1 ... 6.1.4-1 (22 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libyang3.12.2-1 ... 6.1.4-1 (22 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 36× 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 214 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-44673?
CVE-2026-44673 is a high vulnerability published on May 14, 2026. libyang is a YANG data modeling language library. Prior to SO 5.2.15, lybreadstring() in src/parser_lyb.c contains an integer overflow that results in a heap buffer overflow when parsing a maliciously crafted LYB binary blob. An attacker who can supply LYB data to any libyang consumer (NETCONF…
When was CVE-2026-44673 disclosed?
CVE-2026-44673 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44673 actively exploited?
CVE-2026-44673 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44673?
CVE-2026-44673 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44673?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44673, 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-2026-44673

Explore →

Is Your Infrastructure Affected by CVE-2026-44673?

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

Start Free Scan →Browse All CVEs