CVE Vulnerability Catalog

On a multi-user system, a user with an active local login session could downgrade a system-wide Flatpak app to an older version by removing the app's remote ref via the unprivileged system-helper RemoveLocalRef method, causing the anti-downgrade check to fail to find a reference date. A malicious local user could use this to expose other users of the same system to an app version with unfixed vulnerabilities.

The OCI delta stream parser reads sizes as guint64 but passes them to GLib I/O and allocation functions expecting gsize (32 bits on 32-bit systems), causing undersized allocations and heap buffer overflows. An attacker controlling an OCI registry can craft a delta stream that triggers this during flatpak install/update, potentially achieving code execution on 32-bit systems.

Nezha 2.2.3 contains a Host header injection regression in the OAuth2 redirect endpoint. When the dashboard_host setting is empty, /api/v1/oauth2/{provider} reflects the attacker-supplied Host header into the redirect_uri. An attacker can steal the victim's authorization code and take over the account.

Nezha before 2.2.7 contains an information disclosure vulnerability in the GET /api/v1/profile endpoint that returns the bcrypt-hashed password field of authenticated users. Attackers can extract password hashes and perform offline cracking attacks without rate limiting or audit trail constraints.

Nezha is a server and website monitoring tool. In versions >= 2.2.11 and < 2.3.1, the service sentinel worker (service/singleton/servicesentinel.go) contains an incomplete fix for a previously reported nil dereference denial of service (GHSA-qjpp-gffx-2wm9). The 2026-07-21 fix re-validated the service lifecycle under serviceResponseDataStoreLock but reused an already-captured, now stale reporter pointer and never re-validated the server, and that lock does not guard ServerShared. An authenticated user with the member role who owns an agent can issue a concurrent server delete (POST /api/v1/batch-delete/server) for their own server to win the race window, causing the worker to dereference a missing entry in the server list snapshot. Because the sentinel workers and the gRPC server have no recover()/recovery interceptor, the resulting panic is unrecovered and crashes the entire instance. This is fixed in version 2.3.1.

Nezha versions 2.0.10 through 2.3.2 use a restricted HTTP client to validate user-configurable notification and DDNS webhook URLs, but the denylist did not cover IPv6 transition ranges — specifically the 6to4 prefix 2002::/16 and the local-use IPv4/IPv6 translation prefix 64:ff9b:1::/48. Because such addresses satisfy Go's netip.Addr.IsGlobalUnicast check, the URL validator accepted them. An authenticated user able to configure a webhook may be able to cause the dashboard to issue requests to an otherwise restricted IPv6 endpoint, but only where the dashboard's network provides unusual or non-standards-compliant routing for these transition ranges; no direct path to an IPv4 metadata, loopback, or private-network HTTP request has been demonstrated. The issue is fixed in version 2.3.3 (commit d1fcde8e), which blocks both prefixes.

Nezha Dashboard versions before 2.3.5 fail to restrict service monitor task types to supported probe types. An authenticated user with nezha:service:write scope can submit privileged task types through the service API by exploiting the shared protobuf Task.Type namespace.

Nezha before 2.3.8 fails to validate alert rule type and duration bounds, allowing authenticated non-administrator users to create malformed rules that trigger unrecovered panics in the alert evaluator goroutine. An attacker can submit a crafted rule via POST /api/v1/alert-rule, crashing the dashboard process.

obot versions before v0.21.1 fail to enforce Access Control Rules on the /mcp-connect endpoint, allowing any authenticated user to connect to restricted MCP servers if they possess the server ID. Attackers can bypass authorization to access sensitive backend systems.

Obot up to commit d7e6970, when started via the Docker quickstart from README, listens on 0.0.0.0:8080 with authentication disabled. Every request is mapped to a synthetic 'nobody' user with Owner and Admin roles, granting full administrative access. The quickstart also mounts /var/run/docker.sock, giving access to the host's Docker control surface.

Obot before v0.23.0 contains a server-side request forgery vulnerability in remote MCP server registration that allows privileged users to specify arbitrary URLs without destination validation. Attackers with Power User or higher roles can coerce Obot to make requests to internal services and cloud metadata endpoints, reading responses in error messages to disclose sensitive credentials.

Obot versions before v0.23.0 fail to enforce authentication on MCP Registry endpoints under /v0.1/* when registry authentication is enabled. An unauthenticated attacker can read registry metadata including server names, descriptions, repository URLs, and connect URLs by sending GET requests to /v0.1/servers.

Obot before v0.23.0 (affected versions <= v0.22.1) with OBOT_SERVER_ENABLE_AUTHENTICATION=true exposes OAuth dynamic client registration without authentication and without redirect URI restrictions. An attacker can register a client pointing to their domain and steal the authorization code of a logged-in victim, then exchange it for access and refresh tokens. The MCP OAuth token carries the victim's full group set in the JWT, and Obot validates only the issuer, not the audience, allowing the token to be used as a bearer token against any Obot API endpoint the victim can access.

A cross-site scripting (XSS) vulnerability has been identified in zhistaredu StarTraining up to 3.8.1, in the Upload Endpoint component, specifically in MimeTypeUtils.java. Manipulation of the File argument allows remote attack. The exploit is publicly available, and the vendor did not respond.

A security flaw was discovered in zhistaredu StarTraining up to 3.8.1 affecting the checkRoleAllowed function in SysRoleServiceImpl.java of the dataScope Endpoint component. The manipulation results in missing authorization and can be performed remotely.

A vulnerability was identified in zhistaredu StarTraining up to 3.8.1 affecting the SysUser.isAdmin function in edu-common/src/main/java/com/edu/common/core/domain/entity/SysUser.java of the authRole Endpoint component. Manipulation of the userId/roleIds arguments leads to authorization bypass and can be carried out remotely.

A vulnerability was determined in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be affecting an unknown functionality of registrationform.php. Manipulation of the FName/LName/Addrs arguments leads to cross site scripting and can be executed remotely.

A malicious OCI registry can hardlink arbitrary host files into the extraction directory when a user installs or updates a Flatpak application from an OCI remote, allowing disclosure of arbitrary host file contents.

A vulnerability was found in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be affecting an unknown function of loginlinkstudent.php. Manipulation of the umail argument results in missing authentication and can be exploited remotely.

A vulnerability has been found in mathurvishal CloudClassroom-PHP-Project up to commit 5dadec098bfbbf3300d60c3494db3fb95b66e7be. An unknown function in updatedetailsfromfaculty.php is affected by SQL injection via the myfid argument. The attack can be launched remotely and the exploit is public.