Empty default secret is accepted as valid — every request is authorized when the secret is unset
CVE-2026-48814 is an authentication bypass (CWE-287) rooted in an insecure default (CWE-1188) in Network AI. The product ships with an empty default secret, and the authorization routine treats that empty value as a legitimate secret. When an operator has not set one, the credential check succeeds for everyone — every request is authorized.
The authorization gate compares a caller-supplied value against the configured secret. The configured secret defaults to an empty string, and the comparison does not special-case "unset":
The dangerous property is that the vulnerable state is the default state. A fresh deployment is exposed until and unless the operator notices and sets a secret — the system does not force that step.
Full authentication bypass on any deployment left at the default. An unauthenticated attacker can issue authorized requests against the protected surface and exercise whatever the authorized role permits. Because no misconfiguration is required — only the absence of configuration — exposure across real-world installs is likely broad.
Upgrade to the fixed release named in the advisory, which fails closed: an empty or unset secret is rejected rather than accepted. Operationally:
Reported by Kai Aizen (SnailSploit). Coordinated with the Network AI maintainers via GitHub Security Advisory GHSA-r78r-rwrf-rjwp. See the advisory for affected and fixed version details.
An authentication bypass (CWE-287, insecure default CWE-1188) in Network AI. The product ships with an empty default secret, and the authorization check treats the empty value as valid, so every request is authorized when no secret is set. Tracked as GHSA-r78r-rwrf-rjwp.
You are affected if you run Network AI without explicitly configuring an authentication secret, leaving it at the empty default. See GHSA-r78r-rwrf-rjwp for the affected and fixed version range.
Upgrade to the fixed release, which fails closed by rejecting an empty or unset secret. Immediately set a strong non-empty secret on every deployment, treat an unset secret as a hard startup error, and review logs for requests authorized during the empty-secret window.
Full authentication bypass on any deployment left at the default. An unauthenticated attacker can issue authorized requests with whatever the authorized role permits. The insecure state is the default state, so exposure is likely broad.
The GitHub Security Advisory GHSA-r78r-rwrf-rjwp, the MITRE CVE record for CVE-2026-48814, and the NVD detail page once published.