PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-9807 GitLab CVE debrief

GitLab has remediated an authorization enforcement flaw in GitLab CE/EE where blocked Project Access Tokens could, under certain conditions, continue accessing private resources. The vulnerability affects versions 18.9 through 18.10.6, 18.11 through 18.11.3, and 19.0. Patched versions are 18.10.7, 18.11.4, and 19.0.1. The issue was reported through HackerOne and assigned CWE-863 (Incorrect Authorization). CVSS 3.1 score is 4.3 (Medium), indicating network-accessible attack vector with low attack complexity, requiring low privileges but no user interaction, with limited confidentiality impact.

Vendor
GitLab
Product
Unknown
CVSS
MEDIUM 4.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-28
Original CVE updated
2026-05-29
Advisory published
2026-05-28
Advisory updated
2026-05-29

Who should care

GitLab administrators managing self-hosted CE/EE instances, DevOps security teams, and organizations relying on Project Access Tokens for CI/CD or API access should prioritize patching. Security teams should audit token lifecycle management and verify that blocking operations properly invalidate access.

Technical summary

The vulnerability stems from incorrect authorization enforcement in GitLab's Project Access Token handling. When a Project Access Token was blocked, the authorization check failed to immediately terminate active sessions or cached permissions, allowing continued access to private resources. The flaw is classified as CWE-863 (Incorrect Authorization) with a CVSS 3.1 score of 4.3 (Medium). Attack prerequisites require low-privileged network access and an existing (but blocked) valid token. The confidentiality impact is limited (C:L) with no integrity or availability impact.

Defensive priority

medium

Recommended defensive actions

  • Upgrade GitLab CE/EE to patched versions: 18.10.7, 18.11.4, or 19.0.1 or later
  • Review and rotate Project Access Tokens, especially any tokens that were blocked but may have shown continued activity
  • Audit access logs for private resources for unauthorized access patterns from May 2026 backwards
  • Verify token revocation workflows are functioning correctly after patching
  • For environments where immediate patching is not feasible, consider additional monitoring on private repository access and token usage patterns

Evidence notes

The vulnerability description and affected version ranges are sourced from the official CVE record and GitLab's security release notes. The CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) confirms network accessibility with low privileges required. CWE-863 classification indicates an authorization logic error. The HackerOne report reference confirms responsible disclosure through GitLab's bug bounty program.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-9807 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-9807

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-9807 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-9807

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.