CVE Vulnerability Catalog

GeoLens prior to 1.2.3 contains multiple authorization flaws in read and link endpoints. The application authorizes only the resource named in the request URL and fails to re-authorize a second caller-influenced dataset reached through relationships, map layers, VRT sources, externalId lookups, or request bodies. Anonymous callers can obtain metadata, rows, vector geometries, raster pixels, and other data from private datasets via public maps, dataset relationship APIs, and the /collections/datasets/items endpoint.

Conflibot prior to 1.2.1 builds git checkout, git merge, and git format-patch commands by interpolating the attacker-controlled pull request head.ref value into strings passed to exec. In the documented pull_request_target configuration, an attacker can open a pull request whose branch name contains shell metacharacters that are executed without maintainer interaction. The issue is fixed in versions 1.2.1 and 2.0.0.

In Dragonfly prior to 2.4.4-rc.3, the scheduler's default unauthenticated v1 gRPC flow accepts attacker-controlled PeerHost.Ip and PeerHost.DownPort values through RegisterPeerTask and ReportPeerResult. These values are copied into resource.Host, and Peer.DownloadTinyFile() builds an HTTP GET request without destination validation, allowing read SSRF against loopback, link-local, and private services. DownPort is restricted to 1024-65534, and up to 128 bytes of the response can be placed in Task.DirectPiece.

In Cyberdrop-DL from 8.5.0 until 9.14.0, the Pixeldrain crawler uses substring host matching instead of requiring the input host to be an exact member of SUPPORTED_DOMAINS, then reuses that host for API requests. When a Pixeldrain API key is configured, processing a crafted URL from an attacker-controlled lookalike host causes the Authorization header to be sent to that host, disclosing the user's API key.

In Pipelines-as-Code prior to 0.37.8, 0.39.6, 0.42.1, and 0.48.0, a GitHub App installation token created during webhook processing is not scoped to the repository that triggered the event when the App is installed across multiple repositories. A user with push access to one repository can submit a PipelineRun with a remote task annotation targeting a private repository in the same installation, disclosing that repository's Tekton definitions.

Vulnerability in Pipelines-as-Code before 0.37.8, 0.39.6, 0.42.1, and 0.48.0. The GitHub App provider accepts X-GitHub-Enterprise-Host as the API host while processing webhook events before signature validation or host confirmation. An unauthenticated attacker reaching the webhook endpoint can select an attacker-controlled host and cause the controller to send a locally signed GitHub App JWT to that service.

Vulnerability in XWiki Platform from 13.4-rc-1 through 16.10.17, 17.4.10, 17.10.4, and 18.1.0-rc-1. The Live Data edit REST API allows a user with page edit rights to change that page's rights without executing normal authorization checks. The user can grant script right and then execute dangerous Velocity scripts or send unfiltered HTML/JavaScript to clients.

Vulnerability in Contentful MCP Server before versions 1.7.19 and 0.4.5. export_space and import_space expose host, proxy, rawProxy, and insecure network options to LLM-controlled tool arguments and combine them with CONTENTFUL_MANAGEMENT_TOKEN. After enabling migration tools, a direct MCP call or prompt injection can redirect API requests and Authorization header to an attacker-controlled host.

In Kuma prior to 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7, Universal mode kuma-dp connections to an HTTPS control plane disable TLS peer verification when --ca-cert-file is not supplied and KUMA_CONTROL_PLANE_CA_CERT is unset. The dataplane authentication token is sent over the unverified connection, allowing an on-path attacker to intercept the token, impersonate the control plane, inject a forged bootstrap configuration, and take over the proxy.

In Kuma prior to 2.7.26, 2.9.16, 2.11.14, 2.12.11, and 2.13.7, a kumactl profile manually configured for an HTTPS control plane without --ca-cert-file disables TLS peer verification and sends API tokens over the unverified connection. An attacker on the network path can intercept user or administrator API tokens and act against the control plane as the compromised user.

