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 48 min ago

Severity of matching CVEs

CVSS base severity, as scored in NVD

Critical
00%
High
00%
Medium
264100%
Low or not scored
00%
Matching CVEs
264
Last two years
Critical
0
CVSS 9.0 and above
High
0
CVSS 7.0 to 8.9
Known exploited
0
On CISA's KEV list

Matching CVEs published

By month, last two years

Peak 23 · May 2026

  • Total: 259
  • December 2024: 8
  • January 2025: 7
  • February 2025: 12
  • March 2025: 13
  • April 2025: 4
  • May 2025: 8
  • June 2025: 9
  • July 2025: 6
  • August 2025: 13
  • September 2025: 7
  • October 2025: 4
  • November 2025: 11
  • December 2025: 6
  • January 2026: 7
  • February 2026: 14
  • March 2026: 18
  • April 2026: 15
  • May 2026: 23
  • June 2026: 15
  • July 2026: 16
  • August 2026: 9
  • September 2026: 15
  • October 2026: 19
  • 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. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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

  11. 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

  12. 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

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

  14. 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

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

  21. 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

  22. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.6 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 disclose confidential issue titles due to improper filtering under certain circumstances.

    GitLab· Mar 11, 2026

  23. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 14.4 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user with group import permissions to create labels in private projects due to improper authorization validation in the group import process under certain circumstances.

    GitLab· Mar 11, 2026

  24. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 1.0 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 cause repository downloads to contain different code than displayed in the web interface due to incorrect validation of branch references under certain circumstances.

    GitLab· Mar 11, 2026

  25. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.6 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user, when the `markdown_placeholders` feature flag was enabled, to inject JavaScript in a browser due to improper sanitization of placeholder content in markdown processing.

    GitLab· Mar 11, 2026

  26. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.6 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 disclose metadata from private issues, merge requests, epics, milestones, or commits due to improper filtering in the snippet rendering process under certain circumstances.

    GitLab· Mar 11, 2026

  27. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.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 cause a denial of service condition due to improper input validation on webhook custom header names under certain conditions.

    GitLab· Mar 11, 2026

  28. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 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 access Virtual Registry data in groups where they are not members due to improper authorization under certain conditions.

    GitLab· Mar 11, 2026

  29. 4.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.5 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user with maintainer-role permissions to reveal Datadog API credentials under certain conditions.

    GitLab· Mar 11, 2026

  30. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 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 cause a denial of service due to improper handling of webhook response data.

    GitLab· Mar 11, 2026

  31. 6.5Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 11.2 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have allowed an authenticated user to cause denial of service by exploiting a Bitbucket Server import endpoint via repeatedly sending large responses.

    GitLab· Feb 25, 2026

  32. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 17.11 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that, under certain conditions, could have allowed Developer-role users with insufficient privileges to make unauthorized modifications to protected Conan packages.

    GitLab· Feb 25, 2026

  33. 6.1Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.2 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that under certain circumstances, could have allowed an unauthenticated user to inject arbitrary scripts into the Mermaid sandbox UI.

    GitLab· Feb 25, 2026

  34. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.0 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have, under certain circumstances, allowed an authenticated user with certain access to cause Denial of Service by creating specially crafted CI triggers via the API.

    GitLab· Feb 25, 2026

  35. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.7 before 18.7.5, 18.8 before 18.8.5, and 18.9 before 18.9.1 that could have allowed an unauthorized user with Developer-role permissions to set pipeline variables for manually triggered jobs under certain conditions.

    GitLab· Feb 25, 2026

  36. 6.5Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 15.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an authenticated user to cause Denial of Service by uploading a malicious file and repeatedly querying it through GraphQl.

    GitLab· Feb 11, 2026

  37. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an authenticated user to inject malicious content into project labels titles.

    GitLab· Feb 11, 2026

  38. 4.6Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.8 before 18.8.4 that could have allowed an authenticated developer to hide specially crafted file changes from the WebUI.

    GitLab· Feb 11, 2026

  39. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 16.7 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to access iteration data from private descendant groups by querying the iterations API endpoint.

    GitLab· Feb 11, 2026

  40. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.9 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to add unauthorized email addresses to victim accounts through HTML injection in test case titles.

    GitLab· Feb 11, 2026

  41. 5.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to perform unauthorized operations by submitting GraphQL mutations through the GLQL API endpoint.

    GitLab· Feb 11, 2026

  42. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.1 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user to perform unauthorized actions on behalf of another user by injecting malicious content into vulnerability code flow.

    GitLab· Feb 11, 2026

  43. 5.4Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an authenticated user with certain permissions to make unauthorized requests to internal network services through the GitLab server.

    GitLab· Feb 11, 2026

  44. 4.3Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions, could have allowed an authenticated user to perform server-side request forgery against internal services by bypassing protections in the Git repository import functionality.

    GitLab· Feb 11, 2026

  45. 6.5Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.1 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2 that under certain circumstances could have allowed an authenticated user to create a denial of service condition by configuring malformed Wiki documents that bypass cycle detection.

    GitLab· Jan 22, 2026

  46. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.10 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2 that could have allowed an authenticated user to execute stored cross-site scripting through improper input validation in the Kubernetes proxy functionality.

    GitLab· Jan 14, 2026

  47. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.2.2 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed an authenticated user to achieve stored cross-site scripting by exploiting GitLab Flavored Markdown.

    GitLab· Jan 9, 2026

  48. 6.5Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.5 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed an authenticated user to modify instance-wide AI feature provider settings by exploiting missing authorization checks in GraphQL mutations.

    GitLab· Jan 9, 2026

  49. 4.3Med

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

    GitLab has remediated an issue in GitLab EE affecting all versions from 18.4 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed an authenticated user to access and utilize AI model settings from unauthorized namespaces by manipulating namespace identifiers in API requests.

    GitLab· Jan 9, 2026

  50. 5.4Med

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

    GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.4 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed an authenticated user with specific permissions to remove all project runners from unrelated projects by manipulating GraphQL runner associations.

    GitLab· Jan 9, 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 48 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.