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

Severity mix

CVSS base severity, as scored in NVD

Critical
4018%
High
2,47348%
Medium
1,99639%
Low or not scored
2365%
CVEs
5,106
Last two years
Critical
401
CVSS 9.0 and above
High
2,473
CVSS 7.0 to 8.9
Known exploited
55
On CISA's KEV list

CVEs published

By month, last two years

Peak 834 · October 2026

  • Total: 5042
  • December 2024: 87
  • January 2025: 102
  • February 2025: 92
  • March 2025: 81
  • April 2025: 132
  • May 2025: 106
  • June 2025: 119
  • July 2025: 112
  • August 2025: 166
  • September 2025: 133
  • October 2025: 126
  • November 2025: 134
  • December 2025: 159
  • January 2026: 116
  • February 2026: 139
  • March 2026: 204
  • April 2026: 140
  • May 2026: 306
  • June 2026: 221
  • July 2026: 390
  • August 2026: 476
  • September 2026: 578
  • October 2026: 834
  • November 2026: 89

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

Latest 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. 8.2High

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

    A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to cause the Manage API to send crafted outbound requests to an attacker-controlled host. An unauthenticated endpoint parsed an attacker-supplied cluster configuration and issued gateway-to-agent requests whose HMAC authenticated only a timestamp, not the request path or body. An attacker positioned to intercept the outbound request could capture this token and replay it against privileged management agent endpoints. High-availability deployments were not affec

    GitHub· Sep 1, 2026

  2. 6.5Med

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

    Missing Authorization (CWE-862) in Kibana can lead to information disclosure via Privilege Abuse (CAPEC-122). An authorization control was not applied to an internal Kibana APM integration function, allowing any authenticated Kibana user to read APM server credentials that should be restricted to users holding APM or Fleet administrative privileges.

    Elastic Cloud· Sep 1, 2026

  3. 7.1High

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

    Missing Authorization (CWE-862) in the Elasticsearch custom inference service can lead to information disclosure via Privilege Abuse (CAPEC-122). A user holding only inference execution privileges could cause outbound inference traffic to be directed to a destination of their choosing and could cause administrator-provisioned credentials to be exposed.

    Elastic Cloud· Sep 1, 2026

  4. 4.2Med

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

    Incorrect Authorization (CWE-863) in Kibana can lead to unauthorized disclosure, modification, and deletion of data via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). Where two authenticated principals originating from different authentication realms share the same username value, one could read, modify, and delete the other's private Elastic AI Assistant Knowledge Base entries.

    Elastic Cloud· Sep 1, 2026

  5. 5.9Med

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

    Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') (CWE-444) in Elasticsearch can lead to information disclosure via HTTP Request Smuggling (CAPEC-33). Under specific proxy deployment configurations, a network attacker could obtain confidential responses intended for other authenticated users.

    Elastic Cloud· Sep 1, 2026

  6. 4.3Med

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

    Missing Authorization (CWE-862) in Kibana can lead to information disclosure via Exploiting Incorrectly Configured Access Control Security Levels (CAPEC-180). An authenticated user holding minimal Elasticsearch privileges could bypass Kibana feature authorization and space access controls, resulting in the unauthorized disclosure of Fleet deployment metadata from the default Kibana space.

    Elastic Cloud· Sep 1, 2026

  7. 4.3Med

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

    Missing Authorization (CWE-862) in the Kibana Entity Store feature can lead to unauthorized credential creation via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user holding only low-privilege Security feature access could invoke an administrative operation that creates and persists Elasticsearch API keys under the caller's identity, bypassing the elevated cluster and Kibana privileges that the documented Entity Store setup flow requires.

    Elastic Cloud· Sep 1, 2026

  8. 7.3High

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

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22) in Kibana can lead to the unauthorized deletion of privileged resources via Path Traversal (CAPEC-126). A low-privileged user holding tag creation privileges could cause a subsequent administrative action in the tag management interface to act on an unintended target, resulting in the deletion of privileged resources including administrative accounts and other organizational assets. Exploitation requires an administrator to interact with the affected interface.

    Elastic Cloud· Sep 1, 2026

  9. 6.5Med

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

    Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding only low, read-level Agent Builder privileges could submit a specially crafted request that causes Kibana to consume an unbounded amount of memory, terminating the process and denying service to all users of the instance.

    Elastic Cloud· Sep 1, 2026

  10. 6.5Med

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

    Execution with Unnecessary Privileges (CWE-250) in the Kibana machine learning feature can lead to information disclosure via Privilege Abuse (CAPEC-122). An operation available to users holding only read access to the machine learning feature was performed with an internal service identity rather than the identity of the requesting user. Such a user could therefore receive data from Elasticsearch indices they are not authorized to read. No Elasticsearch cluster or index privileges are required.

    Elastic Cloud· Sep 1, 2026

  11. 6.5Med

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

    Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user can submit a specially crafted request that causes excessive resource consumption, which may render Kibana unavailable.

    Elastic Cloud· Sep 1, 2026

  12. 8.8High

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

    Deserialization of Untrusted Data (CWE-502) in the Elasticsearch machine learning component can lead to remote code execution via Object Injection (CAPEC-586). A specially crafted trained model artifact could cause attacker-controlled logic to execute with a materially broader system-call surface than intended. Exploitation requires an authenticated user with sufficient privileges to create and deploy trained models.

    Elastic Cloud· Sep 1, 2026

  13. 6.5Med

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

    Uncaught Exception (CWE-248) in Kibana can lead to a denial of service via Input Data Manipulation (CAPEC-153). An authenticated user holding only the low-privileged feature access required to use the Observability AI Assistant can submit a specially crafted request that produces an unhandled error condition, terminating the Kibana process and denying service to all users and spaces on that instance until it is restarted.

    Elastic Cloud· Sep 1, 2026

  14. 5.4Med

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

    Incorrect Authorization (CWE-863) in Kibana can lead to unauthorized modification of data via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user holding only Security Solution read access in a Kibana space could enumerate and change the state of Entity Store maintainer tasks, silently disabling Entity Analytics maintenance for that space.

    Elastic Cloud· Sep 1, 2026

  15. 4.3Med

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

    Incorrect Authorization (CWE-863) in Kibana Entity Analytics can lead to a loss of security monitoring via Accessing Functionality Not Properly Constrained by ACLs (CAPEC-1). An authenticated user holding only read-level Security feature access, and no Elasticsearch privileges, could stop the recurring Privilege Monitoring engine task for a Kibana space. Privileged user monitoring then stops producing data for that space while the engine continues to report a healthy state to operators.

    Elastic Cloud· Sep 1, 2026

  16. 6.5Med

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

    Improper Handling of Highly Compressed Data (CWE-409) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user holding Streams management privileges could supply specially crafted content that expands to a far larger volume of data during processing, exhausting the memory available to Kibana. The Kibana process is terminated by the host and remains unavailable to all users until the service is restarted.

    Elastic Cloud· Sep 1, 2026

  17. 6.5Med

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

    Improper Neutralization of Special Elements in Data Query Logic (CWE-943) in Kibana can lead to information disclosure via NoSQL Injection (CAPEC-676). An authenticated user with access to the affected query functionality could submit specially crafted input that alters the intended query logic, returning data the user is not authorized to read.

    Elastic Cloud· Sep 1, 2026

  18. 8.3High

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

    Incorrect Authorization (CWE-863) in Kibana can lead to privilege escalation via Exploiting Incorrectly Configured Access Control Security Levels (CAPEC-180). A user holding workflow edit permissions could cause scheduled workflow executions to run with the privileges of a different, higher-privileged user, allowing access to and modification of data beyond their own authorization scope.

    Elastic Cloud· Sep 1, 2026

  19. 4.9Med

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

    Allocation of Resources Without Limits or Throttling (CWE-770) in Elasticsearch can lead to a denial of service via Excessive Allocation (CAPEC-130). A user with elevated privileges can submit a specially crafted request that causes excessive memory consumption, which may render the affected node unavailable.

    Elastic Cloud· Sep 1, 2026

  20. 6.5Med

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

    Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana can lead to a denial of service via Excessive Allocation (CAPEC-130). An authenticated user with low-level permissions could submit a specially crafted request that causes excessive resource consumption, which may render Kibana unavailable.

    Elastic Cloud· Sep 1, 2026

  21. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  22. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  23. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  24. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  25. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  26. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  27. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  28. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  29. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  30. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  31. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  32. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  33. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  34. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  35. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  36. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  37. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  38. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  39. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  40. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  41. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  42. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  43. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  44. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  45. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  46. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  47. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  48. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  49. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 2026

  50. 7.8High

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

    NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.

    NVIDIA· Sep 1, 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 3 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.