In Cosmos prior to 0.22.19, tokenMiddleware in src/proxy/routerGen.go can return through the Constellation tunnel bypass before removing x-cosmos-user, x-cosmos-role, x-cosmos-user-role, and x-cosmos-mfa headers and before invoking AdminOnlyWithRedirect. An attacker with a valid x-cstln-auth API key for an enrolled device who reaches Cosmos through the Constellation Nebula tunnel can supply a chosen x-cosmos-user value to a route with AuthEnabled enabled when the upstream application trusts that forward-auth header.

Dragonfly prior to 2.4.4 registers GET /api/v1/oauth and GET /api/v1/oauth/:id without jwt.MiddlewareFunc() or RBAC(), while the handler returns models.Oauth records with client_secret exposed in JSON. When an administrator has configured a GitHub or Google OAuth provider, an unauthenticated network client can retrieve the provider's client secret, client identifier, and redirect URL.

In pyLoad prior to 0.5.0b3.dev101, EventManager in src/pyload/core/managers/event_manager.py appends a Client object to the clients list for each unique uuid submitted to the authenticated getEvents API endpoint, but get_events does not invoke the available clean method to remove inactive clients. An authenticated user can repeatedly submit unique UUID values, causing retained client objects and process memory to grow without bound.

In pyLoad prior to 0.5.0b3.dev101, is_global_address in src/pyload/core/utils/web/check.py relies on Python's global-address classification without examining IPv4 destinations embedded in 6to4 or NAT64 IPv6 addresses. A low-privileged user can submit an IPv6 literal through parse_urls to the pre-resolution is_global_host guard, and curl resolves hostnames before the same vulnerable check is applied, permitting connections to embedded loopback, private, CGNAT, or link-local IPv4 addresses.

In Nextflow from 25.09.2-edge until 25.10.6 and 26.04.3, nextflow auth login writes Seqera Platform OIDC bearer tokens to ${NXF_HOME:-~/.nextflow}/seqera-auth.config through AuthCommandImpl.writeConfig without setting restrictive file permissions, allowing the default umask 022 to create the file with mode 0644. On a multi-user POSIX host, a local user who can traverse the victim's home directory can read seqera-auth.config and impersonate the victim against Seqera Platform within the token's scope.

In free5GC 4.2.3 and earlier, HandleCreateEeSubscriptions and HandleQueryeesubscriptions in internal/sbi/api_datarepository.go validate the ueId path value with a regular expression whose final .+ alternative accepts any non-empty string instead of restricting identifiers to supported SUPI and GPSI formats. An actor with network reachability to the UDR SBI can submit a non-3GPP identifier to /nudr-dr/v2/subscription-data/{ueId}/context-data/ee-subscriptions, causing it to pass validation and enter the normal create or query flow. Invalid identifiers can be persisted and retrieved as subscription records.

OpenDJ prior to 5.1.1 processes attacker-controlled credential objects in the JMX RMI connector before authentication without a restrictive credentials filter pattern, and RmiAuthenticator accepts an unconstrained Object array rather than a two-element String[]. When the JMX Connection Handler is enabled and reachable, an unauthenticated remote attacker can submit a crafted serialized Java object and achieve code execution. The issue is fixed in 5.1.1.

Ghostscript before 10.08.0 contains a heap-based buffer overflow in the JPEG 2000 output adapter (base/sjpx_openjpeg.c). An attacker can cause memory corruption by supplying a crafted PDF containing a JPEG 2000 image with mismatched component subsampling factors. The issue is fixed in version 10.08.0.

In Keyfactor SignServer before 7.6.0, several properties were identified to have no restrictions on what path they can be set to by an admin user. Setting these properties to specific file paths can reveal information to the client side. This includes ATTRIBUTESFILE in PKCS11CryptoToken, KEYSTOREPATH in KeyStoreCryptoToken, and TRUSTSTOREPATH in RenewalWorker.

In Keyfactor SignServer before 7.6.0, the ATTRIBUTESFILE attribute in PKCS11CryptoToken can be set to a readable file but not an accepted file. In this case, an error is thrown which also prints the file content to the application server log. This allows a user with both SignServer admin access and log read access to read files accessible by the local JBoss user.