github dedicatedcode/reitti v5.12.0

2 hours ago

Reitti v5.12.0 Release Notes

Hey everyone, Daniel here!

This release came together faster than planned. I had intended to hold these changes for a later date, but two vulnerabilities disclosed this week, NGINX2Root and Java4Shell, made a quick release the right call. Alongside the security fixes, there are a few useful improvements that were ready to go.

Security: NGINX2Root and Java4Shell

Two separate issues needed attention:

NGINX2Root is a set of five critical memory-corruption vulnerabilities in nginx (CVE-2026-123007 among them) that can allow remote code execution. nginx is used in our reitti-tile-cache image, so I have upgraded it to a fixed release. If you run the tile cache, please pull the new image and restart the container, since a configuration reload alone will not replace the running nginx binary.

Java4Shell (CVE-2026-114938) is a flaw in the HotSpot JVM's Base64 decoder. Reitti's main image runs on Java, but there is no patched base image available for me to use yet. Until one is released, I have added the recommended mitigation by starting the JVM with:

-XX:-UseBASE64Intrinsics

That disables the optimized decoder where the bug lives and falls back to the standard one. This is a temporary measure, not the final fix. As soon as the base image is updated with a patched Java runtime, I will release a new version of Reitti that includes it and remove the flag again.

this-is-fine


⚠️ Important Upgrade Notice

Please be patient during startup after upgrading!
Because this release removes persisted synthetic points from the database (#1403), the database migration will delete a large number of historical rows (potentially several gigabytes of data depending on your history). On my instance, this took roughly 2 minutes. Do not interrupt the container while the migration is running.

What's Changed

Drop Synthetic Point Storage

Reitti generates synthetic points between your tracked GPS points when they arrive too sparsely, giving the visit-detection algorithm something to work with in low-power modes. Until now those points were written to the database and never read again. They are now generated in memory while streaming, so the synthetic column and its index are gone and the historical rows have been deleted.

The savings are substantial. On my dataset:

  • Database size dropped from 4,864 MB to 2,155 MB (about 56% smaller).
  • The raw_location_points table shrank by 75%, and the retained indexes by 78%.
  • 7.3 million rows were removed from raw_location_points (from 10.45 million down to 3.15 million).
  • The detection stream is roughly 5 to 8 times faster, with the end-to-end detection job running 3.4 to 4.3 times faster over a full month.

One important note: the upgrade can take a few minutes, because it deletes several gigabytes of row data. On my machine it took about two minutes. That is a one-time cost.

GeoJSON Export Fix

The GeoJSON export endpoint had stopped returning any points. When the devices feature was introduced, I missed updating this endpoint, so it kept searching for GPS points with no device assigned, and those no longer exist. It now respects device-token-user authentication and exports the correct points again.

New timestampMs Field on the Latest Location Endpoint

If you use the latest-location endpoint for monitoring, it now includes an additional element:

"measurements": {
  "timestampMs": 1793950958716,
  "ageMs": 951906899
}

This gives you the timestamp and age of the last received GPS point directly, so you can build monitoring without having to parse the date string.

Removed Old Segmented API Responses

I removed a large amount of code left over from the days when paths were drawn with Leaflet.js. Related to that, the map previews in Visit Sensitivity and the memories overview now use MapLibre.

Clearer Transportation Mode Pills

When you selected a trip on the map, the transportation mode pills were still shown for every other trip as well. Reitti now hides those pills on unselected trips, so it is much clearer where and when a mode was changed.

Mobile Fixes for Notifications and Coverage

The new-version notification dialog was effectively unusable on mobile because it was nested inside the navigation. That is fixed now, and I also improved the coverage and discovery pages to work better on smaller screens.

Upgrading

Pull the latest image and recreate the container. There is no manual database migration, though allow a couple of minutes for the synthetic-point cleanup described above.

Full Changelog: v5.11.0...v5.12.0

Links & Community

If you want to support development financially, you can find me on Patreon and Ko-fi.

Thanks for your patience with the quick turnaround. Happy tracking!

— Daniel

Don't miss a new reitti release

NewReleases is sending notifications on new releases.