LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1725: Allocation of Resources Without Limits or Throttling in GitLab

GitLab has remediated an issue in GitLab CE/EE affecting versions from 18.9 before 18.9.1 that could have under certain conditions, allowed an unauthenticated user to cause denial of service by sending specially crafted requests to a CI jobs API endpoint.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1725 is a GitLab denial-of-service issue. An unauthenticated attacker could send specially crafted requests to a CI jobs API endpoint and reduce availability under certain conditions. It affects GitLab CE/EE 18.9 versions before 18.9.1. GitLab says the issue is remediated in 18.9.1.

Executive priority

Treat as a timely patching item, not an emergency absent evidence of active exploitation. Prioritize if GitLab is internet-facing or business-critical for software delivery, because disruption could affect CI/CD operations.

Technical view

The flaw is CWE-770, allocation of resources without limits or throttling. The CVSS 3.1 score is 5.3: network exploitable, low complexity, no privileges, no user interaction, with low availability impact only. The affected range is GitLab CE/EE from 18.9 before 18.9.1.

Likely exposure

Exposure is likely limited to self-managed GitLab CE/EE instances running 18.9 before 18.9.1, especially where the GitLab web/API interface is reachable by unauthenticated users. The sources do not state impact to other versions or products.

Exploitation context

The CVE states unauthenticated specially crafted requests can cause denial of service under certain conditions. CISA KEV is false in the provided data, and no cited source confirms active exploitation in the wild.

Researcher notes

Public technical detail is limited; the GitLab issue and HackerOne report are marked permissions-required in the source bundle. Avoid assuming request structure or exploit mechanics beyond the CVE description. Focus validation on affected version, exposure, and availability symptoms.

Mitigation direction

  • Upgrade affected GitLab CE/EE 18.9 deployments to 18.9.1 or later vendor-fixed release.
  • Review GitLab’s 18.9.1 patch release notes and any updated vendor guidance.
  • Prioritize internet-facing GitLab instances before internal-only instances.

Validation and detection

  • Inventory GitLab CE/EE versions and identify any 18.9 builds before 18.9.1.
  • Confirm whether the GitLab web/API interface is reachable by unauthenticated users.
  • Review availability monitoring for abnormal errors or resource spikes around CI jobs API traffic.
  • Verify the instance reports version 18.9.1 or a later fixed release after remediation.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-1725 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-1725Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitLabGitLab18.9unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.