Skip to content

Open-source gym & body-weight tracker, now in the App Store (iPhone + Apple Watch) and as an Android APK. Plan routines, log workouts, see which muscles are trained, import from Strong/Hevy/FitNotes. Self-host it or use it on the phone alone.

Android backups leave the pairing token out, nginx stops naming its version, changelog

Duarte Santos2da3cb594f3f
diff --git a/CHANGELOG.md b/CHANGELOG.md
index b3ee834f4..d68405236 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,30 @@
# Changelog
+## Unreleased
+
+**Security.** Five private reports, all fixed, plus our own audit. Thanks to Boris Kurktchiev
+for the reports, each with a patch and a test. Self-hosters: please update.
+
+- **A crafted link could send your sign-in to another server** (GHSA-375x-wfvj-jf7q). A link to
+ your own instance with an odd path made the app talk to a host named in that path. It can't
+ leave your instance any more.
+- **Another site could sign you into its account** (GHSA-48ff-v63h-99xr). The passkey sign-in
+ routes now check where a request comes from like every other route, and the API only takes JSON.
+- **Push notifications could be taken over** by someone who knew your device's push address
+ (GHSA-568g-hg5j-h53q). The address now only moves to another account with its own keys.
+- **The Coach's sandbox check was skipped** on the admin's test button, the status card and jobs
+ queued before a provider switch (GHSA-w724-p4hx-jfv9).
+- **One profile could slow the server down for everyone** with a huge queue (GHSA-69j8-85pp-mf8j),
+ or with many accounts and large saved states. The reminder check now reads a state only when a
+ reminder could actually go out.
+- Rest timers and test pushes are limited per account, disabled accounts get no reminders and no
+ Coach reviews, and signing up with someone's e-mail as the name counts against your address
+ like the e-mail field does.
+- A browser's sign-in cookie can no longer be turned into a phone token that renews forever.
+- The Coach forgets a stored API key when its server address moves to another host. Enter it again.
+- Request paths the server would have to tidy up (`..`, backslashes) are refused, nginx stops
+ naming its version, and Android backups no longer include the paired server's sign-in.
+
## v1.4.1 (2026-10-10)
Bug fixes for v1.4.0, mostly the things you told us about on Discord and GitHub.
diff --git a/frontend/android/app/src/main/res/xml/backup_rules.xml b/frontend/android/app/src/main/res/xml/backup_rules.xml
index 3354925d9..14ae9c098 100644
--- a/frontend/android/app/src/main/res/xml/backup_rules.xml
+++ b/frontend/android/app/src/main/res/xml/backup_rules.xml
@@ -4,7 +4,10 @@
(src/lib/media-store-fs.js, Directory.Library, which is the files directory). Auto Backup
skips an app's WHOLE backup once it passes 25 MB, and a few videos would take the state
mirror (opengym-state.json) down with them. A paired phone gets the files back from its
- server; a phone in local mode keeps them in the zip export. -->
+ server; a phone in local mode keeps them in the zip export.
+ The pairing (opengym-remote.json) stays out as well: it holds the session token for the
+ server, and a backup is no place for a credential. A restored phone pairs again. -->
<full-backup-content>
<exclude domain="file" path="opengym-media/" />
+ <exclude domain="file" path="opengym-remote.json" />
</full-backup-content>
diff --git a/frontend/android/app/src/main/res/xml/data_extraction_rules.xml b/frontend/android/app/src/main/res/xml/data_extraction_rules.xml
index 95b0f44ae..a6cd542c2 100644
--- a/frontend/android/app/src/main/res/xml/data_extraction_rules.xml
+++ b/frontend/android/app/src/main/res/xml/data_extraction_rules.xml
@@ -2,9 +2,14 @@
<!-- Android 12 (API 31) and later: the same rule as backup_rules.xml for the cloud backup, where
the 25 MB cap applies. A device-to-device transfer has no such cap, and a phone moved to a
new one should arrive with its photos and videos, so that section is left out: without one,
- a transfer takes everything, as before. -->
+ a transfer takes everything, as before, except the pairing (opengym-remote.json), which holds
+ the session token for the server and stays out of both. A new phone pairs again. -->
<data-extraction-rules>
<cloud-backup>
<exclude domain="file" path="opengym-media/" />
+ <exclude domain="file" path="opengym-remote.json" />
</cloud-backup>
+ <device-transfer>
+ <exclude domain="file" path="opengym-remote.json" />
+ </device-transfer>
</data-extraction-rules>
diff --git a/web/nginx.conf.template b/web/nginx.conf.template
index 696b9c243..f66aee554 100644
--- a/web/nginx.conf.template
+++ b/web/nginx.conf.template
@@ -15,6 +15,8 @@ map $request_uri $api_request_uri {
server {
listen ${NGINX_PORT};
+ # No nginx version in the Server header or on its own error pages.
+ server_tokens off;
root /usr/share/nginx/html;
index index.html;
# Every redirect nginx sends (the unknown-path one below, and /api to /api/) carries a