Security fixes target the current main branch and the latest tagged minor release. Older release lines receive fixes only when explicitly announced.

Please report security issues privately to Sonic Field Labs before public disclosure. Include the affected commit, local configuration, reproduction steps, and whether raw audio or private listening traces can be exposed.

oida binds to 127.0.0.1 by default. Wildcard or LAN binds are refused unless OIDA_AUTH_TOKEN (legacy HMM_AUTH_TOKEN/AEAR_AUTH_TOKEN) is set, and token-protected clients must send Authorization: Bearer <token>. Loopback requests are additionally guarded by Host/Origin checks against DNS rebinding and cross-origin calls.

Audio-analysis routes intentionally accept an operator-selected local file path; these are desktop/localhost file references, not web-root-relative tenant paths. The daemon verifies that each reference resolves to an existing regular file before analysis. Writes remain confined to configured Oída data directories, and names used inside those directories are normalized. The Sonic Field reveal route separately requires the resolved target to remain inside its configured Sonic Field root.

MOSS-Audio Hugging Face model lookup is disabled by default. Download weights into weights/ or set OIDA_ALLOW_HF_HUB=1 (legacy HMM_/AEAR_) explicitly. HF_HUB_OFFLINE=1 always disables hub lookup.

The optional embedded MOSS-Audio runtime uses the locally validated Torch and Torchaudio 2.10.0 pair. Upstream MOSS-Audio currently pins 2.9.1, while moving Oída to 2.13 requires a new TorchCodec, Transformers, MPS, and model-inference validation cycle.

Two findings remain accepted temporarily for this optional local runtime:

The exception ends immediately if Oída begins calling either API, if its model trust boundary changes, or when a compatible runtime is validated. The all-extras CI audit ignores only these identifiers and fails on any new finding.