CVE-2026-92530 GitLab CVE debrief

Who should care

GitLab CE/EE administrators and security teams should assess exposure and prioritize patching vulnerable instances to prevent potential spoofing of merge request authorship. Operators of GitLab CE/EE instances, platform administrators, and security teams need to verify and apply patches for versions 19.1 to 19.2.6, 19.3 to 19.3.2, and 19.4.0. Vulnerability management and security teams should monitor for potential spoofing attempts and review inventory of

Why it matters

Defenders should prioritize verifying and applying patches for GitLab CE/EE versions 19.1 to 19.2.6, 19.3 to 19.3.2, and 19.4.0, as these are vulnerable to potential spoofing of merge request authorship. The vulnerability allows an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users on the target instance.

• Potential spoofing of merge request authorship, allowing an authenticated user to attribute content to arbitrary existing users
• Need to verify and apply patches for vulnerable GitLab CE/EE versions
• Possible impact on the integrity of merge requests and authorship information

Technical summary

The vulnerability affects GitLab CE/EE versions 19.1 to 19.2.6, 19.3 to 19.3.2, and 19.4.0, allowing an authenticated user to spoof merge request authorship due to improper reliance on ephemeral cache state during Direct Transfer imports. This issue could allow an authenticated user to attribute content to arbitrary existing users on the target instance. The vulnerability has been remediated in versions 19.2.7, 19.3.3, and 19.4.1. Defenders should prioritize verifying and applying patches for these vulnerable versions.

Defensive priority

Defenders should prioritize verifying and applying patches for GitLab CE/EE versions 19.1 to 19.2.6, 19.3 to 19.3.2, and 19.4.0, as these are vulnerable to potential spoofing of merge request authorship.

Recommended defensive actions

• Verify and apply patches for GitLab CE/EE versions 19.1 to 19.2.6, 19.3 to 19.3.2, and 19.4.0
• Review and update inventory of GitLab CE/EE instances to ensure patched versions are deployed
• Monitor GitLab CE/EE instances for potential spoofing attempts
• Confirm whether affected GitLab CE/EE deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability and its remediation. GitLab has released patches for the affected versions. Defenders should verify patches are applied to GitLab CE/EE versions 19.1 to 19.2.6, 19.3 to 19.3.2, and 19.4.0. Evidence from GitLab's advisory and CVE details indicate the vulnerability allows spoofing of merge request authorship. Limited source detail suggests verifying patch deployment and monitoring for potential spoofing attempts are prudent.

Sources and 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.