What is CVE-2026-7427?

CVE-2026-7427 is Allocation of Resources Without Limits or Throttling in GitLab. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-770 CWE-770.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-7427. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-7427 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

5 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-7427 using CVSS 5.3, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumRemote Code Execpublic exploit

CVE-2026-7427

CVE-2026-7427 — Allocation of Resources Without Limits or Throttling in GitLab

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to improper input validation.

Published Aug 12, 2026Updated Aug 12, 2026Sources: NVD, GitLab (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

GitLab

3 products listed

CVSS base

5.3

medium

Remediation

The vendor's own words where we have them.

Upgrade to versions 19.0.6, 19.1.4, 19.2.2 or above.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
GitLab	GitLab	18.5 to < 19.0.6	Vulnerable
GitLab	GitLab	19.1 to < 19.1.4	Vulnerable
GitLab	GitLab	19.2 to < 19.2.2	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

None

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
5.3	CVSS 3.1	medium	3.9	1.4	gitlab.com (CNA), GitLab (CNA), GHSA

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-770 · Allocation of Resources Without Limits or Throttling

DoS: Resource Consumption (CPU)
DoS: Resource Consumption (Memory)
DoS: Resource Consumption (Other)

Mitigation: Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.

Weakness & attack patterns

CWE-770

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-528 · XML FloodCAPEC-230 · XML Nested PayloadsCAPEC-496 · ICMP FragmentationCAPEC-493 · SOAP Array BlowupCAPEC-487 · ICMP FloodCAPEC-147 · XML Ping of the DeathCAPEC-495 · UDP FragmentationCAPEC-486 · UDP FloodCAPEC-489 · SSL FloodCAPEC-469 · HTTP DoSCAPEC-231 · Oversized Serialized Data PayloadsCAPEC-494 · TCP Fragmentation

T1498.001Network Denial of Service: Direct Network Flood
T1499Endpoint Denial of Service
T1499.003Endpoint Denial of Service: Application Exhaustion Flood

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /EE.
Prioritize edge telemetry for network-reachable GitLab.
Monitor for scanner or exploit-pattern traffic after 5 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 5.3 (AV:N)
Aug 12, 2026 · NVD
Initial · CVE published
Aug 12, 2026 · NVD
Added · GHSA-mrwr-f6g8-28q2 published (medium)
Aug 12, 2026 · GitHub Security Advisory

Source activity

Readings a source repeats on a schedule, counted rather than listed.

2×ModifiedAug 12, 2026 · SOCRadar CTI

References

5 on the record

docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-2-released/
Vendor Advisory, NIST
gitlab.com/gitlab-org/gitlab/-/work_items/598561
Vendor Advisory, NIST
hackerone.com/reports/3638799
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-7427
NVD
github.com/advisories/GHSA-mrwr-f6g8-28q2
Exploit, Third Party Advisory

Elsewhere on this site

GitLabevery CVE for this vendor
Remote Code Execsame class
CWE-770other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-7427 is Allocation of Resources Without Limits or Throttling in GitLab, a medium vulnerability affecting GitLab from GitLab. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-7427. Public exploit evidence is: 5 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 5.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.