Retrospective for 2026-06-25, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.
What this advisory changes in your environment
The starting point is CERTFR-2026-AVI-0799, published on 2026-06-25. Its scope includes GitLab Community Edition (CE) et Enterprise Edition (EE). Reported consequences are cross-site scripting (XSS), server-side request forgery (SSRF), security control bypass, loss of confidentiality. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.
This case focuses on GitLab Community Edition (CE) et Enterprise Edition (EE). Locate that edition in live installations, deployment images and actual dependencies, rather than treating every product from GitLab as equivalent.
Products and versions to examine
- Reference
- CERTFR-2026-AVI-0799
- Source first published
- 2026-06-25
- Latest source revision available for this day
- 2026-06-25
- Named components
- GitLab Community Edition (CE) et Enterprise Edition (EE)
- CVE identifiers
- CVE-2026-0934, CVE-2026-11379, CVE-2026-5952, CVE-2026-5796, CVE-2026-10712, CVE-2026-5309, CVE-2026-1606, CVE-2026-10086, CVE-2026-3176, CVE-2026-2238, CVE-2026-12053, CVE-2026-8330, CVE-2026-12635
| Component | Published condition |
|---|---|
| GitLab Community Edition (CE) et Enterprise Edition (EE) | 19.1.x : < 19.1.1 |
| GitLab Community Edition (CE) et Enterprise Edition (EE) | < 18.11.6 |
| GitLab Community Edition (CE) et Enterprise Edition (EE) | 19.0.x : < 19.0.3 |
For GitLab Community Edition (CE) et Enterprise Edition (EE), the published condition is “19.1.x : < 19.1.1”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of GitLab does not close this case.
Mechanism and prerequisites
SSRF abuses requests a server is allowed to make. Inspect outbound destinations, metadata access and service secrets; segmentation can reduce impact without repairing the vulnerable request logic.
The primary record CVE-2026-0934, published by GitLab, covers GitLab. The retained revision is dated 2026-06-25. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-0799.
The published metric for CVE-2026-0934 is CVSS 3.1, 3.8/10. The vector below describes technical prerequisites; it does not measure attack frequency or the likelihood that your deployment is compromised.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
- Attack vector
- network
- Prior privileges
- high
- User interaction
- none
- Complexity
- low
- Weakness
- CWE-863
Choose the appropriate intervention
- Locate GitLab Community Edition (CE) et Enterprise Edition (EE) instances, running releases and service owners. Record condition 19.1.x : < 19.1.1 in the ticket alongside reference CERTFR-2026-AVI-0799.
- Compare the installed branch with the vendor’s GitLab Community Edition (CE) et Enterprise Edition (EE) release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
- After changing GitLab Community Edition (CE) et Enterprise Edition (EE), capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.
Verify the fix in a real workflow
Validation scenario to adapt for GitLab: In a test project using GitLab Community Edition (CE) et Enterprise Edition (EE), rerun a build without production secrets and verify the delivered artifact. Compare runner permissions, actually resolved dependencies and the behaviour of a contributor without an administrative role. This is a proposed defensive check, not a claim that testing was performed against third-party systems.
Limit of case CERTFR-2026-AVI-0799: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.
Questions specific to this case
Which condition should be checked for GitLab Community Edition (CE) et Enterprise Edition (EE)?
Advisory CERTFR-2026-AVI-0799 states: GitLab Community Edition (CE) et Enterprise Edition (EE) — 19.1.x : < 19.1.1. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.
Which prerequisites does record CVE-2026-0934 specify?
For CVE-2026-0934, the published vector is CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N. Verify those conditions on GitLab before applying them to an integration named in CERTFR-2026-AVI-0799.
Sources and related reading
Practical guide : Software supply chain assurance: components to release
Explore the decision addressed in this case
Complete source advisory inventory
The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.
Official source · CERTFR-2026-AVI-0799
Advisory revision : · Checked on :
Affected systems · 3
Original French wording is retained to avoid ambiguous translations of version conditions.
- GitLab Community Edition (CE) et Enterprise Edition (EE) versions 19.1.x antérieures à 19.1.1
- GitLab Community Edition (CE) et Enterprise Edition (EE) versions antérieures à 18.11.6
- GitLab Community Edition (CE) et Enterprise Edition (EE) versions 19.0.x antérieures à 19.0.3