# CVE-2025-13735: Out-of-bounds Read in nr flc

> An out-of-bounds read in the ASR Lapwing Linux kernel allows attackers to read sensitive memory or cause a denial of service.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Nov 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-8mjc-g2w7-fch8, ROOT-OS-UBUNTU-2204-CVE-2025-13735

## What is CVE-2025-13735?

CVE-2025-13735 is a high-severity memory corruption vulnerability in ASR Lapwing_Linux, published on 26 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Out-of-bounds Read vulnerability in ASR1903、ASR3901 in ASR Lapwing_Linux on Linux (nr_fw modules). This vulnerability is associated with program files Code/nr_fw/DLP/src/NrCgi.C.

This issue affects Lapwing_Linux: before 2025/11/26.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2025-13735?


## How do I fix CVE-2025-13735?

Apply the vendor's patch.

## Is CVE-2025-13735 being exploited?

There is no known exploitation of CVE-2025-13735 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13735 and fix it if it is affected.

What it is: CVE-2025-13735 is a high-severity memory corruption vulnerability in ASR Lapwing_Linux, published on 26 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13735 in the wild and no public exploit code.

Affected product: ASR Lapwing_Linux. 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-2025-13735/ (Markdown: https://insights.sbomify.com/CVE-2025-13735/index.md)
```

## Sources

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

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