dbcve.org
Asr1803 FirmwareOperating system · Asrmicro

CVE-2026-42799

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-30
Fix available
A fix is available. Upgrade to 1.216.002 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 ASR Kestrel (nr_fw modules) allows Overflow Buffers. This vulnerability is associated with program files Code/Nr/nr_fw/RA/src/NrPwrCtrl.C. This issue affects Kestrel: before 2026/02/10.

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 ASR Kestrel firmware's nr_fw modules, specifically in the NrPwrCtrl.C file (power control code). The vulnerability allows buffer overflow to occur by reading beyond allocated buffer boundaries, potentially enabling remote code execution or denial of service with no authentication required.

MitigationApply the vendor firmware update released on or after 2026/02/10 which contains the patched nr_fw module. If immediate patching is not possible, restrict network access to affected ASR Kestrel devices as a compensating control.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Asr1803 FirmwareOperating system
Affected:< 1.216.002

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the device model and firmware line
    Determine if the target device runs ASR Kestrel firmware or uses the Asrmicro Asr1803 chipset. Check device documentation, boot logs, or system information for the ASR platform identifier.
    Affected if The device is confirmed to be an ASR Kestrel or Asr1803-based system
  2. Locate the firmware version
    Access the device's firmware information through its management interface, boot logs, system settings, or by extracting the firmware image if accessible. Look for version strings in the format X.X.X.XXX.
    Affected if The installed firmware version cannot be determined or is below 1.216.002
  3. Confirm firmware version is in affected range
    Compare the identified firmware version against the affected range. Versions prior to 1.216.002 are considered vulnerable.
    Affected if The installed firmware version is 1.216.002 or higher - the version is NOT in the affected range
  4. Check for nr_fw module presence
    If firmware version cannot be determined directly, examine the firmware image or device filesystem for the nr_fw module directory and specifically locate the NrPwrCtrl.C or compiled NrPwrCtrl component.
    Affected if The nr_fw module with NrPwrCtrl component is present and the firmware version is unknown or below 1.216.002
  5. Verify power control functionality is active
    Determine if the power control subsystem (NrPwrCtrl) is enabled and operational on the device. This may involve checking running processes, loaded modules, or system configuration.
    Affected if The power control code is active and the firmware version is below 1.216.002

A user is affected if the device runs ASR Kestrel or Asr1803 firmware with version lower than 1.216.002 and contains the nr_fw module with NrPwrCtrl component.

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.

dbcve · scoped
Upgrade available Upgrade to 1.216.002 or later
Fixed in 1.216.002
Interim mitigation

Apply the vendor firmware update released on or after 2026/02/10 which contains the patched nr_fw module. If immediate patching is not possible, restrict network access to affected ASR Kestrel devices as a compensating control.

Recommended fix Moderate confidence

Asr1803 Firmware version 1.216.002 or later

  1. 1. Obtain the latest Asr1803 firmware version 1.216.002 or later from AsrMicro's official download portal or contact their support
  2. 2. Review the firmware release notes to confirm the vulnerability fix is included
  3. 3. Backup the current firmware configuration if supported by the device
  4. 4. Follow the vendor's standard firmware upgrade procedure for the Asr1803 platform
  5. 5. Verify the upgrade was successful by checking the firmware version post-installation
  6. 6. Test that the nr_fw modules (particularly NrPwrCtrl) function normally after the upgrade
Caveat Review vendor release notes for any configuration or compatibility changes between current and target firmware versions before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Asr1803 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42799 — 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-2026-42799 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