CVE-2023-26916

libyang from v2.0.164 to v2.1.30 was discovered to contain a NULL pointer dereference via the function lys_parse_mem at lys_parse_mem.c.

Published: 2023-04-03 Last update: 2025-02-18 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-26916 is rated Moderate Risk (42.2/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.99%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-26916

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.19% 0.99% +0.80%
2 2026-05-05 0.30% 0.19% -0.11%
3 2026-04-19 — 0.30% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-26916

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2023-26916

OS Trackers for CVE-2023-26916

vendor priority summary link
alpine — CVE-2023-26916: 1 source package rows (libyang); 1 state rows across 1 repos (3.17-community); fixed 0, open 1. https://security.alpinelinux.org/vuln/CVE-2023-26916
debian not yet assigned CVE-2023-26916 not yet assigned priority: Debian including 2 source packages (libyang, libyang2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2023-26916
redhat low — https://access.redhat.com/security/cve/CVE-2023-26916
suse medium CVE-2023-26916 severity moderate: SUSE including 10 source package names (libyang, libyang-devel-2.1.55-1.1, …), 38 product×package rows across 14 product lines (SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 15 SP3-ESPOS, … (14 product lines)): Known Not Affected 32, Fixed 6. https://www.suse.com/security/cve/CVE-2023-26916/
ubuntu medium CVE-2023-26916 medium priority: Ubuntu including 2 source packages (libyang, libyang2), 16 status rows across 12 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, trusty, upstream, xenial): DNE 5, not-affected 5, ignored 3, needs-triage 2, released 1. https://ubuntu.com/security/CVE-2023-26916

Affected software / configurations for CVE-2023-26916

Vendor Product Version Raw CPE
cesnet libyang >= 2.0.164, <= 2.1.30 cpe:2.3:a:cesnet:libyang:*:*:*:*:*:*:*:*
fedoraproject fedora 36 cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
fedoraproject fedora 37 cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*

References for CVE-2023-26916

cvelogic Threat Intelligence