LiveActive security incident?Get immediate response
CVE Record

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

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.3 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2 that could have allowed an unauthenticated user to create a denial of service condition by sending repeated malformed SSH authentication requests.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-1102 is a GitLab CE/EE denial-of-service issue. An unauthenticated attacker could send repeated malformed SSH authentication requests and reduce service availability. It does not indicate data theft or code execution. Business urgency is highest for internet-exposed GitLab SSH services on affected versions.

Executive priority

Prioritize patching exposed self-managed GitLab instances in the next regular security maintenance window. Escalate sooner if GitLab availability is business-critical or SSH access is internet-facing. Current evidence supports moderate urgency, not emergency response.

Technical view

GitLab remediated CWE-770, allocation of resources without limits or throttling, in CE/EE versions from 12.3 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, availability impact low.

Likely exposure

Organizations running affected GitLab CE/EE versions with GitLab SSH authentication reachable from untrusted networks are the most likely exposed. Hosted or managed environments should confirm their provider’s patch status. Systems already on 18.6.4, 18.7.2, 18.8.2, or later fixed releases are not indicated as affected.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not marked KEV. The issue is unauthenticated and network reachable, but the documented impact is denial of service with low availability impact, not confidentiality or integrity compromise.

Researcher notes

The public record identifies malformed SSH authentication requests as the trigger but does not provide detailed internals in the source bundle. GitLab issue access may require permissions. Avoid assuming exploit availability, broader products, or impacts beyond availability without additional vendor-confirmed evidence.

Mitigation direction

  • Upgrade GitLab CE/EE to 18.6.4, 18.7.2, 18.8.2, or a later fixed release.
  • Review GitLab’s patch release advisory for any environment-specific guidance.
  • Restrict GitLab SSH exposure to trusted networks where operationally feasible.
  • Monitor GitLab SSH authentication volume and availability until patched.

Validation and detection

  • Inventory GitLab CE/EE instances and record exact versions.
  • Confirm whether versions fall in 12.3 before 18.6.4, 18.7 before 18.7.2, or 18.8 before 18.8.2.
  • Verify SSH authentication endpoints are not unnecessarily exposed to untrusted networks.
  • Confirm upgrade completion by checking the installed GitLab version after maintenance.
Prepared
Confidence
high
Sources
4

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-1102 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
3Source 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-1102Attack 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
GitLabGitLab12.3, 18.7, 18.8unaffected
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.