<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 12:41:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-316822</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-316822</link>
      <description>EUVD-2026-316822</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-316822</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42072</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42072</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42072</guid>
    </item>
    <item>
      <title>GHSA-2hp7-65r3-wv54 — NornicDB has Improper Network Binding in its Bolt Server, allowing unauthorized remote access</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2hp7-65r3-wv54</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/orneryd/nornicdb&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;On a LAN, this exposes the graph database — with its default `admin:password` credentials — to any device sharing the network.&lt;/p&gt;
&lt;p&gt;## Version&lt;/p&gt;
&lt;p&gt;- `nornicdb v1.0.39`
- Built from commit `afe7c9d` on `main`
- Platform: macOS (darwin 25.4.0, arm64)&lt;/p&gt;
&lt;p&gt;## Reproduction&lt;/p&gt;
&lt;p&gt;```
$ nornicdb serve --address 127.0.0.1 --bolt-port 7687 --http-port 7474 ...
```&lt;/p&gt;
&lt;p&gt;Output claims Bolt is on localhost:
```
Bolt server listening on bolt://localhost:7687
```&lt;/p&gt;
&lt;p&gt;But the actual socket:
```
$ netstat -an -p tcp | grep 7687
tcp46      0      0  *.7687                 *.*                    LISTEN&lt;/p&gt;
&lt;p&gt;$ lsof -iTCP:7687 -sTCP:LISTEN -n -P
nornicdb ... IPv6 ... TCP *:7687 (LISTEN)
```&lt;/p&gt;
&lt;p&gt;HTTP port is correctly bound:
```
tcp4  127.0.0.1.7474   *.*  LISTEN
```&lt;/p&gt;
&lt;p&gt;Reachable from another host on the LAN:
```
$ nc -z 192.168.x.y 7687
Connection to 192.168.x.y port 7687 [tcp/*] succeeded!
```&lt;/p&gt;
&lt;p&gt;Setting `NORNICDB_BOLT_ADDRESS=127.0.0.1` or `server.host: &amp;#34;127.0.0.1&amp;#34;` in `config.yaml` has **no effect** on the Bolt listener.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;In `pkg/bolt/server.go:774-776`:&lt;/p&gt;
&lt;p&gt;```go
func (s *Server) ListenAndServe() error {
    addr := fmt.Sprintf(&amp;#34;:%d&amp;#34;, s.config.Port)
    listener, err := net.Listen(&amp;#34;tcp&amp;#34;, addr)
    ...
}
```&lt;/p&gt;
&lt;p&gt;`…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/orneryd/nornicdb&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;On a LAN, this exposes the graph database — with its default `admin:password` credentials — to any device sharing the network.&lt;/p&gt;
&lt;p&gt;## Version&lt;/p&gt;
&lt;p&gt;- `nornicdb v1.0.39`
- Built from commit `afe7c9d` on `main`
- Platform: macOS (darwin 25.4.0, arm64)&lt;/p&gt;
&lt;p&gt;## Reproduction&lt;/p&gt;
&lt;p&gt;```
$ nornicdb serve --address 127.0.0.1 --bolt-port 7687 --http-port 7474 ...
```&lt;/p&gt;
&lt;p&gt;Output claims Bolt is on localhost:
```
Bolt server listening on bolt://localhost:7687
```&lt;/p&gt;
&lt;p&gt;But the actual socket:
```
$ netstat -an -p tcp | grep 7687
tcp46      0      0  *.7687                 *.*                    LISTEN&lt;/p&gt;
&lt;p&gt;$ lsof -iTCP:7687 -sTCP:LISTEN -n -P
nornicdb ... IPv6 ... TCP *:7687 (LISTEN)
```&lt;/p&gt;
&lt;p&gt;HTTP port is correctly bound:
```
tcp4  127.0.0.1.7474   *.*  LISTEN
```&lt;/p&gt;
&lt;p&gt;Reachable from another host on the LAN:
```
$ nc -z 192.168.x.y 7687
Connection to 192.168.x.y port 7687 [tcp/*] succeeded!
```&lt;/p&gt;
&lt;p&gt;Setting `NORNICDB_BOLT_ADDRESS=127.0.0.1` or `server.host: &amp;#34;127.0.0.1&amp;#34;` in `config.yaml` has **no effect** on the Bolt listener.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;In `pkg/bolt/server.go:774-776`:&lt;/p&gt;
&lt;p&gt;```go
func (s *Server) ListenAndServe() error {
    addr := fmt.Sprintf(&amp;#34;:%d&amp;#34;, s.config.Port)
    listener, err := net.Listen(&amp;#34;tcp&amp;#34;, addr)
    ...
}
```&lt;/p&gt;
&lt;p&gt;`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2hp7-65r3-wv54</guid>
    </item>
  </channel>
</rss>
