WAMF v0.4.3¶
Released 28 October 2026. Latest stable release. Published GitHub release.
The release tag points to eb6d298357fd481f4c82257adc41c211d6e6fa1c,
incorporating PR #4's security fixes and PR #5's release preparation.
Python 3.11, the CPU TFLite classifier, application dependency pins and AMD64
deployment scope are retained. Kingfisher v0.5.0 remains under development.
Changes¶
- Embedded navigation parses destinations with the browser URL API and permits HTTP/HTTPS only. Unsafe or malformed destinations are removed while preserving internal links, fragments, external HTTP/HTTPS links and Home Assistant embeds.
- Security regression coverage includes URL formats, daily-summary/date navigation, login redirects, browser history and embed parameters.
- A pinned Chromium headless shell improves CI browser-test reliability.
- Test HTML parsing uses the standard-library HTMLParser instead of regex.
Installation and upgrade¶
Use ghcr.io/wamf-project/wamf:0.4.3 for the published container.
The publishing workflow does not update latest.
Follow Docker deployment or upgrading v0.4.2 to v0.4.3. No configuration, database or media migration is introduced. Stop cleanly, back up configuration/database/media together, retain the old image, and preserve mounts, ports, credentials and session secrets. For rollback, stop the upgraded container and restore the previous image and corresponding backup if needed; never run both versions as database writers.
Security and validation scope¶
Protobuf 3.20.3 retains CVE-2025-4565 and CVE-2026-0994. Their alerts were dismissed as accepted risks, not patched; TFLite Support 0.4.4's protobuf constraint prevents an isolated compatible upgrade. Packaging-tool and setup-token acceptance conditions, root-container/Flask limitations and Debian/native-library risks remain. Read Security.
The published release records 1,860 tests passed with no skips, successful release PR/post-merge checks, and an isolated Linux/AMD64 build and smoke test. Version reporting, web/health responses and database/archive storage checks passed. The isolated test did not exercise live Frigate/MQTT connectivity or establish a separate comprehensive image-security scan.
The publishing workflow succeeded, including its configured CRITICAL-only Trivy gate with unfixed findings excluded. This does not establish that lower-severity or unfixed vulnerabilities are absent. Manual workflow dispatch remains pinned to historical v0.4.2 recovery source; it must not be used to publish v0.4.3.