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.4%, top 65% 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
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%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
0%
EPSS %ILE
35%
KEV
Not listed

Published

May 14, 2026

Last Modified

July 15, 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(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 31× 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 121 total refreshes for this CVE.

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

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 July 15, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 64.9% 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

Explore the affected products and dependency analysis for 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