PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-12436 GitLab CVE debrief

CVE-2026-12436 is a HIGH-severity vulnerability affecting GitLab CE/EE versions 18.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. An authenticated user could modify CI/CD configurations due to improper validation of user-supplied attributes when processing pipeline schedule inputs. This vulnerability allows unauthorized modification of CI/CD configurations, potentially leading to security risks. GitLab has remediated this issue in versions 19.0.5, 19.1.3, and 19.2.1. Limited source detail exists; further verification is recommended. Additional review of pipeline schedule inputs and user-supplied attributes is necessary to ensure configuration integrity and security.

Vendor
GitLab
Product
Unknown
CVSS
HIGH 8.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-29
Original CVE updated
2026-08-03
Advisory published
2026-07-29
Advisory updated
2026-08-03

Who should care

GitLab administrators and users with CI/CD configurations should be aware of this vulnerability and take steps to patch vulnerable versions and verify their configurations. Security teams and vulnerability management teams should also review the impact of this vulnerability on their environments and prioritize patching. Additionally, operators and platform teams may need to assess the risk and implement compensating controls if necessary.

Technical summary

CVE-2026-12436 is a HIGH-severity vulnerability in GitLab CE/EE affecting multiple versions. An authenticated user could modify CI/CD configurations due to improper validation of user-supplied attributes when processing pipeline schedule inputs. GitLab has remediated this issue in versions 19.0.5, 19.1.3, and 19.2.1. The vulnerability allows unauthorized modification of CI/CD configurations, potentially leading to security risks. Users should review their configurations and patch vulnerable versions.

Defensive priority

GitLab users should prioritize patching vulnerable versions to prevent potential CI/CD configuration modification.

Recommended defensive actions

  • Patch vulnerable GitLab versions to 19.0.5, 19.1.3, or 19.2.1
  • Verify and update CI/CD configurations for potential unauthorized modifications
  • Monitor GitLab instance for suspicious pipeline schedule activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record indicates that GitLab has remediated an issue affecting versions 18.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. Authenticated users could modify CI/CD configuration due to improper validation of user-supplied attributes. Limited source detail exists; further verification recommended. Additional review of pipeline schedule inputs and user-supplied attributes is necessary to ensure configuration integrity.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-12436 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-12436 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.