Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker could, under certain conditions, alter or delete public GitLab projects and user data. The impact is primarily severe data-integrity and availability loss, with some confidentiality impact. GitLab has released corrected versions, so affected deployments should be upgraded urgently.
Executive priority
Treat this as an immediate patching and integrity-review priority. Unauthenticated remote modification or deletion can disrupt development, damage trusted source repositories, and require recovery from backups. Highest urgency applies to remotely reachable affected instances with valuable public projects. Active exploitation is not established by the supplied evidence.
Technical view
CVE-2026-19478 is a CWE-94 code-injection flaw involving a GraphQL directive in GitLab CE/EE. It affects 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. CVSS 3.1 is 9.4: network-accessible, low complexity, unauthenticated, and requiring no user interaction.
Likely exposure
Potentially exposed organizations operate GitLab CE/EE within the specified version ranges, particularly where GitLab is remotely reachable and contains public projects. The bundle does not establish whether every deployment configuration meets the unspecified conditions required for exploitation.
Exploitation context
The flaw requires no authentication or user interaction and can reportedly affect public projects and user data remotely. A technical HackerOne report is referenced, but the source bundle provides no evidence of active exploitation in the wild, and the CVE is not identified as being in KEV.
Researcher notes
The stated weakness is CWE-94 through a GraphQL directive, with high integrity and availability impact. The phrase “under certain conditions” is not defined in the supplied description, so configuration-level exploitability cannot be determined from this bundle alone. The HackerOne report and GitLab work item are the appropriate sources for deeper technical conditions without assuming universal exposure.
Mitigation direction
- Upgrade affected branches to 18.11.11, 19.0.8, 19.1.6, 19.2.4, or a later applicable release.
- Prioritize internet-reachable instances and deployments hosting important public projects or user data.
- Preserve backups and relevant audit records before remediation and investigation.
- If upgrading is delayed, consult GitLab's patch advisory for vendor-supported temporary guidance.
Validation and detection
- Inventory all GitLab CE/EE deployments and record their complete installed versions.
- Confirm each deployment is outside the affected ranges or successfully upgraded to an applicable corrected version.
- Review audit records for unexpected public-project changes, deletions, and user-data modifications.
- Validate public-project and user-data integrity against trusted backups or authoritative records.
- Check GitLab's advisory and work item for updated indicators, conditions, or remediation guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupCVE-2026-19478 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H3.95.5GitLabVulnerability scoring details
Base CVSS 3.1 score
9.4CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://gitlab.com/gitlab-org/gitlab/-/work_items/611377CVE reference, GitLab
- HackerOne Bug Bounty Report #3926431CVE reference, GitLab · technical-description, exploit
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-4-released/CVE reference, GitLab
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code
Improper Control of Generation of Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.