JC_

September 12, 2026

Reaching 19.2.4: The Milestone

Gitlab
DevOps
Postgresql
Site Reliability
Software Engineering

Live Wire: A Solo GitLab Upgrade Log — Ten mandatory stations after a CVSS 9.4 vulnerability announcement, the version number that started this whole series is finally the version actually running.

The version this series opened with as a target is now the version actually running

This is Part 13 of "Live Wire: A Solo GitLab Upgrade Log" Previous: Station 7–8: The Backup That Looked Broken | Series overview: Live Wire: A Solo GitLab Upgrade Log — Series Overview | Next: Two Thousand Stalled Jobs

TL;DR

This series opened with a CVSS 9.4 vulnerability forcing an upgrade across a mandatory version path, with no test environment to rehearse any of it. Ten stations later, the instance is running 19.2.4 — the exact version that patches both CVEs this whole project was triggered by. This station itself was uneventful, the second clean landing after Station 9. A fourth data point confirmed the backup-duration trend already tracked across the series, and a small cross-verification habit caught an SSH display quirk before it could cause an unnecessary delay. The CVE line is closed. One station remains, and it’s a different kind of problem entirely.

Back to Where This Started

This series opened with a number: CVSS 9.4, an unauthenticated GraphQL code-injection vulnerability, alongside a lower-severity CSRF issue riding along with it. Ten mandatory stations stood between that announcement and a fix, with no staging environment anywhere in the process. Everything since has been about getting from there to here.

The Milestone, in One Sentence

Confirm the version number directly rather than assuming success from a smooth-looking process, and treat this as the end of one storyline — the CVE fix — not the end of the whole project.

Quick Start: Confirming the Version, Not Assuming It

curl -sk "https://<host>/api/v4/version" --header "PRIVATE-TOKEN: ${GITLAB_ADMIN_TOKEN}"
{"version":"19.2.4","revision":"06e8d813296","kas":{...},"enterprise":false}

19.2.4 — the exact version GitLab’s own advisory named as the fix for CVE-2026–19478 (CVSS 9.4, GraphQL code injection) and CVE-2026–19650 (CSRF). The core objective this entire project was triggered by is now confirmed, directly, rather than assumed from an upgrade script exiting cleanly.

Ten stations, start to finish — and a trend line that’s now four points long

A Small Habit That Paid Off: Verify Independently, Don’t Wait Blindly

During this station’s execution, the Rails console command to raise migration parallelism appeared to time out over SSH, with the connection display suggesting it had been backgrounded unexpectedly. Rather than waiting on that same connection to resolve, a direct SQL check confirmed the real state:

SELECT value FROM application_settings
WHERE name = 'database_max_running_batched_background_migrations';
-- 6

The setting had, in fact, updated correctly — the apparent timeout was purely a display quirk in how that SSH session reported its own status, not a real failure. The lesson generalizes past this one command: when an operation’s own output looks stuck or ambiguous, an independent query through a different channel is usually faster and more reliable than waiting on the original command to resolve itself.

The Backup Trend: A Fourth Point Makes It a Real Pattern

Date       Before          Duration     Final Size
09-01      Station 6        ~2h          39G
09-03      Station 7-8      ~3h05m       39G
09-09      Station 10       ~2h06m       38G

The judgment principle from two stations back — trust the process, not just the file — verified correctly a fourth time: at 11:05, the backup file already read 37GB, but pgrep -af "rake gitlab:backup:create|tar --exclude" still returned a live process, which didn't actually finish until 11:06. Checking the file alone would have suggested it was already done a full minute early. Four data points across four different stations turns "data volume seems to be growing" from a single station's observation into a confirmed, ongoing trend.

The Path, Looking Back

Ten mandatory stations, start to finish: 17.4.2 → 17.5.5 → 17.8.7 → 17.11.7 → (PostgreSQL 15→16) → 18.2.8 → 18.5.7 → 18.8.11 → 18.11.11 → (PostgreSQL 16→17, Redis 6.2→7.2) → 19.2.4. Worth being honest about one detail: the original plan named eight version stops. Two of those stops turned out to each fold in a second, distinct kind of station — a database engine swap layered underneath the version bump — bringing the real total to ten. The CVSS 9.4 vulnerability that started all of this is now patched.

Under the Hood

+---------------------------+------------------------------------------------+----------------------------------------------------+
| Item                        | What I Confirmed                                 | Why It Mattered                                       |
+---------------------------+------------------------------------------------+----------------------------------------------------+
| Version and CVE fix          | Queried the API directly for the running          | Confirmed the core objective, not just that the       |
|                             | version, not just trusted a clean upgrade exit     | upgrade script exited without error                    |
+---------------------------+------------------------------------------------+----------------------------------------------------+
| Ambiguous command state      | Cross-verified via direct SQL instead of          | Avoided an unnecessary delay chasing a display          |
|                             | waiting on a stuck-looking SSH session             | quirk that wasn't a real failure                         |
+---------------------------+------------------------------------------------+----------------------------------------------------+
| Backup duration trend         | Logged a fourth data point across a fourth        | Turned a single station's observation into a           |
|                             | station                                            | confirmed, ongoing pattern                                |
+---------------------------+------------------------------------------------+----------------------------------------------------+

What Actually Worked

Confirming the version directly, rather than trusting that a clean-looking upgrade meant the goal was met, is a small habit that matters most exactly on the station where it would be easiest to skip. The independent cross-check during the SSH timeout is the same instinct in a different shape: when something looks stuck, verify through a different channel before assuming failure or waiting indefinitely.

Where This Still Falls Short

This closes the CVE-driven storyline this series opened with — it does not close the project. One station remains, and it’s a different kind of problem than any of the ten before it: the Container Registry itself, carrying a protocol-level mismatch this series met early on and never fully resolved. That fix is deliberately scheduled for after a period of observing 19.2.4 running stable, not rushed in immediately just because the CVE line is finished.

If you’ve ever hit a milestone that felt like the end of a project, only to realize it was actually the end of just one storyline inside it — what did the second half look like?

This is Part 13 of "Live Wire: A Solo GitLab Upgrade Log" Previous: Station 7–8: The Backup That Looked Broken | Series overview: Live Wire: A Solo GitLab Upgrade Log — Series Overview | Next: Two Thousand Stalled Jobs