CVE-2026-33366
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 · uneditedMissing authentication for critical function vulnerability in BUFFALO Wi-Fi router products may allow an attacker to forcibly reboot the product without authentication.
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 confidenceMissing authentication vulnerability in BUFFALO Wi-Fi routers allows unauthenticated remote attackers to trigger a device reboot via a critical function (likely a CGI endpoint or API). The attack is exploitable over the network without any privileges, leveraging the lack of authentication checks on the reboot mechanism.
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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 your Buffalo router modelCheck the device label or web interface for the exact model name (e.g., Wcr 1166dhpl, Wsr3600be4 Kh, Wxr 1750dhp, etc.)Affected if The model matches one of the affected products: Wcr 1166dhpl, Wsr3600be4 Kh, Wsr3600be4p, Wxr 1750dhp, Wxr 1750dhp2, Wxr18000be10p, Wxr 1900dhp, or Wxr 1900dhp2
-
Determine the installed firmware versionAccess the router web interface and look in System settings or Administration > Firmware Update, or check the device documentation for the command to display firmware versionAffected if The firmware version is below the fixed version for your model (Wcr 1166dhpl: 1.01, Wsr3600be4 Kh: 6.02, Wsr3600be4p: 5.02, Wxr 1750dhp: 2.63, Wxr 1750dhp2: 2.63, Wxr18000be10p: 5.03, Wxr 1900dhp: 2.53, Wxr 1900dhp2: 2.62)
-
Verify router management interface accessibilityCheck your router's firewall or access control settings to determine if the web management interface is reachable from outside your local networkAffected if The router administration interface is accessible from the internet or an untrusted network (not just from local LAN)
-
Confirm reboot functionality is exposedAttempt to access common CGI endpoints on the router (such as /cgi-bin/reboot, /cgi-bin/system, or similar) from an unauthenticated context to see if they respond without loginAffected if The reboot endpoint or similar critical function responds without requiring authentication credentials
You are affected if you own one of the listed Buffalo router models AND your firmware version is below the specified threshold AND the management interface is network-accessible, allowing unauthenticated reboot commands.
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 vendor-supplied firmware updates when available; if no patch exists, restrict router management interface access to trusted networks or disable remote administration to reduce attack surface.
Wcr 1166dhpl: Firmware >= 1.01 | Wsr3600be4 Kh: Firmware >= 6.02 | Wsr3600be4p: Firmware >= 5.02 | Wxr 1750dhp: Firmware >= 2.63 | Wxr 1750dhp2: Firmware >= 2.63 | Wxr18000be10p: Firmware >= 5.03 | Wxr 1900dhp: Firmware >= 2.53 | Wxr 1900dhp2: Firmware >= 2.62
- 1. Identify your Buffalo router model from the affected list: Wcr 1166dhpl, Wsr3600be4 Kh, Wsr3600be4p, Wxr 1750dhp, Wxr 1750dhp2, Wxr18000be10p, Wxr 1900dhp, or Wxr 1900dhp2
- 2. Access the router's web administration interface by entering the router's IP address in a web browser
- 3. Navigate to the Administration or System settings section
- 4. Look for a Firmware Update or Router Update option
- 5. Check the current firmware version under the System Information or Status page
- 6. Download the latest firmware from the official Buffalo support website (www.buffalo.jp) for your specific model
- 7. In the firmware update section, upload the downloaded firmware file
- 8. Wait for the update process to complete - do not power off the router during this process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33366 — 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-33366 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