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

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

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

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

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

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

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

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

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

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

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

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

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

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