Schwachstellen, die jetzt zählen.

fastnetmon: FastNetMon: Denial of Service via race condition in IPv6 traffic monitoring

github.com/kubeflow/pipelines: Kubeflow Pipelines: Cross-tenant data disclosure via missing namespace in execution cache keys

github.com/kubeflow/pipelines: Kubeflow Pipelines: Information disclosure via default proxy signing key

github.com/kubeflow/pipelines: Kubeflow Pipelines: Unauthorized modification of shared pipelines via authorization bypass

github.com/kubeflow/pipelines: Kubeflow Pipelines: Information disclosure via SQL injection in pagination token handling

github.com/kubeflow/pipelines: Kubeflow Pipelines: Server-Side Request Forgery via unrestricted pipeline URL fetching

filelock: filelock: unauthorized concurrent access via insecure claim directory permissions

filelock: filelock: Denial of Service (DoS) via symbolic link race condition

filelock: filelock: Denial of Service via Windows opportunistic lock on lock markers

filelock: filelock: Denial of service via pre-created SQLite side files

filelock: filelock: Denial of Service via improper lock file permissions on Windows

@modelcontextprotocol/server: @modelcontextprotocol/server: Information disclosure via shared HTTP transport instance

The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 2.0.0 until 2.3.0 in @modelcontextprotocol/server, applications that shared one stateless HTTP transport or one McpServer or Server instance among multiple clients could deliver responses and notifications to the wrong client. The affected surface is an MCP server reached over HTTP by multiple clients. The trigger is reuse of one stateless…

@modelcontextprotocol/sdk: @modelcontextprotocol/server: Model Context Protocol TypeScript SDK: Denial of service via memory exhaustion from crafted HTTP…

The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 1.3.0 until 1.32.0 in @modelcontextprotocol/sdk and from 2.0.0 until 2.3.0 in @modelcontextprotocol/server, HTTP servers did not enforce a limit on the number of array elements and object keys validated in one request. The affected surface is validation of HTTP requests containing arrays or object keys. The trigger is an array-element or…

@modelcontextprotocol/sdk: @modelcontextprotocol/client: Model Context Protocol TypeScript SDK: Sensitive information disclosure via cross-origin redirects

The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. Prior to 1.32.0 in @modelcontextprotocol/sdk and from 2.0.0 until 2.3.0 in @modelcontextprotocol/client, the HTTP client transports and OAuth client requests followed redirects to a different origin while retaining custom request headers and, for HTTP 307 or 308 responses, request bodies. The affected surfaces are StreamableHTTPClientTransport…

@modelcontextprotocol/sdk: @modelcontextprotocol/server: @modelcontextprotocol/express: @modelcontextprotocol/server-legacy: Model Context Protocol TypeScript…

The Model Context Protocol TypeScript SDK provides TypeScript client and server implementations of the Model Context Protocol. From 1.6.0 until 1.32.0 in @modelcontextprotocol/sdk, from 2.0.0 until 2.3.0 in @modelcontextprotocol/server, from 2.0.0 until 2.0.2 in @modelcontextprotocol/express, and from 2.0.0 until 2.3.1 in @modelcontextprotocol/server-legacy, server-side bearer authentication could accept a valid access token issued for a different service because the SDK did…

oauthlib: oauthlib: Authentication bypass via missing device code validation

OAuthLib is an implementation of the OAuth request-signing logic for Python 3.6+. From 3.3.0 until 4.0.1, OAuthLib's RFC 8628 device workflow does not require DeviceCodeGrant.validate_token_request to check that the device_code parameter is present and valid. A caller whose client request is accepted by the configured validator and who knows a valid client ID enabled for the device workflow can submit a missing or bogus device code to the token endpoint and obtain a bearer…

russh: russh: Cryptographic restriction bypass via signature algorithm mismatch

altair: Altair: Cross-site scripting via crafted iframe sandbox URL

Altair is a GraphQL client for all platforms. From 7.2.4 until 8.5.8, packages/altair-iframe-sandbox/src/main.ts reads plugin_sandbox_opts from the iframe-sandbox query string and passes attacker-controlled scriptUrls to injectScript() in packages/altair-core/src/utils/inject.ts, which creates script elements in the page. The intended parent iframe flow places the page in an iframe with sandbox allow-scripts and without allow-same-origin, but direct navigation to a crafted…

