dbcve.org
GitLabApplication

CVE-2025-1198

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-13
Fix available
A fix is available. Upgrade to 17.6.5 / 17.7.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue discovered in GitLab CE/EE affecting all versions from 16.11 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2 meant that long-lived connections in ActionCable potentially allowed revoked Personal Access Tokens access to streaming results.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

GitLab's ActionCable WebSocket implementation does not re-validate Personal Access Tokens on ongoing streaming connections. When a PAT is revoked after a WebSocket connection is established, the long-lived connection continues to receive streaming data using the now-revoked token, allowing unauthorized access to streaming results.

MitigationUpgrade GitLab to version 17.6.5, 17.7.4, 17.8.2 or later to patch the token re-validation issue in ActionCable connections.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 16.11.0, < 17.6.5>= 17.7.0, < 17.7.4>= 17.8.0, < 17.8.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the version file at `/opt/gitlab/version` (Omnibus) or `git --version` for source installations
    Affected if The version falls within one of these ranges: 16.11.0 to 17.6.4, 17.7.0 to 17.7.3, or 17.8.0 to 17.8.1
  2. Verify ActionCable WebSocket is enabled
    Check the GitLab Rails configuration: grep -i 'actioncable' /etc/gitlab/gitlab.rb for Omnibus, or look for `config.action_cable` in gitlab.yml for source installations. ActionCable is enabled by default in affected versions.
    Affected if ActionCable is enabled (default state) and the GitLab version is affected
  3. Confirm PAT authentication is in use
    Review active Personal Access Tokens: Navigate to User Settings > Access Tokens in the GitLab UI, or run `sudo gitlab-rails console` then `User.with_personal_access_tokens.exists?` to check if any PATs exist
    Affected if Any Personal Access Tokens exist or have existed in the system, as revoked tokens could still be active on open WebSocket connections

You are affected if your GitLab version is 16.11.0-17.6.4, 17.7.0-17.7.3, or 17.8.0-17.8.1 AND ActionCable WebSocket connections are enabled AND users employ Personal Access Tokens for authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 17.6.5 / 17.7.4 / 17.8.2 or later
Fixed in 17.6.517.7.417.8.2
Interim mitigation

Upgrade GitLab to version 17.6.5, 17.7.4, 17.8.2 or later to patch the token re-validation issue in ActionCable connections.

Recommended fix High confidence

17.8.2 (or latest 17.8.x stable)

  1. Identify your current GitLab version using the GitLab Rails console (`gitlab-rake gitlab:version`) or the admin area
  2. Determine which release branch you need to upgrade to based on your current version (17.6.x, 17.7.x, or 17.8.x)
  3. Back up your GitLab instance database and repositories
  4. Follow the official GitLab upgrade documentation for your installation method (package, source, or Docker)
  5. Upgrade to GitLab 17.8.2 (or the latest 17.8.x stable release) for 17.8.x users, 17.7.4 for 17.7.x users, or 17.6.5 for 17.6.x users
  6. After upgrade, verify the instance is functioning correctly
  7. Confirm the Personal Access Token revocation now properly terminates ActionCable sessions
Caveat Minor version upgrades typically have minimal breaking changes; review GitLab release notes for any deprecation notices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1198 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1198 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data