What is CVE-2026-19478?

CVE-2026-19478 is Improper Control of Generation of Code ('Code Injection') in GitLab. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-94 Code Injection.

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?

Exploitation is reported, but no independent confirmation is available in the sources we have. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-19478 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?

12 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-19478 using CVSS 9.4, EPSS 6%, 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.

criticalRemote Code Execpublic exploit

CVE-2026-19478

CVE-2026-19478 — Improper Control of Generation of Code ('Code Injection') in GitLab

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4 that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive.

Published Aug 17, 2026Updated Aug 18, 2026Sources: NVD, GitLab (CNA), GitHub, SOCRadar CTI

Triage

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

Exploitation

Reported

not confirmed by CISA

EPSS

ahead of 93% of scored CVEs

Affects

GitLab

4 products listed

CVSS base

9.4

critical

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade to versions 18.11.11, 19.0.8, 19.1.6, 19.2.4 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.2 to < 18.11.11	Vulnerable
GitLab	GitLab	19.0 to < 19.0.8	Vulnerable
GitLab	GitLab	19.1 to < 19.1.6	Vulnerable
GitLab	GitLab	19.2 to < 19.2.4	Vulnerable

Attack characteristics

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

Availability

High

Confidentiality

Low

Integrity

High

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
9.4	CVSS 3.1	critical	3.9	5.5	gitlab.com (CNA), GitLab (CNA)

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

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-94 · Improper Control of Generation of Code ('Code Injection')

Bypass Protection Mechanism
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands
Hide Activities

Mitigation: Refactor your program so that you do not have to dynamically generate code.

Weakness & attack patterns

CWE-94Code Injection

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

CAPEC-77 · Manipulating User-Controlled VariablesCAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

T1027.006Obfuscated Files or Information: HTML Smuggling
T1027.009Obfuscated Files or Information: Embedded Payloads
T1564.009Hide Artifacts: Resource Forking

Public exploit

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

Repositories

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

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 12 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
Cve is exploited dinosn/gitlab-cve-2026-19478-lab
Aug 23, 2026 · SOCRadar CTI
Cve is exploited n0xdaemon/cve-2026-19478
Aug 21, 2026 · SOCRadar CTI
Added · CVSS 3.1 9.4 (AV:N)
Aug 18, 2026 · NVD
Cve is exploited davkharrr/CVE-2026-19478-PoC
Aug 18, 2026 · SOCRadar CTI
Initial · CVE published
Aug 17, 2026 · NVD

Source activity

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

13×TweetsAug 18, 2026 – Aug 29, 2026 · SOCRadar CTI
9×SvrsAug 18, 2026 – Aug 29, 2026 · SOCRadar CTI
7×Github ReposAug 17, 2026 – Aug 27, 2026 · SOCRadar CTI
3×TelegramAug 19, 2026 – Aug 24, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Aug 18, 2026 · SOCRadar CTI

References

3 on the record

docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-4-released/
Vendor Advisory, NIST
gitlab.com/gitlab-org/gitlab/-/work_items/611377
Vendor Advisory, NIST
hackerone.com/reports/3926431
Vendor Advisory

Coverage

19 stories from the feeds we poll

14 more reports on this CVEShowing 5 of 19 · Vendor research and security press coverageUnlock free

Elsewhere on this site

GitLabevery CVE for this vendor
Remote Code Execsame class
CWE-94other 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-19478 is Improper Control of Generation of Code ('Code Injection') in GitLab, a critical vulnerability affecting GitLab from GitLab. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 12 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 9.4 describes technical severity, while EPSS 6% 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.