CVE Vulnerability Catalog

A vulnerability in Prowler (versions 5.4.0 through 5.35.0) allows an unauthenticated attacker to take over the account of a user who has not yet completed registration. This occurs because Google or GitHub login is automatically linked to an existing local account with the same email address, without verifying that the address belongs to the same person. An attacker can register an account with the victim's email address and gain persistent access to their data, including cloud credentials, scan findings, and tenant memberships.

NGINX Plus and NGINX Open Source configured with ssl_session_cache shared:name:size without explicit ssl_session_ticket_key directives to automatically rotate SSL session ticket keys allow a remote unauthenticated attacker to forge client SSL sessions in a non-deterministic manner. An attacker could leverage this to bypass verification of client certificates.

NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_core_module module. When asynchronous file I/O (AIO) is enabled in certain configurations, processing a Server Side Includes (SSI) page containing “include virtual” commands may trigger a Use-After-Free (UAF) in the NGINX worker process. This may cause memory corruption or a worker process crash. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.

NGINX Gateway Fabric configured with the Gateway CRD and an authenticated gRPC connection with NGINX Agent allows a namespaced authenticated attacker with access to a service account to impersonate the authenticated NGINX Agent gRPC connection and read TLS private keys of Gateway deployments in another namespace.

NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_v3_module. When using HTTP/3 with the proxy_request_buffering on directive, an unauthenticated attacker may be able to inject data into the proxied request.

Vulnerability in F5 NGINX Kubernetes Ingress Controller (NIC) when configured with ExternalAuth policy or Ingress external authentication. Client-supplied X-Forwarded-Prefix, X-Forwarded-URI, X-Original-URI, and X-Forwarded-Method headers are forwarded unsanitized into the internal authentication subrequest, allowing an unauthenticated remote attacker to spoof request attributes evaluated by the external authentication provider.

Vulnerability in NGINX Plus and NGINX Open Source when a map directive uses regex matching and the root directive or access log format references the map's regex capture variables before the map output variable. An unauthenticated attacker can send crafted HTTP requests, causing a heap buffer overflow in the NGINX worker process, leading to restart or potential code execution.

Vulnerability in NGINX Gateway Fabric where the spec.basic.realm (and spec.jwt.realm) field of a namespaced AuthenticationFilter is rendered verbatim, unescaped and unvalidated, into the shared data-plane nginx.conf as auth_basic "<realm>";. An authenticated attacker with namespace access can inject arbitrary NGINX directives into the Gateway's data-plane config.

Incomplete fix for CVE-2026-12996. A use-after-free in OpenVPN 2.6.0 through 2.6.22 and 2.7_alpha1 through 2.7.7 allows remote authenticated peers to potentially cause a denial of service or leak memory via crafted packets during TLS session promotion or expiry.

Gitea's web attachment handler skips its cross-repository ownership check for attachments created before 16 January 2026 and checks permissions against the repository named in the request URL instead. An unauthenticated attacker who knows a private attachment's UUID can request it through a public repository's attachment path and retrieve its contents.

When OpenID sign-in is enabled, Gitea processes unauthenticated assertion parameters and sends an HTTP POST request to the caller-supplied OpenID provider endpoint during verification. An attacker controls the destination and much of the form body, allowing interaction with internal HTTP services reachable from the Gitea server.

Gitea's collaboration access-mode endpoint accepts the Owner access mode from an authenticated repository collaborator with Admin access. The collaborator can promote their effective permissions from Admin to Owner and then perform owner-only operations, including transferring the repository to their own account.

Gitea allows a token with write:user scope to register an attacker-controlled SSH public key on the token owner's account. API requests signed with the corresponding private key authenticate as that account through HTTP Signature without API token scope information, causing route-level token scope checks to be skipped.

Gitea Runner passes workflow-controlled container options into Docker job container configuration while privileged mode is disabled. Host namespace settings, expanded capabilities, and security profile overrides can remain effective despite Privileged being forced false.

Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pull_request_target event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the repository and organization secrets available to that event.

Gitea substitutes a URL derived from the markup Context field into external renderer command templates without escaping the reference path before shell-style argument splitting. A crafted Context can inject additional renderer arguments, including options that load executable filter files. On deployments using a susceptible external renderer such as pandoc, a user who can place a filter file at an accessible path can cause it to execute as the Gitea service account; the public repository markup endpoint itself can be reachable without authentication.

Gitea's OpenID connect handler accepts a user's password without enforcing enrolled TOTP or WebAuthn verification before completing sign-in and linking an OpenID identifier. When OpenID sign-in is enabled, an attacker who knows the victim's password can obtain a session and link an attacker-controlled identifier. The attacker can then sign in through that identifier without the victim's password or second factor, and a password change does not remove the link.

Gitea's Maven upload handler reads checksum uploads entirely into memory and returns before enforcing package-size quotas. An authenticated user with package-publish permission can submit an oversized body to a checksum endpoint, bypassing the upload quota and exhausting server memory.

Gitea uses inconsistent repository visibility predicates, and the condition used by some repository-listing endpoints admits repositories whose owners are hidden from the viewer. Those listings disclose repository metadata even though direct routes correctly deny access with a 404 response.

Gitea does not limit the length of the gitignores field accepted by repository-creation forms and the API. Repository initialization splits the field into template names, repeatedly reads the referenced templates, and buffers their contents in memory. An attacker who can create repositories can submit an oversized value to amplify template reads and memory use, impairing availability.