CVEs.

Vulnerabilities published in the last two years in software made by the companies on the wall: clients, SDKs, agents and self-hosted editions. A CVE here does not mean the hosted service was affected or breached.

NVD data refreshed 5 min ago

Severity of matching CVEs

CVSS base severity, as scored in NVD

Critical
143%
High
12328%
Medium
26461%
Low or not scored
358%
Matching CVEs
436
Last two years
Critical
14
CVSS 9.0 and above
High
123
CVSS 7.0 to 8.9
Known exploited
2
On CISA's KEV list

Matching CVEs published

By month, last two years

Peak 36 · October 2026

  • Total: 424
  • December 2024: 11
  • January 2025: 8
  • February 2025: 18
  • March 2025: 19
  • April 2025: 8
  • May 2025: 14
  • June 2025: 19
  • July 2025: 11
  • August 2025: 15
  • September 2025: 16
  • October 2025: 10
  • November 2025: 14
  • December 2025: 11
  • January 2026: 13
  • February 2026: 25
  • March 2026: 27
  • April 2026: 23
  • May 2026: 31
  • June 2026: 24
  • July 2026: 20
  • August 2026: 23
  • September 2026: 28
  • October 2026: 36
  • November 2026: 0

Most CVEs

In each company's software, last two years

  1. Microsoft 365990
  2. NVIDIA590
  3. GitLab436
  4. Apple (iCloud, App Store and services)348
  5. MongoDB Atlas320
  6. Mattermost Cloud310

Matching CVEs

