PHP Vulnerability Responses by Company

GitLab

Global cloud / infrastructure
Aliases / services
ギットラボ / GitLab CI / GitLab Runner / GitLab
Official website
https://about.gitlab.com/

Each response applies only to its stated service scope. “Not listed” does not mean unpatched or unaffected.

Response status by service

GitLab CI/CD (customer PHP runtimes)

Response status
Customer runtime update guidance
Response information checked
2026-10-27

Current re-audit: Official response verified · Research date: 2026-10-27

Provides source management and CI/CD.

GitLab published guidance for customers to fix PHP runtimes and containers.

Scope: GitLab application's unaffected status does not cover customer PHP workloads.

What users should do

Inventory PHP, install fixed packages or rebuild updated images, then restart PHP processes.

Official service URL

Source URLs

  1. https://about.gitlab.com/blog/gitlab-helps-remediate-critical-php-flaws/https://about.gitlab.com/blog/gitlab-helps-remediate-critical-php-flaws/Response evidence
  2. Testing PHP with GitLab CI/CDhttps://docs.gitlab.com/ci/examples/php/Service and operation documentation

GitLab.com / GitLab Self-Managed / GitLab Dedicated

Response status
GitLab application unaffected
Response information checked
2026-10-27

Current re-audit: Official response verified · Research date: 2026-10-27

GitLab states its application does not serve requests through PHP and is unaffected.

Scope: Does not cover customer CI or deployment PHP.

What users should do

Assess customer PHP workloads separately.

Source URLs

  1. https://about.gitlab.com/blog/gitlab-helps-remediate-critical-php-flaws/https://about.gitlab.com/blog/gitlab-helps-remediate-critical-php-flaws/Response evidence
Related official sources
  1. Testing PHP with GitLab CI/CDOfficial information directory

Comments