Skip to content
VulniPulse
Sign in
Highest advisory severityMedium 1 vendor · 1 advisory

CVE-2026-4398

CVE-2026-4398: 1 tracked advisory record across GitLab. Compare vendor sources and published fix guidance.

Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.

NVD detail CVE.org

Vendor advisory comparison

GitLab

1 advisory
  • Advisory severityMedium5.4

    Medium [CVE-2026-4398] Authorization Bypass Through User-Controlled Key in GitLab

    CVE-2026-4398Source published Source updated

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have assigned compliance frameworks from namespaces they were not authorized to access to their own project, due to missing namespace validation on self-managed instances.

    Affected products in this advisory
    • GitLab
    Source-reported affected versions
    • GitLab 18.3 before 19.1.7
    • GitLab 19.2 before 19.2.5
    • GitLab 19.3 before 19.3.1
    Source-reported fixed versions
    • 19.1.7
    • 19.2.5
    • 19.3.1
    Mitigation guidance
    No mitigation guidance extracted; consult the source.
    Full advisory and evidenceOpen source bulletin

Android app · Google Play

Monitor future GitLab CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features