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 1 h 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

  1. 6.5Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 10.7 before 17.11.5, 18.0 before 18.0.3, and 18.1 before 18.1.1 that could have allowed authenticated attackers to create a DoS condition by sending crafted GraphQL requests.

    GitLab· Jun 26, 2025

  2. 5.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.2 before 17.11.5, 18.0 before 18.0.3, and 18.1 before 18.1.1 that could have allowed unauthenticated attackers to upload arbitrary files to public projects by sending crafted API requests, potentially leading to resource abuse and unauthorized content storage.

    GitLab· Jun 26, 2025

  3. 6.1Med

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

    An issue has been discovered in GitLab EE that allows for cross-site-scripting attack and content security policy bypass in a user's browser under specific conditions, affecting all versions from 16.6 before 17.9.7, 17.10 before 17.10.5, and 17.11 before 17.11.1.

    GitLab· Jun 20, 2025

  4. 5.9Med

    CVE-2024-9512 (opens in a new tab)

    An issue has been discovered in GitLab EE affecting all versions prior to 17.10.8, 17.11 prior to 17.11.4, and 18.0 prior to 18.0.2. It may have been possible for private repository to be cloned in case of race condition when a secondary node is out of sync.

    GitLab· Jun 12, 2025

  5. 4.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.9 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. It was possible for authenticated users to access arbitrary compliance frameworks, leading to unauthorized data disclosure.

    GitLab· Jun 12, 2025

  6. 6.5Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 2.1.0 before 17.10.8, 17.11 before 17.11.4, and 18.0 before 18.0.2. A lack of input validation in HTTP responses could allow an authenticated user to cause denial of service.

    GitLab· Jun 12, 2025

  7. 6.1Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.9 before 17.10.8, 17.11 before 17.11.4, and 18.0 before 18.0.2. Improper output encoding in the snipper viewer functionality lead to Cross-Site scripting attacks.

    GitLab· Jun 12, 2025

  8. 6.5Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. This could allow an authenticated attacker to cause a denial of service condition by exhausting server resources.

    GitLab· May 22, 2025

  9. 4.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.1 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. Under certain conditions un-authorised users can view full email addresses that should be partially obscured.

    GitLab· May 22, 2025

  10. 4.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 16.8 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. Group access controls could allow certain users to bypass two-factor authentication requirements.

    GitLab· May 22, 2025

  11. 6.8Med

    CVE-2024-12093 (opens in a new tab)

    An issue has been discovered in GitLab CE/EE affecting all versions from 11.1 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. Improper XPath validation allows modified SAML response to bypass 2FA requirement under specialized conditions.

    GitLab· May 22, 2025

  12. 6.5Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 10.2 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. A lack of input validation in the Kubernetes integration could allow an authenticated user to cause denial of service..

    GitLab· May 22, 2025

  13. 6.5Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. A lack of proper validation in GitLab could allow an authenticated user to cause a denial of service condition.

    GitLab· May 22, 2025

  14. 4.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 18.0 before 18.0.1. In certain circumstances, a user with limited permissions could access Job Data via a crafted GraphQL query.

    GitLab· May 22, 2025

  15. 6.8Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.3 prior to 17.9.8, from 17.10 prior to 17.10.6, and from 17.11 prior to 17.11.2. A security vulnerability allows attackers to bypass Device OAuth flow protections, enabling authorization form submission through minimal user interaction.

    GitLab· May 9, 2025

  16. 4.3Med

    CVE-2024-12244 (opens in a new tab)

    An issue has been discovered in access controls could allow users to view certain restricted project information even when related features are disabled in GitLab EE, affecting all versions from 17.7 prior to 17.9.7, 17.10 prior to 17.10.5, and 17.11 prior to 17.11.1.

    GitLab· Apr 24, 2025

  17. 6.5Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 7.7 before 17.8.7, 17.9 before 17.9.6, and 17.10 before 17.10.4. Under certain conditions, an attacker could potentially trick users into unintentionally authorizing sensitive actions on their behalf.

    GitLab· Apr 10, 2025

  18. 5.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.9 before 17.9.6, and 17.10 before 17.10.4. The runtime profiling data of a specific service was accessible to unauthenticated users.

    GitLab· Apr 10, 2025

  19. 5.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 13.12 before 17.8.7, 17.9 before 17.9.6, and 17.10 before 17.10.4. Under certain conditions users could bypass IP access restrictions and view sensitive information.

    GitLab· Apr 10, 2025

  20. 6.5Med

    CVE-2024-12619 (opens in a new tab)

    An issue has been discovered in GitLab CE/EE affecting all versions from 16.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1, allowing internal users to gain unauthorized access to internal projects.

    GitLab· Mar 28, 2025

  21. 5.5Med

    CVE-2024-10307 (opens in a new tab)

    An issue has been discovered in GitLab EE/CE affecting all versions from 12.10 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. A maliciously crafted file can cause uncontrolled CPU consumption when viewing the associated merge request.

    GitLab· Mar 28, 2025

  22. 6.5Med

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

    An issue has been discovered in the GitLab Duo with Amazon Q affecting all versions from 17.8 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. A specifically crafted issue could manipulate AI-assisted development features to potentially expose sensitive project data to unauthorized users.

    GitLab· Mar 27, 2025

  23. 5.4Med

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

    An issue has been discovered in Gitlab EE/CE for AppSec affecting all versions from 13.5.0 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. Certain error messages could allow Cross-Site Scripting attacks (XSS). for AppSec.

    GitLab· Mar 27, 2025

  24. 5.4Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.7 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. Improper rendering of certain file types leads to cross-site scripting.

    GitLab· Mar 27, 2025

  25. 6.5Med

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

    An issue has been discovered in GitLab EE/CE affecting all versions starting from 16.9 before 17.7.7, all versions starting from 17.8 before 17.8.5, all versions starting from 17.9 before 17.9.2 could allow unauthorized users to access confidential information intended for internal use only.

    GitLab· Mar 13, 2025

  26. 6.5Med

    CVE-2024-13054 (opens in a new tab)

    An issue was discovered in GitLab CE/EE affecting all versions before 17.7.7, 17.8 prior to 17.8.5, and 17.9 prior to 17.9.2. where a denial of service vulnerability could allow an attacker to cause a system reboot under certain conditions.

    GitLab· Mar 13, 2025

  27. 4.3Med

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

    Improper authorization in GitLab EE affecting all versions from 17.7 prior to 17.7.6, 17.8 prior to 17.8.4, 17.9 prior to 17.9.1 allow users with limited permissions to access to potentially sensitive project analytics data.

    GitLab· Mar 6, 2025

  28. 4.2Med

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

    An issue has been discovered in GitLab CE/EE for Self-Managed and Dedicated instances affecting all versions from 17.5 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2. It was possible for a user added as an External to read and clone internal projects under certain circumstances."

    GitLab· Mar 6, 2025

  29. 6.1Med

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

    A Cross Site Scripting (XSS) vulnerability in GitLab-EE affecting all versions from 16.6 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1 allows an attacker to bypass security controls and execute arbitrary scripts in a users browser under specific conditions.

    GitLab· Mar 3, 2025

  30. 6.1Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 15.10 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1. A proxy feature could potentially allow unintended content rendering leading to XSS under specific circumstances.

    GitLab· Mar 3, 2025

  31. 5.3Med

    CVE-2024-10925 (opens in a new tab)

    A vulnerability in GitLab-EE affecting all versions from 16.2 prior to 17.7.6, 17.8 prior to 17.8.4, and 17.9 prior to 17.9.1 allows a Guest user to read Security policy YAML

    GitLab· Mar 3, 2025

  32. 5.4Med

    CVE-2024-8186 (opens in a new tab)

    An issue has been discovered in GitLab CE/EE affecting all versions from 16.6 before 17.7.6, 17.8 before 17.8.4, and 17.9 before 17.9.1. An attacker could inject HMTL into the child item search potentially leading to XSS in certain situations.

    GitLab· Mar 3, 2025

  33. 5.7Med

    CVE-2024-3303 (opens in a new tab)

    An issue was discovered in GitLab EE affecting all versions starting from 16.0 prior to 17.6.5, starting from 17.7 prior to 17.7.4, and starting from 17.8 prior to 17.8.2, which allows an attacker to exfiltrate contents of a private issue using prompt injection.

    GitLab· Feb 13, 2025

  34. 5.3Med

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

    An issue discovered in GitLab CE/EE affecting all versions from 16.11 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2 meant that long-lived connections in ActionCable potentially allowed revoked Personal Access Tokens access to streaming results.

    GitLab· Feb 13, 2025

  35. 6.6Med

    CVE-2024-8266 (opens in a new tab)

    An issue was discovered in GitLab CE/EE affecting all versions starting from 17.1 prior to 17.6.0, which allows an attacker with maintainer role to trigger a pipeline as project owner under certain circumstances.

    GitLab· Feb 13, 2025

  36. 4.3Med

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

    Improper Authorization in GitLab CE/EE affecting all versions from 17.7 prior to 17.7.4, 17.8 prior to 17.8.2 allow users with limited permissions to perform unauthorized actions on critical project data.

    GitLab· Feb 12, 2025

  37. 6.1Med

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

    An XSS vulnerability exists in GitLab CE/EE affecting all versions from 13.3 prior to 17.6.5, 17.7 prior to 17.7.4 and 17.8 prior to 17.8.2 that allows an attacker to execute unauthorized actions via a change page.

    GitLab· Feb 12, 2025

  38. 6.5Med

    CVE-2024-12379 (opens in a new tab)

    A denial of service vulnerability in GitLab CE/EE affecting all versions from 14.1 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2 allows an attacker to impact the availability of GitLab via unbounded symbol creation via the scopes parameter in a Personal Access Token.

    GitLab· Feb 12, 2025

  39. 6.1Med

    CVE-2024-10383 (opens in a new tab)

    An issue has been discovered in the gitlab-web-ide-vscode-fork component distributed over CDN affecting all versions prior to 1.89.1-1.0.0-dev-20241118094343and used by all versions of GitLab CE/EE starting from 15.11 prior to 17.3 and which also temporarily affected versions 17.4, 17.5 and 17.6, where a XSS attack was possible when loading .ipynb files in the web IDE

    GitLab· Feb 7, 2025

  40. 6.5Med

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

    A Denial of Service (DoS) issue has been discovered in GitLab CE/EE affecting all versions starting from 7.14.1 prior to 17.3.7, 17.4 prior to 17.4.4, and 17.5 prior to 17.5.2. A denial of service could occur upon importing maliciously crafted content using the Fogbugz importer.

    GitLab· Feb 7, 2025

  41. 6.5Med

    CVE-2024-3976 (opens in a new tab)

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 14.0 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. It was possible to disclose via the UI the confidential issues title and description from a public project to unauthorised instance users.

    GitLab· Feb 5, 2025

  42. 5.4Med

    CVE-2024-5528 (opens in a new tab)

    An issue was discovered in GitLab CE/EE affecting all versions prior to 16.11.6, starting from 17.0 prior to 17.0.4, and starting from 17.1 prior to 17.1.2, which allows a subdomain takeover in GitLab Pages.

    GitLab· Feb 5, 2025

  43. 4.4Med

    CVE-2024-6356 (opens in a new tab)

    An issue was discovered in GitLab EE affecting all versions starting from 16.0 prior to 17.0.6, starting from 17.1 prior to 17.1.4, and starting from 17.2 prior to 17.2.2, which allowed cross project access for Security policy bot.

    GitLab· Feb 5, 2025

  44. 5.3Med

    CVE-2024-1539 (opens in a new tab)

    An issue has been discovered in GitLab EE affecting all versions starting from 15.2 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2. It was possible to disclose updates to issues to a banned group member using the API.

    GitLab· Feb 5, 2025

  45. 4.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 15.0 prior to 17.5.5, from 17.6 prior to 17.6.3, and from 17.7 prior to 17.7.1. Under certain conditions, processing of CI artifacts metadata could cause background jobs to become unresponsive.

    GitLab· Jan 28, 2025

  46. 6.1Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.2 before 17.6.4, 17.7 before 17.7.3, and 17.8 before 17.8.1. Improper rendering of certain file types lead to cross-site scripting.

    GitLab· Jan 24, 2025

  47. 5.3Med

    CVE-2024-11931 (opens in a new tab)

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 17.0 prior to 17.6.4, from 17.7 prior to 17.7.3, and from 17.8 prior to 17.8.1. Under certain conditions, it may have been possible for users with developer role to exfiltrate protected CI variables via CI lint.

    GitLab· Jan 24, 2025

  48. 5.4Med

    CVE-2024-13041 (opens in a new tab)

    An issue was discovered in GitLab CE/EE affecting all versions starting from 16.4 prior to 17.5.5, starting from 17.6 prior to 17.6.3, and starting from 17.7 prior to 17.7.1. When a user is created via the SAML provider, the external groups setting overrides the external provider configuration. As a result, the user may not be marked as external thereby giving those users access to internal projects or groups.

    GitLab· Jan 9, 2025

  49. 4.3Med

    CVE-2024-6324 (opens in a new tab)

    An issue was discovered in GitLab CE/EE affecting all versions starting from 15.7 prior to 17.5.5, starting from 17.6 prior to 17.6.3, and starting from 17.7 prior to 17.7.1. It was possible to trigger a DoS by creating cyclic references between epics.

    GitLab· Jan 9, 2025

  50. 4.3Med

    CVE-2024-12431 (opens in a new tab)

    An issue was discovered in GitLab CE/EE affecting all versions starting from 15.5 before 17.5.5, 17.6 before 17.6.3, and 17.7 before 17.7.1, in which unauthorized users could manipulate the status of issues in public projects.

    GitLab· Jan 8, 2025

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