|
| 1 | +# Security Policy |
| 2 | + |
| 3 | +## Supported Versions |
| 4 | + |
| 5 | +Security fixes target the current `main` branch and the latest tagged minor |
| 6 | +release. Older release lines receive fixes only when explicitly announced. |
| 7 | + |
| 8 | +## Reporting a Vulnerability |
| 9 | + |
| 10 | +Please report security issues privately to Sonic Field Labs before public |
| 11 | +disclosure. Include the affected commit, local configuration, reproduction |
| 12 | +steps, and whether generated audio, model files, or listening records can be |
| 13 | +exposed. |
| 14 | + |
| 15 | +## Local-First Boundary |
| 16 | + |
| 17 | +GERM is a local sidecar. Its optional Python provider loads model and LoRA files |
| 18 | +only through configured model roots. Treat every model artifact as executable |
| 19 | +input: use the official Safetensors releases, verify provenance, and do not load |
| 20 | +untrusted pickle-based checkpoints. |
| 21 | + |
| 22 | +## Temporary Upstream PyTorch Exceptions |
| 23 | + |
| 24 | +Stable Audio 3 still pins PyTorch 2.7.1 upstream. GERM overrides that constraint |
| 25 | +with Torch and Torchaudio 2.10.0, validated on macOS by the full GERM suite and |
| 26 | +the upstream Stable Audio CLI suite. This removes every currently fixable |
| 27 | +finding below PyTorch 2.10. |
| 28 | + |
| 29 | +Two findings remain accepted temporarily for the optional local provider: |
| 30 | + |
| 31 | +| Advisory | Affected API | GERM exposure | Review deadline | |
| 32 | +| --- | --- | --- | --- | |
| 33 | +| `PYSEC-2026-139` / `CVE-2026-4538` | `torch.export.load` of `.pt2` artifacts | GERM does not call this API or accept `.pt2` model artifacts. No patched PyTorch release is currently published. | 2026-09-02 | |
| 34 | +| `GHSA-rrmf-rvhw-rf47` / `CVE-2025-3000` | TorchScript compilation | GERM does not compile user-supplied TorchScript. Moving to PyTorch 2.13 requires upstream Stable Audio and accelerator validation. | 2026-09-02 | |
| 35 | + |
| 36 | +The exception ends immediately if GERM begins calling either API, if its model |
| 37 | +trust boundary changes, or when a compatible upstream runtime is available. |
| 38 | +The all-extras CI audit ignores only these identifiers and fails on any new |
| 39 | +finding. |
0 commit comments