# CVE-2026-42072: Nornicdb: Improper Network Binding in NornicDB Bolt Server allows unauthorized remote access

> NornicDB Bolt server ignores address configuration and binds to all interfaces, exposing the database to unauthorized remote access on local networks.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-2hp7-65r3-wv54, GO-2026-4967

## What is CVE-2026-42072?

CVE-2026-42072 is a critical vulnerability in orneryd NornicDB, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nornicdb 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.

Weakness: CWE-1392 (Use of Default Credentials)

## Which versions are affected by CVE-2026-42072?

3 open source packages ship an affected version, including github.com/orneryd/nornicdb.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/orneryd/nornicdb` | Go | All versions | 1.0.42-hotfix |
| `github.com/orneryd/nornicdb` | Go | All versions | 1.0.42-hotfix |
| `github.com/orneryd/nornicdb` | Go | All versions | 1.0.42-hotfix |

## How do I fix CVE-2026-42072?

Upgrade github.com/orneryd/nornicdb to 1.0.42-hotfix or later.

## Is CVE-2026-42072 being exploited?

There is no known exploitation of CVE-2026-42072 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42072 and fix it if it is affected.

What it is: CVE-2026-42072 is a critical vulnerability in orneryd NornicDB, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42072 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/orneryd/nornicdb (Go): affected all versions; fixed in 1.0.42-hotfix
- github.com/orneryd/nornicdb (Go): affected all versions; fixed in 1.0.42-hotfix
- github.com/orneryd/nornicdb (Go): affected all versions; fixed in 1.0.42-hotfix

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42072/ (Markdown: https://insights.sbomify.com/CVE-2026-42072/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42072
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42072
- OSV: https://osv.dev/vulnerability/CVE-2026-42072

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42072/
Summaries are generated and may contain mistakes; the official description above is the record.