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 6 min ago
Severity of matching CVEs
CVSS base severity, as scored in NVD
- Critical
- 4100%
- High
- 00%
- Medium
- 00%
- Low or not scored
- 00%
- Matching CVEs
- 4
- Last two years
- Critical
- 4
- 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 2 · May 2026
- Total: 3
- December 2024: 0
- January 2025: 0
- February 2025: 0
- March 2025: 0
- April 2025: 0
- May 2025: 0
- June 2025: 0
- July 2025: 0
- August 2025: 0
- September 2025: 0
- October 2025: 0
- November 2025: 0
- December 2025: 0
- January 2026: 0
- February 2026: 0
- March 2026: 0
- April 2026: 0
- May 2026: 2
- June 2026: 0
- July 2026: 0
- August 2026: 0
- September 2026: 1
- October 2026: 0
- November 2026: 0
Most CVEs
In each company's software, last two years
Matching CVEs
- 9.3Crit
CVE-2026-77987 (opens in a new tab)
A server-side request forgery (SSRF) vulnerability was identified in the notebook viewer of GitHub Enterprise Server. The notebook viewer validated the scheme and host of a user-supplied URL but did not validate the port, allowing requests to be directed to internal services listening on other ports of the same appliance. Response bodies were not returned to the requester, but response timing acted as an oracle that allowed instance secrets to be extracted character by character. An extracted secret could then be used in a separate interaction with an internal service to obtain remote code exe
GitHub· Sep 22, 2026
- 9.1Crit
CVE-2026-48501 (opens in a new tab)
GitHub CLI (gh) is GitHub’s official command line tool. Prior to 2.93.0, GitHub CLI incorrectly includes authorization header in API requests to TUF repository mirrors via gh attestation, gh release verify, and gh release verify-asset commands. The CLI uses a shared HTTP client with an authentication layer that automatically attaches tokens to outgoing requests. This layer lacks accurate host detection and can incorrectly attribute the target host, providing it with a token it should never receive. Specifically, the host normalization logic collapses any *.github.com subdomain to github.com, s
GitHub· May 29, 2026
- 9.2Crit
CVE-2026-9312 (opens in a new tab)
A server-side request forgery (SSRF) vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to send crafted requests to internal services by exploiting insufficient input validation in an upload endpoint. By injecting path traversal content into request parameters, an attacker could bypass the intended request flow and redirect internal API calls, potentially accessing internal services and exposing sensitive credentials. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.22 and was fixed in versions 3.17.17, 3.18.11, 3.19
GitHub· May 27, 2026
- 9.6Crit
CVE-2024-52308 (opens in a new tab)
The GitHub CLI version 2.6.1 and earlier are vulnerable to remote code execution through a malicious codespace SSH server when using `gh codespace ssh` or `gh codespace logs` commands. This has been patched in the cli v2.62.0. Developers connect to remote codespaces through an SSH server running within the devcontainer, which is generally provided through the [default devcontainer image]( https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-... https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-conf
GitHub· 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
- National Vulnerability Database (opens in a new tab): CVE IDs, descriptions, publication dates and CVSS severity, published by the U.S. government (NIST)
- CISA Known Exploited Vulnerabilities catalog (opens in a new tab): the "Known exploited" flag
How fresh it is
- New and changed CVEs: pulled from NVD every two hours; last run 6 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.