Rv130 FirmwareOperating system · Cisco
CVE-2026-24697
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 · uneditedAn OS command injection vulnerability exists in the start_bonjour() 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 wan_hostname 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 confidenceOS command injection vulnerability in the start_bonjour() function of the rc binary on Cisco RV130/RV130W and RV110W routers. The wan_hostname configuration parameter is not sanitized before being used in system calls, allowing an authenticated remote attacker to inject and execute arbitrary OS commands with root privileges.
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
= 1.0.3.55
Rv130w FirmwareOperating system
= 1.0.3.55
Rv110w FirmwareOperating system
= 1.2.2.5= 1.2.2.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelAccess the router web interface or check the device label to confirm the exact model number (RV130, RV130W, or RV110W)Affected if Model is RV130, RV130W, or RV110W
-
Check firmware versionLog into the router administration interface and navigate to Status > System or similar, or use the CLI command 'show version' via SSH/Telnet to identify the installed firmware versionAffected if Firmware version is exactly 1.0.3.55 (for RV130/RV130W) or exactly 1.2.2.5 or 1.2.2.8 (for RV110W)
-
Verify management interface exposureCheck router firewall settings or network configuration to determine if the web management interface (HTTP/HTTPS on ports 80/443) is accessible from untrusted networksAffected if Management interface is reachable from outside the trusted local network without VPN or ACL restrictions
-
Confirm remote access authenticationReview whether remote management authentication is enabled and accessible to attackers (check for weak or default credentials, or exposed admin login pages)Affected if An authenticated attacker can access the router configuration interface
You are affected if you own an RV130, RV130W, or RV110W router running the specific vulnerable firmware versions listed, with the management interface accessible to an authenticated attacker who can modify the wan_hostname parameter.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate affected routers to patched firmware versions when available from Cisco. Until then, restrict management interface access to trusted networks only and monitor for suspicious activity.
Fix this in Rv130 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24697 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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