# CVE-2026-115327: libyang through 6.4.13 Uninitialized Pointer Free in NETCONF RPC Parser


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** AZL-110492, DEBIAN-CVE-2026-115327, GHSA-x4q2-x59g-x339, UBUNTU-CVE-2026-115327, openSUSE-SU-2026:12301-1

## What is CVE-2026-115327?

CVE-2026-115327 is a medium-severity vulnerability in CESNET libyang, published on 22 Oct 2026. 

### Official description

libyang through 6.4.13 contains an uninitialized pointer free vulnerability in lydxml_env_netconf_rpc() in src/parser_xml.c when parsing NETCONF rpc action envelopes. Peers with a NETCONF session can send an action element containing non-whitespace text via lyd_parse_op() to crash servers like netopeer2 or corrupt the heap.

Weakness: CWE-824 (Access of Uninitialized Pointer)

## Which versions are affected by CVE-2026-115327?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libyang` | openSUSE:Tumbleweed | All versions | 3.13.6-4.1 |

## How do I fix CVE-2026-115327?

Upgrade to a fixed version.

## Is CVE-2026-115327 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115327 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115327 and fix it if it is affected.

What it is: CVE-2026-115327 is a medium-severity vulnerability in CESNET libyang, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-115327 exists.

Affected product: CESNET libyang. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115327/ (Markdown: https://insights.sbomify.com/CVE-2026-115327/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115327
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115327
- OSV: https://osv.dev/vulnerability/CVE-2026-115327

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115327/
Summaries are generated and may contain mistakes; the official description above is the record.