Unauthenticated service interruption via token decoder
Published Feb 25, 2026 · Updated Feb 25, 2026
Resource exhaustion in GitLab CE/EE 18.9 before 18.9.1 allows remote attackers to interrupt service via CI jobs API requests. GitLab identifies the affected locus as the token decoder, but the public advisory does not disclose which token field or decoding operation consumes resources without an enforced limit. The endpoint is reachable without authentication; the published impact is reduced availability, and no crash, reboot, shutdown, or persistence effect is specified.
Summary
What happened
Resource exhaustion in GitLab CE/EE 18.9 before 18.9.1 allows remote attackers to interrupt service via CI jobs API requests. GitLab identifies the affected locus as the token decoder, but the public advisory does not disclose which token field or decoding operation consumes resources without an enforced limit. The endpoint is reachable without authentication; the published impact is reduced availability, and no crash, reboot, shutdown, or persistence effect is specified.
The record
- CVE
- CVE-2026-1725
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=18.9 <18.9.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo