CVE-2026-42072
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 · uneditedNornicdb is a distributed low-latency, Graph+Vector, Temporal MVCC with all sub-ms HNSW search, graph traversal, and writes. Prior to version 1.0.42-hotfix, the --address CLI flag (and NORNICDB_ADDRESS / server.host config key) is plumbed through to the HTTP server correctly but never reaches the Bolt server config. The Bolt listener therefore always binds to the wildcard address (all interfaces), regardless of what the user configures. On a LAN, this exposes the graph database — with its default admin:password credentials — to any device sharing the network. This issue has been patched in version 1.0.42-hotfix.
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 confidenceNornicdb's Bolt database server ignores the user-configured binding address (--address CLI flag or server.host config) and always binds to the wildcard address (0.0.0.0), exposing the database with default admin:password credentials to any device on the local network.
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
- 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 installed nornicdb versionRun `nornicdb --version` or check the package manager output to see the installed version numberAffected if Version is before 1.0.42-hotfix and you intended to bind to a specific address
-
Verify configured binding addressCheck your configuration file (typically in /etc/nornicdb/ or the working directory) for server.host setting, or review your startup command for the --address flagAffected if A specific non-wildcard address was configured (e.g., 127.0.0.1 or a specific IP)
-
Inspect actual listening addressRun `ss -tlnp | grep bolt` or `netstat -tlnp | grep bolt` to see which address the Bolt server is actually listening onAffected if Server is listening on 0.0.0.0 despite a specific address being configured
-
Confirm network exposureFrom another machine on the same network, attempt to connect to the Bolt port using the local IP address (default port 7687)Affected if The database is reachable from other devices on the network when it should have been restricted
You are affected if running a version before 1.0.42-hotfix and the server is bound to 0.0.0.0 regardless of your explicit address configuration.
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 · scopedUpgrade to version 1.0.42-hotfix which properly propagates the configured address to the Bolt server, and change default credentials immediately if not yet patched.
1.0.42-hotfix
- Upgrade to version 1.0.42-hotfix or later which contains the patch for proper address configuration propagation to the Bolt server
- After upgrading, verify the --address CLI flag or NORNICDB_ADDRESS / server.host config is correctly applied to both HTTP and Bolt listeners
- If running in a LAN environment, ensure the configured address is not exposing the database to untrusted networks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42072 — 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-42072 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