Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/orneryd/nornicdb

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.8GoPublished

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

    CVE-2026-42072 · GHSA-2hp7-65r3-wv54

    Affected
    • Go github.com/orneryd/nornicdb < 1.0.42-hotfix
    Fixed in
    1.0.42-hotfix· Vendor fix available
    Issue
    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…

    Recommended action: Upgrade to 1.0.42-hotfix (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →