CVE-2026-27650
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 · uneditedOS Command Injection vulnerability exists in BUFFALO Wi-Fi router products. If this vulnerability is exploited, an arbitrary OS command may be executed on the products.
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 confidenceOS Command Injection vulnerability in BUFFALO Wi-Fi routers allows remote attackers to execute arbitrary operating system commands, likely through unsanitized input in a web interface or API endpoint. The critical CVSS 9.8 score indicates the flaw is exploitable over the network without authentication.
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< 1.01< 6.02< 5.02< 2.63< 2.63< 5.03< 2.53< 2.62CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Buffalo router modelCheck the device label on the router, or log into the web management interface and look under Status or System Information to find the exact model number (e.g., WCR-1166DHPL, WSR-3600BE4-KH, WXR-1750DHP, etc.)Affected if The model matches any of the affected products: WCR-1166DHPL, WSR-3600BE4-KH, WSR-3600BE4P, WXR-1750DHP, WXR-1750DHP2, WXR-18000BE10P, WXR-1900DHP, or WXR-1900DHP2
-
Check installed firmware versionLog into the router web management interface and navigate to Status or System Settings to view the firmware version. Alternatively, check the Buffalo support website using the model number to locate the current firmware version.Affected if The installed firmware version is below the affected threshold for your model (WCR-1166DHPL < 1.01, WSR-3600BE4-KH < 6.02, WSR-3600BE4P < 5.02, WXR-1750DHP < 2.63, WXR-1750DHP2 < 2.63, WXR-18000BE10P < 5.03, WXR-1900DHP < 2.53, WXR-1900DHP2 < 2.62)
-
Verify web management interface exposureDetermine if the router web management interface (HTTP/HTTPS on ports 80 or 443, or custom ports) is accessible from the internet by attempting to access the router IP from an external network or using an online port scanner. Also check firewall rules that may allow external access to the router management ports.Affected if The web management interface or API endpoints are reachable from untrusted networks (internet), as the vulnerability is exploited via unsanitized input in these interfaces
You are affected if you own any of the listed Buffalo router models AND your firmware version is below the specified threshold AND your router management interface is exposed to untrusted networks.
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.
dbcve · scoped1.012.532.62
Apply available vendor firmware updates immediately; if no patch exists, disable remote management interfaces, restrict administrative access to trusted IPs, and monitor for indicators of compromise.
Upgrade to firmware version 1.01 or later for Wcr 1166dhpl; 6.02 or later for Wsr3600be4 Kh; 5.02 or later for Wsr3600be4p; 2.63 or later for Wxr 1750dhp and Wxr 1750dhp2; 5.03 or later for Wxr18000be10p; 2.53 or later for Wxr 1900dhp; 2.62 or later for Wxr 1900dhp2
- 1. Identify your BUFFALO router model (Wcr 1166dhpl, Wsr3600be4 Kh, Wsr3600be4p, Wxr 1750dhp, Wxr 1750dhp2, Wxr18000be10p, Wxr 1900dhp, or Wxr 1900dhp2)
- 2. Access the router's web administration interface via browser (typically at 192.168.1.1 or 192.168.0.1)
- 3. Navigate to the Administration or System settings section
- 4. Look for Firmware Update or Router Update option
- 5. Download the latest firmware from Buffalo's official support page (www.buffalo.jp) for your specific model
- 6. Upload and install the firmware update through the web interface
- 7. After update completes, verify the firmware version matches or exceeds the fixed version for your model
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27650 — 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-27650 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