CVE-2026-42072: orneryd NornicDB · Use of Default Credentials
Affects orneryd NornicDBSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.0.42-hotfix as a priority.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.42-hotfix
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade orneryd NornicDB to 1.0.42-hotfix.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ornerydNornicDB | Affected
| Fixed in
|
GitHuborneryd/NornicDBpkg:github/orneryd/NornicDBOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade NornicDB to version 1.0.42-hotfix or later, where the Bolt server listener correctly respects the configured address and does not bind to all interfaces by default. This patch effectively mitigates the exposure of the database with default credentials on the network. Until upgraded, restrict network access to the Bolt server interface to trusted hosts only.
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.