Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-101074 – Stack-Based Buffer Overflow (Remote Code Execution) – Netcore NR289-GE Firmware 1.

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-101074 is a critical stack-based buffer overflow (CWE-121) in the Authentication component of the Netcore NR289-GE router, specifically in the password-check function of the embedded /bin/boa binary (a Boa web server instance bundled in the firmware). An unauthenticated remote attacker can trigger the overflow by manipulating the Username argument submitted to the device’s login/authentication handler, potentially leading to memory corruption and full system compromise. The flaw is rated critical severity and is remotely exploitable over the network without any privileges or user interaction.

Technical details

  • Root cause: The password-check routine in /bin/boa fails to properly bound-check the Username parameter before copying it into a fixed-size stack buffer, resulting in a stack-based buffer overflow.
  • Trigger conditions: An attacker sends a crafted authentication request to the device’s web management interface with an oversized or malformed Username value.
  • Attack vector: Network — the vulnerable authentication endpoint is exposed remotely, requires no prior authentication, no privileges, and no user interaction.
  • Impact: Successful exploitation can corrupt stack memory, potentially enabling denial of service or arbitrary code execution on the device, leading to full compromise of the router.
  • Exploit status: A public exploit/proof-of-concept for this vulnerability has been disclosed.
  • Vendor response: The vendor was reportedly contacted regarding this disclosure but did not respond.

Affected software

  • Netcore NR289-GE router firmware version 1.4.5102 (Authentication component / /bin/boa binary)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 Base Score: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: No official patched firmware version has been identified from the vendor at the time of publication. Check with Netcore for an updated firmware release addressing this issue and apply it as soon as it becomes available.
  • If no patch is available:
    • Restrict access to the router’s web management/authentication interface to trusted internal networks only; do not expose it to the public internet.
    • Place the device behind a firewall or VPN and disable remote administration if not strictly required.
    • Monitor for anomalous authentication traffic or crash/restart behavior on affected devices, which may indicate exploitation attempts.
    • Consider replacing or isolating affected devices if no vendor fix is issued, given the unauthenticated remote code execution potential.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge