Read 2026-11-03
fabiolb/fabio: technical due diligence, read from its repository
What Borehole read in fabiolb/fabio's code and history at 09108b4: 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 | adequate |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | strong |
| Security & Reliability Posture | strong |
| Observability & Operations | strong |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
adequate1 base image floats: no version, or `latest`
adequate1 of 2 `FROM` lines in product Dockerfiles name an image without a version, or with `latest`. Each build pulls whatever the registry serves that day, so the image that ships can change without a commit, and last month's build cannot be reproduced. Pin a version, or a digest.
Dockerfile:1 — base image without a version |
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
strongNo finding.
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate7 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. 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.
.github/workflows/build.yml:15 — action pinned by tag |
.github/workflows/build.yml:25 — action pinned by tag |
1 locked dependency has published vulnerabilities
adequate1 of 88 locked dependencies match 1 published advisories in OSV. 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.
go.mod — github.com/osrg/gobgp/v4 v4.8.0: GO-2026-4736 (unrated) |
6 advisories against this project in the last 24 months, 5 high or critical
adequateThe newest was published on 2026-09-09. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 1 record names fabio with nothing tying it to this repository (CVE-2025-23652).
| 2026-09-09: GHSA-h66f-g4vc-vj55 (high), fixed in 1.8.0: Unauthenticated Runtime Configuration Disclosure via Admin API `/api/config` in fabio |
| 2026-09-09: GHSA-m4gq-923h-4w8r (critical), fixed in 1.8.0: Default Unauthenticated Admin Write API Enables Routing Takeover |
| 2026-09-09: GHSA-247f-2cq2-v793 (high), fixed in 1.8.0: fabio: setting `proxy.header.clientip` to `X-Real-Ip` silently makes the client-IP header attacker-controlled |
| 2026-08-09: GHSA-4hrh-34w3-5ww8 (critical), fixed in 1.7.3: Route selection uses the raw un-normalized path |
| 2026-07-03: GHSA-fq95-v8xc-jm3v (moderate), fixed in 1.7.2: Fabio - Incomplete fix for CVE-2025-48865: operator-configured trust headers (clientip/tls/requestid) still strippable via the Connection header |
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 fabiolb/fabio: 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.