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 13 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. 5.8Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.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 view Jira issues outside the configured project scope due to an integration filter functioning only as a display control rather than enforcing access boundaries as specified.

    GitLab· May 14, 2026

  2. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.7 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 download private debugging symbols from inaccessible projects due to improper access control.

    GitLab· May 14, 2026

  3. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.6 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 PyPI package protection rules and upload restricted packages due to improper authorization checks.

    GitLab· May 14, 2026

  4. 2.7Low

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 16.10 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that when instance-level approval rule editing prevention was enabled, could have allowed an authenticated user with Maintainer permissions to modify or delete project approval rules due to missing authorization checks.

    GitLab· May 14, 2026

  5. 7.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.0 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 cause denial of service by sending specially crafted requests due to insufficient input validation.

    GitLab· May 14, 2026

  6. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.10 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 delete protected container registry tags due to improper authorization checks.

    GitLab· May 14, 2026

  7. 8.1High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.0 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 a read_api scoped OAuth application to create issues and add comments to issues in private projects due to improper authorization.

    GitLab· May 14, 2026

  8. 7.5High

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 11.9 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 cause denial of service by uploading a specially crafted file due to improper validation.

    GitLab· May 14, 2026

  9. 7.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 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 cause denial of service by sending specially crafted JSON payloads due to insufficient input validation.

    GitLab· May 14, 2026

  10. 7.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 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 cause denial of service by sending specially crafted payloads on certain API endpoints.

    GitLab· May 14, 2026

  11. 4.3Med

    CVE-2025-13874 (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 Guest permissions to view issues in projects they were not authorized to access.

    GitLab· May 14, 2026

  12. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.11 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 inject HTML and JavaScript into email notifications sent to other users due to improper input sanitization.

    GitLab· May 14, 2026

  13. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed a user to use invalidated or incorrectly scoped credentials to access Virtual Registries under certain conditions.

    GitLab· Apr 22, 2026

  14. 8.1High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.10.4 and 18.11 before 18.11.1 that 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· Apr 22, 2026

  15. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.11 before 18.11.1 that could have allowed an authenticated user to access titles of confidential or private issues in public projects due to improper access control in the issue description rendering process.

    GitLab· Apr 22, 2026

  16. 6.1Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.1.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an unauthenticated user to access tokens in the Storybook development environment due to improper input validation.

    GitLab· Apr 22, 2026

  17. 8.1High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.0 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an unauthenticated user to execute GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection.

    GitLab· Apr 22, 2026

  18. 3.5Low

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user to load unauthorized content into another user's browser due to improper input validation in the Mermaid sandbox.

    GitLab· Apr 22, 2026

  19. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.3 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user to cause denial of service when importing issues due to improper input validation.

    GitLab· Apr 22, 2026

  20. 2.7Low

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that under certain conditions could have allowed an authenticated user with project owner permissions to bypass group fork prevention settings due to improper authorization checks.

    GitLab· Apr 22, 2026

  21. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.2 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an authenticated user to cause denial of service due to insufficient resource allocation limits when retrieving notes under certain conditions.

    GitLab· Apr 22, 2026

  22. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.4 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an authenticated user to cause denial of service by overwhelming system resources under certain conditions due to insufficient resource allocation limits in the GraphQL API.

    GitLab· Apr 22, 2026

  23. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.6 before 18.9.6, 18.10 before 18.10.4, and 18.11 before 18.11.1 that could have allowed an authenticated user to cause denial of service under certain conditions by exhausting server resources by making crafted requests to a discussions endpoint.

    GitLab· Apr 22, 2026

  24. 8.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.9.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user to invoke unintended server-side methods through websocket connections due to improper access control.

    GitLab· Apr 8, 2026

  25. 2.7Low

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user with custom role permissions to demote or remove higher-privileged group members due to improper authorization checks on member management operations.

    GitLab· Apr 8, 2026

  26. 5.4Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have assigned compliance frameworks from namespaces they were not authorized to access to their own project, due to missing namespace validation on self-managed instances.

    GitLab· Apr 8, 2026

  27. 5.4Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.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· Apr 8, 2026

  28. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that under certain circumstances could have allowed an authenticated user with auditor privileges to modify vulnerability flag data in private projects due to incorrect authorization.

    GitLab· Apr 8, 2026

  29. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user to access confidential issues assigned to other users via CSV export due to insufficient authorization checks.

    GitLab· Apr 8, 2026

  30. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 11.3 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user with developer-role permissions to modify protected environment settings due to improper authorization checks in the API.

    GitLab· Apr 8, 2026

  31. 5.7Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.0.0 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that in Code Quality reports could have allowed an authenticated user to leak IP addresses of users viewing the report via specially crafted content.

    GitLab· Apr 8, 2026

  32. 6.5Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an authenticated user to cause denial of service to the GitLab instance due to improper input validation in GraphQL queries.

    GitLab· Apr 8, 2026

  33. 7.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.10 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an unauthenticated user to cause denial of service due to improper input validation of JSON payloads.

    GitLab· Apr 8, 2026

  34. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 16.6 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that under certain circumstances could have allowed an authenticated user to have access to other users' email addresses via certain GraphQL queries.

    GitLab· Apr 8, 2026

  35. 7.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.0 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an unauthenticated user to cause denial of service by sending repeated GraphQL queries.

    GitLab· Apr 8, 2026

  36. 8.8High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.3 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 affecting Jira Connect installations that could have allowed an authenticated user with minimal workspace permissions to obtain installation credentials and impersonate the GitLab app due to improper authorization checks.

    GitLab· Mar 30, 2026

  37. 7.5High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an unauthenticated user to cause a denial of service by making the GitLab instance unresponsive due to improper input validation in GraphQL request processing.

    GitLab· Mar 25, 2026

  38. 8.8High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.10 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an unauthenticated user to execute arbitrary GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection.

    GitLab· Mar 25, 2026

  39. 5.4Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 15.4 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an authenticated user to add email addresses to targeted user accounts due to improper sanitization of HTML content.

    GitLab· Mar 25, 2026

  40. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.7 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an authenticated user to execute arbitrary JavaScript in a user's browser due to improper sanitization of entity-encoded content in Mermaid diagrams.

    GitLab· Mar 25, 2026

  41. 8.1High

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 7.11 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an unauthenticated user to bypass WebAuthn two-factor authentication and gain unauthorized access to user accounts due to inconsistent input validation in the authentication process.

    GitLab· Mar 25, 2026

  42. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.10 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an authenticated user to perform unauthorized actions on merge requests in other projects due to improper access control during cross-repository operations.

    GitLab· Mar 25, 2026

  43. 7.5High

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.5 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an unauthenticated user to access API tokens of self-hosted AI models due to improper access control.

    GitLab· Mar 25, 2026

  44. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.6 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that under certain conditions could have allowed an authenticated user with Planner role to view security category metadata and attributes in group security configuration due to improper access control

    GitLab· Mar 25, 2026

  45. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.7 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an authenticated user to cause a denial of service due to excessive resource consumption when handling certain CI-related inputs.

    GitLab· Mar 25, 2026

  46. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.10 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an authenticated user to cause a denial of service due to excessive resource consumption when processing certain webhook configuration inputs.

    GitLab· Mar 25, 2026

  47. 3.7Low

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.1 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that under certain conditions could have allowed an authenticated user to gain unauthorized access to resources due to improper caching of authorization decisions.

    GitLab· Mar 25, 2026

  48. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.14 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to gain unauthorized access to confidential issue title created in public projects under certain circumstances.

    GitLab· Mar 12, 2026

  49. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.1 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that, under certain conditions, could have allowed an authenticated user to access previous pipeline job information on projects with repository and CI/CD disabled due to improper authorization checks.

    GitLab· Mar 11, 2026

  50. 5.0Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.11 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to make unintended internal requests through proxy environments under certain conditions due to improper input validation in import functionality.

    GitLab· Mar 11, 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 13 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.