@graphql-tools/utils: @graphql-tools/utils: Prototype pollution via unvalidated incremental response path segments

@angular/common: @angular/common: Cross-Site Request Forgery token leakage via URL parsing discrepancy

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.34 and 21.0.3, the @angular/common HttpClient function xsrfInterceptorFn uses a regular expression that does not normalize request URLs in the same way as the browser's WHATWG URL parser. With XSRF protection enabled, a mutating HTTP request to an attacker-controlled URL containing backslashes, stripped control characters or…

black: Black: Arbitrary code execution via unvalidated version specification in GitHub Action

Black is the uncompromising Python code formatter. Prior to 26.10.1, the Black GitHub Action with use_pyproject: true accepts tool.black.required-version from pyproject.toml without validating that it is a released Black version specifier. An attacker who can submit a pull request can change that field to a direct reference to attacker-controlled code, causing the workflow to install and execute the code in the victim repository's GitHub Actions context. This issue is fixed…

github.com/caddyserver/caddy: caddy: Hop-by-hop header leakage via improper protocol upgrade response handling

Caddy is an extensible server platform that uses TLS by default. Prior to 2.11.5, the reverse proxy's finalizeResponse method in modules/caddyhttp/reverseproxy/reverseproxy.go handles an upstream 101 Switching Protocols response before running removeConnectionHeaders and the hopHeaders deletion loop used for ordinary responses. The early return invokes handleUpgradeResponse, which copies the upstream headers to the client and normalizes only WebSocket-specific header names…

DSA-6615-1 libreoffice - security update

LibreOffice includes a dBASE database driver, which reads dBASE tables and their .ndx index files when a folder of dBASE files is used as a data source. A heap buffer overflow existed when an index page was read. The number of entries recorded in a page was not checked against the number of entries the page could hold, which comes from a different field of the index header. A crafted index could also make a page refer back to itself, so that reading it recursed without end…

ImageMagick: Mehrere Schwachstellen

ImageMagick: ImageMagick: Denial of Service via infinite loop in SVG decoding

github.com/mark3labs/mcp-go: mcp-go: Unauthorized access via improper OAuth metadata validation

noname: noname: Arbitrary code execution via unauthenticated local file server

noname Electron desktop build v1.11.2 through v1.11.6.1 contains an unauthenticated local file server with wildcard CORS that allows malicious websites to read, overwrite, or delete installation files. Attackers can send cross-origin requests to /writeFile on localhost port 8089 to overwrite renderer scripts, executing JavaScript with Node.js access as the local user.

accel-ppp: accel-ppp: Denial of Service via heap buffer overflow in logging targets

accel-ppp before 1.15.0 contains a heap buffer overflow vulnerability in the tcp, syslog and pgsql log targets that allows unauthenticated remote peers to overflow fixed heap buffers by producing log lines exceeding LOG_MAX_SIZE. Attackers within client-ip-range can send an L2TP Start-Control-Connection-Request with many string AVPs when verbose logging is enabled to corrupt heap memory and crash the daemon.

github.com/goposta/posta: Posta: Server-side request forgery via arbitrary webhook URLs

Posta before v0.18.0 contains a server-side request forgery vulnerability that allows authenticated users with edit rights to make the backend send POST requests to internal destinations by creating webhooks with arbitrary URLs. Attackers can target loopback, private-network or cloud metadata addresses and read delivery status codes and error strings to probe internal hosts and ports.

neuron: neuron: Denial of Service via crafted model dataset

NEURON (CoreNEURON) through 9.0.2 contains a stack buffer overflow vulnerability that allows attackers to corrupt stack memory by supplying over-long tokens in a crafted model dataset. Attackers can place oversized version or mechanism-name tokens in bbcore_mech.dat, globals.dat, or files.dat loaded by nrniv-core to crash the process.

vrpn: vrpn: Denial of Service via out-of-bounds stack write

VRPN through 07.36 contains an out-of-bounds stack write vulnerability in vrpn_Endpoint::handle_sender_message() and handle_type_message() that allows unauthenticated remote peers to write outside a stack buffer via an unchecked length index. Attackers can connect, complete the version-cookie exchange, and send a SENDER_DESCRIPTION or TYPE_DESCRIPTION message with an out-of-range or negative index to crash the process.