Missing AuthenticationWeakness · CWE-306

CVE-2026-31846

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
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
Missing authentication in the /goform/ate endpoint in Nexxt Solutions Nebula 300+ firmware through version 12.01.01.37 allows an adjacent unauthenticated attacker to retrieve sensitive device information, including the administrator password. An attacker can decode this value to obtain valid administrative credentials and authenticate to the device.

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 /goform/ate endpoint in Nexxt Solutions Nebula 300+ routers (firmware through 12.01.01.37) lacks authentication controls, allowing any adjacent network attacker to access it without credentials. The endpoint returns sensitive parameters including Login_PW, which is Base64-encoded administrator password. An attacker with adjacent network access can retrieve and decode this value to obtain valid admin credentials.

MitigationSince this is a firmware-level vulnerability requiring vendor patch, implement network segmentation to limit adjacent access to the device. Contact vendor for firmware update addressing the missing authentication on /goform/ate endpoint.

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify the router model
    Check the device label or web interface to confirm it is a Nexxt Solutions Nebula 300+ router
    Affected if The device is a Nexxt Solutions Nebula 300+ model
  2. Check the firmware version
    Access the router web interface admin panel and look for a firmware version display (typically under Status, System, or Maintenance sections), or check the kernel/bootloader version via telnet/SSH if enabled
    Affected if The installed firmware version is 12.01.01.37 or any version up to and including 12.01.01.37
  3. Verify the /goform/ate endpoint is accessible without authentication
    From a browser or curl command on the adjacent network, navigate to http://[router-ip]/goform/ate without providing any login credentials. A successful (non-redirect) response indicates the endpoint is exposed
    Affected if The endpoint returns an HTTP 200 response with content rather than redirecting to a login page or returning an authentication error
  4. Confirm password exposure in the response
    Examine the response from /goform/ate for the Login_PW parameter or similar field containing a Base64-encoded string. Decode the value using a Base64 decoder to verify it exposes administrator credentials
    Affected if The response contains a Login_PW field or similar parameter with Base64-encoded data that decodes to what appears to be an administrator password

A user is affected if they have a Nexxt Solutions Nebula 300+ router running firmware 12.01.01.37 or earlier, where the /goform/ate endpoint is accessible without authentication and exposes the Login_PW parameter containing a Base64-encoded administrator password.

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

Since this is a firmware-level vulnerability requiring vendor patch, implement network segmentation to limit adjacent access to the device. Contact vendor for firmware update addressing the missing authentication on /goform/ate endpoint.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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 locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-31846 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