NornicDB has Improper Network Binding in its Bolt Server, allowing unauthorized remote access

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-42072: 0.44% estimated exploitation activity in the next 30 days; percentile 38.27 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The --address CLI flag (and NORNICDBADDRESS / 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. Version - nornicdb v1.0.39 - Built from commit afe7c9d on main - Platform: macOS (darwin 25.4.0, arm64) Reproduction Output claims Bolt is on localhost: But the actual socket: HTTP port is correctly bound: Reachable from another host on the LAN: Setting NORNICDBBOLTADDRESS=127.0.0.1 or server.host: "127.0.0.1" in config.yaml has no effect on the Bolt listener. Root Cause In pkg/bolt/server.go:774-776: bolt.Config (line 474) has no Host/Address/Addr field — only Port. The CLI flag --address is stored in a local variable in cmd/nornicdb/main.go:80 and used to format user-facing…

Published by the source

22 Apr 2026, 22:03 UTC

Last modified by the source

13 May 2026, 13:30 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2hp7-65r3-wv54

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42072

Advisory: NornicDB has Improper Network Binding in its Bolt Server, allowing unauthorized remote access
IDs: CVE-2026-42072, GHSA-2hp7-65r3-wv54
Record: https://patchnext.com/advisories/cve-2026-42072 (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/orneryd/nornicdb 1.0.42-hotfix. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/orneryd/nornicdb: affected < 1.0.42-hotfix; fixed in 1.0.42-hotfix

## Suggested inspection (read-only)
- Go github.com/orneryd/nornicdb: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/orneryd/nornicdb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2hp7-65r3-wv54 (GitHub-reviewed advisory GHSA-2hp7-65r3-wv54 lists affected ranges: Go github.com/orneryd/nornicdb >=0 <1.0.42-hotfix)

Commands are suggestions: review each one before running it.