dbcve.org
Rv130 FirmwareOperating system · Cisco

CVE-2026-24699

HIGH · 7.2 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click 6 weeks old

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
An OS command injection vulnerability exists in the sub_34984() function of the "rc" binary in Cisco RV130/RV130W with firmware 1.0.3.55 and RV110W routers with firmware 1.2.2.5 / 1.2.2.8. The lan_ipv6_prefixlen configuration parameter is not properly sanitized, which could allow an authenticated remote attacker to execute arbitrary OS commands with root privileges.

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 · high confidence

OS command injection vulnerability in Cisco RV130/RV130W and RV110W routers where the lan_ipv6_prefixlen configuration parameter passed to the sub_34984() function in the 'rc' binary is not properly sanitized, allowing an authenticated attacker to inject arbitrary OS commands executed with root privileges.

MitigationApply Cisco-provided firmware updates for RV130/RV130W (1.0.3.55) and RV110W (1.2.2.5/1.2.2.8). If patches unavailable, restrict management interface access via ACLs and network segmentation to minimize attack surface.

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
Rv130 FirmwareOperating system
Affected:= 1.0.3.55
Rv130w FirmwareOperating system
Affected:= 1.0.3.55
Rv110w FirmwareOperating system
Affected:= 1.2.2.5= 1.2.2.8

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

CVSS:3.1/AV:N/AC:L/PR:H/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 router model and firmware version
    Access the router web interface (typically at 192.168.1.1) and navigate to Status > System Summary, or use CLI: 'show version' via SSH/Telnet to retrieve the exact firmware build
    Affected if The firmware version matches 1.0.3.55 (RV130/RV130W) or 1.2.2.5/1.2.2.8 (RV110W)
  2. Verify IPv6 LAN configuration is present
    In the router web interface, go to IPv6 Setup > LAN Settings, or via CLI check for lan_ipv6_prefixlen configuration: 'cat /tmp/etc rc.conf' or equivalent config file that stores this parameter
    Affected if The lan_ipv6_prefixlen parameter is defined and set in the router configuration (indicates IPv6 LAN is configured)
  3. Confirm management interface accessibility
    Check if the router admin interface (HTTP/HTTPS on ports 80/443) is reachable from untrusted networks, or review ACL configurations: 'show ip access-lists' or check WAN-side firewall rules
    Affected if The management interface is exposed to WAN or untrusted networks without proper ACL restrictions (authenticated attacker required for exploitation)
  4. Check for remote management enablement
    In web interface, go to Administration > Management, or review config for 'http_enable' or 'https_enable' settings; verify if 'remote management' or 'web management' is enabled for WAN access
    Affected if Remote management is enabled allowing authentication attempts from outside the trusted network

You are affected if your router runs RV130/RV130W firmware 1.0.3.55 or RV110W firmware 1.2.2.5/1.2.2.8, has IPv6 LAN configured, and the management interface is accessible to an authenticated attacker.

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

Apply Cisco-provided firmware updates for RV130/RV130W (1.0.3.55) and RV110W (1.2.2.5/1.2.2.8). If patches unavailable, restrict management interface access via ACLs and network segmentation to minimize attack surface.

Fix this in Rv130 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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