dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-13735

HIGH · 7.4 CVSS v3.1 Published 2025-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An out-of-bounds read vulnerability exists in the NrCgi.C file within the nr_fw DLP (Data Loss Prevention) module of ASR Lapwing_Linux firmware. This vulnerability affects ASR1903 and ASR3901 devices and allows reading memory outside intended buffer boundaries, potentially leading to information disclosure or denial of service.

MitigationUpdate ASR Lapwing_Linux firmware to a version released on or after 2025/11/26 to incorporate the fix for the vulnerable NrCgi.C component in the nr_fw modules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check if the target device is an ASR1903 or ASR3901 device by examining system information, device labels, or via CLI command such as 'show version' or 'display device information'.
    Affected if Device model is ASR1903 or ASR3901 and runs Lapwing_Linux firmware
  2. Verify nr_fw DLP module presence
    Check if the nr_fw module (Data Loss Prevention) is loaded or enabled on the device. This may be visible via 'lsmod', 'show modules', or checking DLP configuration settings.
    Affected if The nr_fw DLP module is present and active on the device
  3. Check firmware version
    Retrieve the current firmware version using 'show version', 'display version', or similar system command. Note the release date of the installed firmware.
    Affected if Firmware version was released before 2025/11/26 on ASR1903 or ASR3901 devices with nr_fw module enabled
  4. Confirm NrCgi.C component existence
    If firmware filesystem is accessible (via TFTP, USB, or debugging interface), locate the NrCgi.C file within the nr_fw module directory to confirm the vulnerable component is present.
    Affected if NrCgi.C file exists in the nr_fw module path on the device

Device is affected if it is an ASR1903 or ASR3901 running Lapwing_Linux firmware released before 2025/11/26 with the nr_fw DLP module enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update ASR Lapwing_Linux firmware to a version released on or after 2025/11/26 to incorporate the fix for the vulnerable NrCgi.C component in the nr_fw modules.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13735 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data