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

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

  2. 7.5High

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

    An issue was discovered in GitLab CE/EE affecting all versions starting from 13.6 prior to 17.2.9, starting from 17.3 prior to 17.3.5, and starting from 17.4 prior to 17.4.2, where viewing diffs of MR with conflicts can be slow.

    GitLab· Feb 5, 2025

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

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

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

  6. 8.8High

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

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 10.6 prior to 16.9.7, starting from 16.10 prior to 16.10.5, and starting from 16.11 prior to 16.11.2 in which cross-site request forgery may have been possible on GitLab instances configured to use JWT as an OmniAuth provider.

    GitLab· Jan 31, 2025

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

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

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

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

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

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

  13. 6.5Med

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

    An issue was discovered in GitLab CE/EE affecting all versions starting from 17.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. Under certain conditions, access tokens may have been logged when API requests were made in a specific manner.

    GitLab· Jan 8, 2025

  14. 5.3Med

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

    An issue was discovered in GitLab CE/EE affecting all versions from 15.0 prior to 17.4.6, 17.5 prior to 17.5.4, and 17.6 prior to 17.6.2 that allowed non-member users to view unresolved threads marked as internal notes in public projects merge requests.

    GitLab· Dec 16, 2024

  15. 5.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 16.9 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. By using a specific GraphQL query, under specific conditions an unauthorized user can retrieve branch names.

    GitLab· Dec 16, 2024

  16. 6.4Med

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

    An issue was discovered in GitLab CE/EE affecting all versions from 11.8 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. An attacker could potentially perform an open redirect against a given releases API endpoint.

    GitLab· Dec 12, 2024

  17. 4.3Med

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

    An issue was discovered in GitLab CE/EE affecting all versions starting from 13.9 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2, that allows an attacker to cause uncontrolled CPU consumption, potentially leading to a Denial of Service (DoS) condition while parsing templates to generate changelogs.

    GitLab· Dec 12, 2024

  18. 5.4Med

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

    An issue was discovered in GitLab affecting all versions starting 15.2 to 17.4.6, 17.5 prior to 17.5.4, and 17.6 prior to 17.6.2. On self hosted installs, it was possible to leak the anti-CSRF-token to an external site while the Harbor integration was enabled.

    GitLab· Dec 12, 2024

  19. 7.5High

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 9.4 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. An attacker could cause a denial of service with requests for diff files on a commit or merge request.

    GitLab· Dec 12, 2024

  20. 5.4Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.3 before 17.4.6, 17.5 before 17.5.4, and 17.6 before 17.6.2. Improper output encoding could lead to XSS if CSP is not enabled.

    GitLab· Dec 12, 2024

  21. 6.7Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7 prior to 17.4.6, from 17.5 prior to 17.5.4, and from 17.6 prior to 17.6.2. It may have been possible for an attacker with a victim's `CI_JOB_TOKEN` to obtain a GitLab session token belonging to the victim.

    GitLab· Dec 12, 2024

  22. 4.0Med

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

    An issue was discovered in GitLab CE/EE affecting all versions starting from 11.0 prior to 17.4.6, starting from 17.5 prior to 17.5.4, and starting from 17.6 prior to 17.6.2, where sensitive information passed in GraphQL mutations may have been retained in GraphQL logs.

    GitLab· Dec 12, 2024

  23. 8.7High

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

    An issue was discovered in GitLab CE/EE affecting all versions starting from 16.1 prior to 17.4.6, starting from 17.5 prior to 17.5.4, and starting from 17.6 prior to 17.6.2, injection of NEL headers in k8s proxy response could lead to session data exfiltration.

    GitLab· Dec 12, 2024

  24. 3.1Low

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

    An issue has been discovered in GitLab EE affecting all versions starting from 14.3 before 17.4.6, all versions starting from 17.5 before 17.5.4 all versions starting from 17.6 before 17.6.2, that allows group users to view confidential incident title through the Wiki History Diff feature, potentially leading to information disclosure.

    GitLab· Dec 12, 2024

  25. 5.3Med

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

    An issue has been discovered in GitLab EE affecting all versions starting from 17.3 before 17.3.7, all versions starting from 17.4 before 17.4.4, all versions starting from 17.5 before 17.5.2 in which an unauthenticated user may be able to read some information about an MR in a private project, under certain circumstances.

    GitLab· Nov 26, 2024

  26. 7.5High

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

    A Denial of Service (DoS) issue has been discovered in GitLab CE/EE affecting all versions prior to 12.6 prior to 17.4.5, 17.5 prior to 17.5.3, and 17.6 prior to 17.6.1. An attacker could cause a denial of service with a crafted cargo.toml file.

    GitLab· Nov 26, 2024

  27. 7.5High

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

    An issue was discovered in GitLab CE/EE affecting all versions starting from 15.6 prior to 17.4.5, starting from 17.5 prior to 17.5.3, starting from 17.6 prior to 17.6.1 which could cause Denial of Service via integrating a malicious harbor registry.

    GitLab· Nov 26, 2024

  28. 8.8High

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 8.12 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. This issue allows an attacker with access to a victim's Personal Access Token (PAT) to escalate privileges.

    GitLab· Nov 26, 2024

  29. 7.5High

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

    A denial of service (DoS) condition was discovered in GitLab CE/EE affecting all versions from 13.2.4 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. By leveraging this vulnerability an attacker could create a DoS condition by sending crafted API calls. This was a regression of an earlier patch.

    GitLab· Nov 26, 2024

  30. 7.5High

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

    An issue was discovered in GitLab CE/EE affecting all versions from 16.9.8 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. Certain API endpoints could potentially allow unauthorized access to sensitive data due to overly broad application of token scopes.

    GitLab· Nov 26, 2024

  31. 5.3Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 16.11 before 17.4.5, 17.5 before 17.5.3, and 17.6 before 17.6.1. Long-lived connections could potentially bypass authentication controls, allowing unauthorized access to streaming results.

    GitLab· Nov 26, 2024

  32. 7.5High

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

    An issue has been discovered in GitLab CE/EE affecting all versions starting from 16.3 before 17.4.2, all versions starting from 17.5 before 17.5.4, all versions starting from 17.6 before 17.6.2. This issue allows an attacker to create a group with a name matching an existing unique Pages domain, potentially leading to domain confusion attacks.

    GitLab· Nov 14, 2024

  33. 6.1Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 16 before 17.3.7, 17.4 before 17.4.4, and 17.5 before 17.5.2. The vulnerability could allow an attacker to inject malicious JavaScript code in Analytics Dashboards through a specially crafted URL.

    GitLab· Nov 14, 2024

  34. 6.5Med

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

    An issue was discovered in GitLab CE/EE affecting all versions starting from 17.2 prior to 17.3.7, starting from 17.4 prior to 17.4.4 and starting from 17.5 prior to 17.5.2, which could have allowed an attacker gaining full API access as the victim via the Device OAuth flow.

    GitLab· Nov 14, 2024

  35. 8.8High

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

    An issue was discovered in GitLab CE/EE affecting all versions starting from 16.0 prior to 17.3.7, starting from 17.4 prior to 17.4.4, and starting from 17.5 prior to 17.5.2, which could have allowed unauthorized access to the Kubernetes agent in a cluster under specific configurations.

    GitLab· Nov 14, 2024

  36. 5.4Med

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

    An issue has been discovered in GitLab CE/EE affecting all versions from 17.3 before 17.3.7, 17.4 before 17.4.4, and 17.5 before 17.5.2. Improper output encoding could lead to XSS if CSP is not enabled.

    GitLab· Nov 14, 2024

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