Vulnerabilities

Vulnerability · CVE-2025-9957

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could ha

Published Apr 22, 2026 · catalog updated Oct 14, 2026 · GitLab has remediated an

Check if you run it

No confirmed exploitation is on record for CVE-2025-9957. EPSS is 0.38%. Act only if a listed version of GitLab has remediated an is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (GitLab has remediated an).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low2.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.38%
Remediation
Advisory link
Affected products
cpe gitlab/gitlab

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user with project owner permissions to bypass group fork prevention settings due to improper authorization checks.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe gitlab/gitlab18.11.0

How to fix CVE-2025-9957

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-9957. EPSS is 0.38%. Act only if a listed version of GitLab has remediated an is installed.

Which versions are affected?

Compare what you have installed with 18.11.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-863: Incorrect Authorization. EPSS 0.38%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 22, 2026 · NIST NVD

    Detected

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user with project owner permissions to bypass group fork prevention settings due to improper authorization checks.

  2. Oct 14, 2026 · NIST NVD

    Updated

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user with project owner permissions to bypass group fork prevention settings due to improper authorization checks.

Sources

  • CVE.orgVulnerability recordCVE-2025-9957

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-9957

    30-day exploitation probability 0.4%

    first.org
  • GitLab Security ReleasesVendor advisoryCVE-2025-9957

    On April 22, 2026, we released versions 18.11.1, 18.10.4, 18.9.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of thes

    docs.gitlab.com
  • NIST NVDVulnerability recordCVE-2025-9957

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user with project owner permissions to bypass group fork prevention sett

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.