To search repositories and projects, login to gitlab.com . Suggestions GitLab Duo Agent Platform Code Suggestions (AI) CI/CD GitLab on AWS GitLab on Google Cloud Why GitLab?
What happened
To search repositories and projects, login to gitlab. com . Platform DevOps CI/CD Source Code Management Agile Delivery Artifact Management Security & Governance Application Security Testing Governance & Compliance Secrets Management Supply Chain Security Agentic AI & Context Duo Agent Platform Orbit Context Graph Visibility & Measurement Explore the Platform GitLab Orbit is generally available Higher agent accuracy, lower token cost.
Where the sources line up
Solutions Outcomes DevOps Modernization Security Modernization AI Modernization By size Enterprise Small Business Startups Industries Financial Services Public Sector Telecommunications Automotive Education Aerospace View all Solutions GitLab Security Standard Learn how to harden your software factory and let AI agents earn autonomy, without trading away security.
Practical impact for readers
Pricing Resources Discover Docs University Demo Series Demo Hub Services Well Architected Connect Blog Community Customers Partners Events View all resources What’s new in GitLab Stay updated with our latest features and improvements.
Who should pay attention now
CVE-2026-114938 allows unauthenticated remote code execution in Java. Learn which builds fix the flaw and how to check your projects.
What is still unclear
GitLab has internally assessed the impact of Java4Shell, and concluded it is not exploitable in GitLab-managed infrastructure. Exploitation requires a specific combination of conditions, which we confirmed are not present in our production environment. A single component was found to contain the impacted bundle in its runtime environment, which we are proactively upgrading as a hardening measure.
Latest comments
0No comments yet. You can start the conversation.