All servicesMicrosoft 365 990NVIDIA 590GitLab 436Apple (iCloud, App Store and services) 348MongoDB Atlas 320Mattermost Cloud 310Elastic Cloud 246Microsoft Azure 186Palo Alto Networks 184Autodesk 136JFrog 99Grafana Cloud 91Zoom 89HashiCorp (HCP / Terraform Cloud) 85Trend Micro 70Docker 65WatchGuard 61Vercel 59GitHub 56TeamViewer 47Amazon Web Services 38Hugging Face 35Anthropic (Claude) 34Salesforce 34Tenable 34Cloudflare 28Adobe 28Snowflake 23Cursor 22Temporal Cloud 21Shopify 19Canva 19LangChain / LangSmith 19Google Cloud 16Jira 14Ping Identity 13WordPress.com (Automattic) 13Webex 11Optimizely 11Metabase Cloud 10
  1. 4.3Med

    CVE-2026-8472 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.9 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with minimal access permissions to read work item metadata from private projects due to missing authorization checks.

    GitLab· Jul 8, 2026

  2. 5.3Med

    CVE-2026-7492 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.1 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an unauthenticated user to determine the existence of a private project due to improper authorization controls on cross-project reference pages.

    GitLab· Jul 8, 2026

  3. 5.4Med

    CVE-2026-6896 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary scripts in another user's browser session due to improper sanitization of user-supplied input.

    GitLab· Jul 8, 2026

  4. 2.7Low

    CVE-2026-6352 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with auditor-level access to modify compliance violation records due to improper authorization on certain GraphQL operations.

    GitLab· Jul 8, 2026

  5. 5.4Med

    CVE-2026-13320 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.7 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user to execute arbitrary scripts in another user's browser session due to improper sanitization of user-supplied input.

    GitLab· Jul 8, 2026

  6. 4.9Med

    CVE-2026-11827 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 9.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with maintainer-role permissions to obtain another user's stored credentials due to improper authorization controls.

    GitLab· Jul 8, 2026

  7. 4.3Med

    CVE-2025-12506 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user to create a repository where the content displayed in the web interface differed from the content available for download, due to improper handling of Git reference name resolution.

    GitLab· Jul 8, 2026

  8. 4.4Med

    CVE-2026-8330 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed sensitive information to be written to application logs due to insufficient filtering in a CI/CD API endpoint.

    GitLab· Jun 25, 2026

  9. 4.3Med

    CVE-2026-5952 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.11 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to bypass package protection rules and overwrite protected Maven package metadata due to incorrect authorization checks.

    GitLab· Jun 25, 2026

  10. 4.3Med

    CVE-2026-5796 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with Reporter-level group permissions to view package metadata from projects with the Package Registry disabled due to incorrect authorization checks in the group packages feature.

    GitLab· Jun 25, 2026

  11. 5.4Med

    CVE-2026-5309 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user to read or modify another group's virtual registry cleanup policy settings without authorization.

    GitLab· Jun 25, 2026

  12. 3.1Low

    CVE-2026-3176 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with limited permissions to access project information due to insufficient authorization checks.

    GitLab· Jun 25, 2026

  13. 5.3Med

    CVE-2026-2238 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.5 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an unauthenticated user to view confidential issue references on public projects due to improper authorization checks.

    GitLab· Jun 25, 2026

  14. 4.3Med

    CVE-2026-1606 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.8 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user to conceal content within a Snippet due to improper input validation.

    GitLab· Jun 25, 2026

  15. 3.1Low

    CVE-2026-12635 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with maintainer-role permissions to make requests to internal network resources through mirror synchronization due to improper URL validation.

    GitLab· Jun 25, 2026

  16. 7.5High

    CVE-2026-12053 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.1 that under certain conditions could have allowed a user to access sensitive information that had already been committed to a project, due to insufficient output filtering in Duo Workflows.

    GitLab· Jun 25, 2026

  17. 5.3Med

    CVE-2026-11379 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 13.11 prior to 18.11.6, 19.0 prior to 19.0.3, and 19.1 prior to 19.1.1 in which incorrect authorization in DAST site profile management could allow a user with Developer role to exfiltrate DAST site profile secrets under certain conditions.

    GitLab· Jun 25, 2026

  18. 6.1Med

    CVE-2026-10712 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an unauthenticated user to execute arbitrary JavaScript in a user's browser session due to improper path validation under certain conditions.

    GitLab· Jun 25, 2026

  19. 5.4Med

    CVE-2026-10086 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 16.4 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary client-side code in the context of another user's session, due to improper sanitization of user-supplied input.

    GitLab· Jun 25, 2026

  20. 3.8Low

    CVE-2026-0934 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 17.9 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with custom role permissions to view, create, or delete protected environment configurations despite CI/CD visibility being disabled for the project.

    GitLab· Jun 25, 2026

  21. 4.3Med

    CVE-2026-9694 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions, could have allowed an unauthenticated user to impersonate the GitLab Support Bot and inject arbitrary content via a specially crafted Service Desk email reply due to improper neutralization in email template processing.

    GitLab· Jun 11, 2026

  22. 6.5Med

    CVE-2026-9204 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user to read arbitrary files from the Gitaly server and access internal network resources during repository import, due to insufficient validation of secondary URLs.

    GitLab· Jun 11, 2026

  23. 8.7High

    CVE-2026-8589 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 13.1.4 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user to add unauthorized email addresses to a targeted user's account due to improper sanitization of user-supplied input in certain group setting fields.

    GitLab· Jun 11, 2026

  24. 7.5High

    CVE-2026-7250 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an unauthenticated user to cause denial of service due to improper input validation in the API request parsing middleware.

    GitLab· Jun 11, 2026

  25. 3.7Low

    CVE-2026-6976 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to hide changes from merge request diff views due to improper input handling of file names.

    GitLab· Jun 11, 2026

  26. 4.3Med

    CVE-2026-6277 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 13.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with Security Manager-role permissions to manage project security configuration even when the relevant feature was in a disabled state, due to incorrect authorization enforcement.

    GitLab· Jun 11, 2026

  27. 5.4Med

    CVE-2026-6269 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to modify hidden merge requests due to incorrect authorization enforcements.

    GitLab· Jun 11, 2026

  28. 3.1Low

    CVE-2026-3553 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.0 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user to access confidential issue details due to incorrect authorization checks.

    GitLab· Jun 11, 2026

  29. 6.5Med

    CVE-2026-1500 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user to cause denial of service due to uncontrolled resource consumption when processing a specially crafted file upload.

    GitLab· Jun 11, 2026

  30. 4.3Med

    CVE-2026-10733 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.0 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that could have allowed an authenticated user to cause denial of service on the CI/CD Catalog page due to improper sanitization.

    GitLab· Jun 11, 2026

  31. 8.7High

    CVE-2026-10087 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary client-side code on behalf of a targeted user due to improper input sanitization in the Analytics Dashboard.

    GitLab· Jun 11, 2026

  32. 4.3Med

    CVE-2026-9807 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed a blocked Project Access Token to continue accessing private resources due to incorrect authorization enforcement.

    GitLab· May 28, 2026

  33. 4.3Med

    CVE-2026-8716 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.7 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an authenticated user to access CI data from a different ref type than intended.

    GitLab· May 27, 2026

  34. 5.3Med

    CVE-2026-6713 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an unauthorized user to enumerate private projects due to incorrect authorization checks.

    GitLab· May 27, 2026

  35. 4.3Med

    CVE-2026-5296 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.7 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that when foundational flows were enabled at the group level, could have allowed an authenticated user with developer-role permissions to bypass flow restrictions under certain conditions.

    GitLab· May 27, 2026

  36. 8.2High

    CVE-2026-4868 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that, under certain conditions, could have allowed an authenticated user to cause specific Duo AI workflows to run under another user's identity due to improper user identity resolution when triggering Duo AI workflow runners.

    GitLab· May 27, 2026

  37. 4.3Med

    CVE-2026-2601 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 11.5 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to access sensitive deployment data on projects due to improper authorization checks.

    GitLab· May 27, 2026

  38. 6.5Med

    CVE-2026-1402 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.1 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1 that under certain conditions could have allowed an authenticated user to cause denial of service due to insufficient validation.

    GitLab· May 27, 2026

  39. 6.5Med

    CVE-2026-8280 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.3 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to cause denial of service through excessive memory consumption due to improper input validation.

    GitLab· May 14, 2026

  40. 4.3Med

    CVE-2026-8144 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.1 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with project membership to enumerate private group members due to missing authorization checks.

    GitLab· May 14, 2026

  41. 5.4Med

    CVE-2026-7481 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 16.4 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with developer-role permissions to execute arbitrary JavaScript in other users' browsers due to improper input sanitization.

    GitLab· May 14, 2026

  42. 3.5Low

    CVE-2026-7471 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with control of a virtual registry upstream to make requests to internal hosts due to improper validation.

    GitLab· May 14, 2026

  43. 5.4Med

    CVE-2026-7377 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that, in customizable analytics dashboards, could have allowed an authenticated user to execute arbitrary JavaScript in the context of other users' browsers due to improper input sanitization.

    GitLab· May 14, 2026

  44. 4.3Med

    CVE-2026-6883 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 15.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to bypass merge request approval requirements due to improper cleanup of orphaned policy records.

    GitLab· May 14, 2026

  45. 5.4Med

    CVE-2026-6335 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.11 before 18.11.3 that under certain conditions could have allowed an authenticated user to execute arbitrary code in another user's browser session due to improper sanitization.

    GitLab· May 14, 2026

  46. 5.4Med

    CVE-2026-6073 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to execute arbitrary JavaScript in other users' browsers due to improper input sanitization.

    GitLab· May 14, 2026

  47. 4.3Med

    CVE-2026-6063 (opens in a new tab)

    GitLab has remediated an issue in GitLab EE affecting all versions from 11.10 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that under certain conditions could have allowed an authenticated user with developer-role permissions to remove code owner approval rules from merge requests due to improper access control.

    GitLab· May 14, 2026

  48. 6.5Med

    CVE-2026-4527 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.10 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an unauthenticated user to create unauthorized Jira subscriptions for a targeted user's namespace via a specially crafted link due to missing CSRF protection.

    GitLab· May 14, 2026

  49. 6.5Med

    CVE-2026-4524 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9.1 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to access confidential issue content in public projects without proper authorization due to improper authorization checks.

    GitLab· May 14, 2026

  50. 4.3Med

    CVE-2026-3607 (opens in a new tab)

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with developer-role permissions to bypass package protection rules due to improper access control.

    GitLab· May 14, 2026

Public information only

Everything on this page was already published by the companies themselves or by public bodies. statuswall gathers it in one place, links every item to its original, and adds nothing from private or leaked sources.

Sources

How fresh it is

  • New and changed CVEs: pulled from NVD every two hours; last run 5 min ago
  • Known-exploited flags: updated from CISA in the same run
  • Window: the last two years; older entries drop off automatically

Source: the U.S. National Vulnerability Database, refreshed daily, with the known-exploited flag from CISA's KEV catalog. Descriptions are NVD's. A CVE is listed under a company when NVD names that company's product as affected, or when the company's own CVE authority assigned it; companies whose names are common words are matched only by explicit rules, so some CVEs will be missing. This product uses NVD data but is not endorsed or certified by the NVD. CVE is a registered trademark of The MITRE Corporation.

statuswall is independent and is not affiliated with, sponsored by or endorsed by any company named here. Company and product names are used only to identify whose public information is being referred to. The information is provided as is, for general reference, with no guarantee that it is complete, current or free of error; it is not security, legal or purchasing advice. Where this page and an official source differ, the official source is right.