Attributed metadata history
Up to 100 retained publisher events per page for 73fc1ebbf802241f5ec38e74608b64c7b0691a46e4deee15d7da69c209de7846. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_cdcffed32aa78fd61f
observed · 2026-10-13 15:27:02 UTC
GitLab just fixed a max-severity vulnerability that could allow unauthenticated attackers to execute arbitrary code on its servers. The company released a fix on Monday, alongside patches for five other high-severity flaws affecting its source code management and continuous integration and delivery (CI/CD) platform. The vulnerability, tracked as CVE-2026-97229, was fixed in versions 19.4.2, 19.3.5, and 19.2.8 of its Community Edition (CE) and Enterprise Edition (EE), according to a patch advisory. The company urged administrators of self-managed installations running affected versions to upgrade immediately. GitLab.com is already running the patched version, while GitLab Dedicated customers do not need to take action, the company said in the advisory. The release also addresses vulnerabilities that could expose protected environment variables, allow unauthorized pipeline execution, and enable attackers to inject crafted content into AI agent instructions. The fixes span both CE and EE, with some issues affecting only the Enterprise Edition. “When no specific deployment type (omnibus, source code, Helm chart, etc.) of a product is mentioned, it means all types are affe
Fingerprint: 12059f4c7bbbab1e04a5f06a545e1341cca20a1da01943f3ad2112289cee58a0
intelligence_src_cdcffed32aa78fd61f
observed · 2026-10-12 15:25:03 UTC
available
Fingerprint: 7058adebc821bb9d551a9ff0b80ac7c4e28d07e4464aca030b831463a16c18c5