Read 2026-10-22
netbirdio/netbird: technical due diligence, read from its repository
What Borehole read in netbirdio/netbird's code and history at f548a74: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | strong |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | adequate |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
LICENSE.md: Relicensed: BSD-3-Clause → AGPL-3.0 (2025-08-05)
Architecture & Codebase — including AI provenance
strongmanagement/server/store/store_mock.go is 4,065 lines, 35× this codebase's median file
adequateThe median source file here is 115 lines. 31 files exceed 1,150 lines, the largest being 4,065. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
management/server/store/store_mock.go:1 — 4,065 lines (35× median) |
client/server/server.go:1 — 3,006 lines (26× median) |
client/internal/engine.go:1 — 2,989 lines (25× median) |
client/proto/daemon.pb.gw.go:1 — 2,922 lines (25× median) |
management/server/account.go:1 — 2,918 lines (25× median) |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequate137 direct dependencies in a single manifest
adequatego.mod declares 137 direct dependencies. Each one is a maintenance obligation, a supply-chain surface and a potential licence question that transfers with the asset. The count says nothing about whether any given dependency was a good choice; it says how many such choices a buyer inherits.
go.mod — 137 declared |
client/ui/frontend/package.json — 24 declared |
proxy/web/package.json — 5 declared |
client/internal/metrics/infra/ingest/go.mod — 1 declared |
Go 1.25 is past end of life
adequateThe code is pinned to Go 1.25 (end of life 2026-08-11). None of these receives security fixes any more; the first stopped on 2026-08-11. Moving off an unsupported runtime is rarely a one-line change, so a buyer should ask whether the upgrade is planned and what it touches.
client/internal/metrics/infra/ingest/Dockerfile — Go 1.25, end of life 2026-08-11 |
Releases are cut from another branch than the one surveyed
adequateThe newest release, v0.81.3, is not on the branch this survey read; the newest release on it is v0.81.1. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v0.81.3 |
Security & Reliability Posture
adequate1 credential-shaped string in the tree sit in tests, examples, documentation or local development settings
adequateStrings shaped like credentials appear only where fakes are usual: test fixtures, examples, documentation, placeholders and local stacks. They are almost always fakes. Ask someone to confirm that none of them works anywhere, because a real key in a development file is still a real key.
| JWT, where fakes are usual |
5 Dockerfiles run the application as root
adequateNo USER instruction switches away from root, so the process runs with full privileges inside the container. It is a one-line fix and an ordinary expectation, which is why its absence is worth asking about: it usually says more about whether anyone has reviewed the deployment than about this container specifically.
client/Dockerfile — runs as root |
combined/Dockerfile — runs as root |
management/Dockerfile — runs as root |
relay/Dockerfile — runs as root |
The build runs third-party code it does not pin
adequate1 step pipes a download straight into a shell. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.
infrastructure_files/getting-started.sh:161 — download piped into a shell |
8 outbound calls can wait forever
adequate8 HTTP calls use a client with no timeout (Python `requests` without `timeout=`, or Go's default client). When a dependency slows down, each one holds a worker until the connection gives up, and enough of them take the service down with the dependency.
management/cmd/management.go:413 — outbound call without a timeout |
management/server/geolocation/utils.go:154 — outbound call without a timeout |
management/server/geolocation/utils.go:180 — outbound call without a timeout |
2 SQL statements built from strings
adequate2 places in product code build SQL by formatting or joining strings rather than passing parameters. In each, what the code shows going in is a table or column name, a constant, or something the line does not show, not a request's value. Ask whether any value reaches these strings, rather than a parameter.
management/server/store/store.go:943 — SQL built from a string |
management/server/store/store.go:1032 — SQL built from a string |
12 locked dependencies have published vulnerabilities, 2 high or critical in what ships
adequate12 of 796 locked dependencies match 20 published advisories in OSV, 2 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.
Relicensed: BSD-3-Clause → AGPL-3.0 (2025-08-05)
adequateThe root licence changed 1 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.
LICENSE.md — BSD-3-Clause from 2021-05-11 |
LICENSE — AGPL-3.0 from 2025-08-05 |
10 advisories against this project in the last 24 months, 6 high or critical
adequateThe newest was published on 2026-09-01. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 4 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 0.81.1. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 1 record names netbird with nothing tying it to this repository (CVE-2025-10678).
| 2026-09-01: GHSA-28q5-j9qm-gx35 (moderate), fixed in 0.76.1: Arbitrary Root File Read via Unauthenticated NetBird Daemon Socket |
| 2026-09-01: GHSA-xmg2-v32j-x2hf (high), fixed in 0.74.7: [H28] SSH config Match line injection via peer FQDN / hostname |
| 2026-09-01: GHSA-jxxc-7jxf-v8hm (high), fixed in 0.74.4: SSH server reaches vulnerable x/crypto/ssh paths fixed in 0.52.0 |
| 2026-09-01: GHSA-4g2w-p87c-hxch (high), fixed in 0.49.0: Local Privilege Escalation in Netbird from v0.23.0 to v0.48.0 via MSI Repair Execution |
| 2026-08-31: GHSA-v5w2-pqxj-6r94 (moderate), fixed in 0.75.0: [H16] Relay server gob-decoded unauthenticated Hello handshake bytes before verifying the HMAC signature |
Observability & Operations
strongNo error reporter is wired in
adequateNothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.
| no error reporter initialised |
Fit with the Acquirer
not assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on netbirdio/netbird: every dimension, the questions for the room, and the audit log.
Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.