dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-2577

CRITICAL · 10.0 CVSS v3.1 Published 2026-02-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The WhatsApp bridge component in Nanobot binds the WebSocket server to all network interfaces (0.0.0.0) on port 3001 by default and does not require authentication for incoming connections. An unauthenticated remote attacker with network access to the bridge can connect to the WebSocket server to hijack the WhatsApp session. This allows the attacker to send messages on behalf of the user, intercept all incoming messages and media in real-time, and capture authentication QR codes.

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

The Nanobot WhatsApp bridge component binds its WebSocket server to all network interfaces (0.0.0.0) on port 3001 without any authentication. An unauthenticated remote attacker with network access can connect directly to this exposed WebSocket endpoint and hijack the WhatsApp session, enabling them to send messages as the user, intercept all incoming messages and media in real-time, and capture authentication QR codes.

MitigationRestrict the WebSocket binding to localhost or a trusted network interface, and implement strong authentication (e.g., token-based or certificate-based) for all incoming WebSocket connections to prevent unauthorized session hijacking.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

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. Verify Nanobot WhatsApp bridge is installed
    Locate the Nanobot application on the system. Check for processes named 'nanobot' or 'whatsapp-bridge', or look for installation directories containing 'nanobot'. On Linux, run: ps aux | grep -i nano or find / -name '*nanobot*' 2>/dev/null
    Affected if The Nanobot WhatsApp bridge component is present on the system
  2. Identify the WebSocket binding configuration
    Examine the Nanobot configuration files for the WebSocket server binding. Common locations include config.json, settings.yaml, or .env files in the Nanobot installation directory. Look for a 'websocket', 'bind', 'host', or 'port' configuration setting.
    Affected if The WebSocket server is configured to bind to 0.0.0.0 instead of localhost or a trusted IP
  3. Check if port 3001 is listening on all interfaces
    Run netstat -tlnp or ss -tlnp and examine if port 3001 is bound to 0.0.0.0 or ::. Example: netstat -tlnp | grep 3001
    Affected if Port 3001 is listening on 0.0.0.0 or :::3001 indicating exposure to all network interfaces
  4. Test WebSocket endpoint for authentication
    Use a WebSocket client tool (such as wscat or a browser developer console) to attempt an unauthenticated connection to ws://<your-server-ip>:3001. Observe whether the connection is accepted without providing any credentials or token.
    Affected if The WebSocket connection is accepted without requiring any authentication token or credential
  5. Verify network exposure
    Determine if the host with Nanobot is directly accessible from untrusted networks. Check firewall rules: iptables -L -n or firewall-cmd --list-all on Linux, or check Windows Firewall rules for port 3001.
    Affected if Port 3001 is exposed to the internet or untrusted networks without network-level access controls

A system is affected if the Nanobot WhatsApp bridge is installed with its WebSocket server on port 3001 bound to 0.0.0.0 and accessible without authentication from untrusted networks.

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

Restrict the WebSocket binding to localhost or a trusted network interface, and implement strong authentication (e.g., token-based or certificate-based) for all incoming WebSocket connections to prevent unauthorized session hijacking.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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