Export limit exceeded: 427961 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 427961 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (427961 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-131018 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Confused deputy in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-130998 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Improper input validation in Parser in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially bypass web origin policy via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-131098 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Out of bounds read in V8 in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-65966 | 1 Pi-hole | 1 Ftl | 2026-11-18 | 3.5 Low |
| Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, validation in src/api/list.c permits spaces for GRAVITY_GROUPS and consequently skips carriage-return and line-feed validation for group names submitted through POST /api/groups. The unsanitized name is copied into the Location value in pi_hole_extra_headers, and CivetWeb interprets embedded CR/LF sequences as separate HTTP response headers. An authenticated administrator can therefore inject headers such as Set-Cookie, Location, or Cache-Control; when a browser processes the response, this can cause session fixation, attacker-controlled redirects, or cache behavior changes. This issue is fixed in version 6.7. | ||||
| CVE-2026-71304 | 1 Pi-hole | 1 Ftl | 2026-11-18 | 8.8 High |
| Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, check_client_auth() in src/api/auth.c detects that a matching session identifier has passed valid_until but still assigns user_id before the expired state can be rejected. That assignment sends execution through the authorized branch, renews valid_until for another timeout interval, and leaves the session-expired response unreachable. An attacker who possesses a previously valid session identifier can periodically reuse it to preserve administrative access indefinitely, making the configured session timeout ineffective. This issue is fixed in version 6.7. | ||||
| CVE-2025-62165 | 1 Pi-hole | 1 Ftl | 2026-11-18 | N/A |
| Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, CivetWeb permits unauthenticated clients to flood the WebUI login page and API invalid paths without connection or request-rate limits. Repeated requests can consume substantial CPU in request processing and session authentication, making the WebUI sluggish or unresponsive and potentially affecting the wider system and DNS service. Requests to selected invalid or redirecting paths also generate a log entry for each request, allowing network traffic to expand logs and exhaust constrained storage such as an SD card, while other request forms consume CPU without producing a corresponding request log. This vulnerability is fixed in 6.7. | ||||
| CVE-2026-65964 | 1 Pi-hole | 1 Ftl | 2026-11-18 | 6.6 Medium |
| Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. Prior to 6.7, log_http_access in src/webserver/webserver.c writes attacker-controlled User-Agent content to the access log without output neutralization when debug.api is enabled. If an administrator configures files.log.webserver inside webserver.paths.webroot with a filename matching lua_server_page_pattern, an unauthenticated request can plant Lua markup in that log and a later request can cause CivetWeb to evaluate the log as a Lua server page. The resulting commands run as the pihole operating-system user and can access or modify pihole-owned configuration, credentials, databases, logs, and rendered interface content. When the log is not served through the Lua handler, the same unneutralized writer still permits log forgery and downstream log-parser injection. This issue is fixed in version 6.7. | ||||
| CVE-2026-104796 | 1 Chevereto | 1 Chevereto | 2026-11-18 | 4.1 Medium |
| Chevereto before 4.5.8 contains a server-side request forgery vulnerability that allows authenticated administrators to cause the server to issue arbitrary requests by supplying a malicious URL to the uploadToWebsite function, which fetches the raw source via fetch_url before the Upload::checkValidUrl SSRF guard can be invoked. Attackers can target loopback addresses, RFC1918 internal services, cloud instance metadata endpoints, and file/gopher/dict schemes through the /json upload action to disclose internal responses or credentials when the fetched content is stored and served back as a public image URL. | ||||
| CVE-2026-63193 | 1 Octobercms | 1 October | 2026-11-18 | 5.5 Medium |
| October System provides the system module for October Content Management System. Prior to 3.7.18 and 4.3.2, the Media Library MediaManager::onCropImage and cropImage path accepts a user-controlled destination filename without applying the default_extensions allowlist enforced by the normal upload path. An authenticated backend user with media.library.create permission can upload arbitrary bytes under an allowed extension and use the zero-dimension crop branch, which performs a byte-for-byte File::copy, to write those bytes into the public media folder under an attacker-selected extension. Default server configurations block PHP execution in that folder, but HTML or SVG output can produce stored cross-site scripting in the application origin; non-default servers that execute PHP in the media directory can expose remote code execution. This vulnerability is fixed in 3.7.18 and 4.3.2. | ||||
| CVE-2026-103931 | 1 Corebunch | 1 Instatic | 2026-11-18 | 8.7 High |
| Instatic is an open source visual content management system for building static websites. Prior to 0.0.14, isSafeUrl() and safeUrl() in src/core/html-sanitize/index.ts remove tabs, newlines, carriage returns, and characters handled by String.prototype.trim(), but leave other leading C0 control characters that browsers discard before parsing a URL scheme. A low-privileged editor can place a dangerous URL behind one of those controls in a URL property or custom HTML attribute, allowing src/core/publisher/escapeProps.ts and the shared URL sanitizer to emit it into rendered content. When an Owner or Admin activates the element in the same-origin admin editor canvas, script executes with the victim's application authority and can drive admin APIs to read protected data, create an owner account, or install a plugin. This issue is fixed in version 0.0.14. | ||||
| CVE-2026-109549 | 1 Omnifaces | 1 Omnifaces | 2026-11-18 | 5.9 Medium |
| OmniFaces is a utility library for Faces. From 5.2 until 5.4.3, applications using <o:sse> or @Push(type=SSE) with session scope, view scope, or a user attribute can expose pushed messages because org.omnifaces.cdi.push.SseEndpoint#doGet accepts a channel identifier registered by SseChannelManager and PushSessionManager without verifying that the caller's HTTP session owns it. An attacker who obtains the victim's channel identifier from a logged URL, report, Referer header, or shared link can connect from a foreign or absent session and receive messages intended for the victim. Application-scoped channels are intentionally unbound, and this issue permits message receipt but not message injection. This issue is fixed in version 5.4.3. | ||||
| CVE-2026-114848 | 2 Oracle, Oracle Corporation | 3 Database - E Text, Database Server, Oracle Database Server | 2026-11-18 | 9.9 Critical |
| Vulnerability in the Oracle Text component of Oracle Database Server. Supported versions that are affected are 19.3-19.33, 21.3-21.24 and 23.4.0-23.26.3. Easily exploitable vulnerability allows low privileged attacker having Create Session privilege with network access via Oracle Net to compromise Oracle Text. While the vulnerability is in Oracle Text, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle Text. CVSS 3.1 Base Score 9.9 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). | ||||
| CVE-2026-58320 | 2026-11-18 | N/A | ||
| Missing Authorization vulnerability in the Apache Iggy server. The system snapshot command (GetSnapshot on the binary transports and POST /snapshot on HTTP) checked only that the caller was logged in, not the read_servers or manage_servers permission. Any authenticated user, including a user with no permissions, could download a diagnostic archive with the server log files, the host process list, a file system listing and the runtime server configuration. The runtime configuration contains the HTTP JWT signing secret and the message encryption key when they are set in the configuration. If HTTP is enabled, the user could use the signing secret to create tokens for any account, including root. This issue affects Apache Iggy: before 0.9.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue. | ||||
| CVE-2026-130491 | 2026-11-18 | N/A | ||
| In Eclipse versions 1.5-1.6.13, 2.0.0-2.0.22 and 2.1.0-2.1.2, the client library libmosquitto does not reject Will messages with payloads greater than 65535 bytes when calling `mosquitto_will_set()` or `mosquitto_will_set_v5()`. This results in up to 65535 bytes of uninitialised heap memory being transmitted as the Will. This can be mitigated by only passing payloads with a maximum length of 65535 bytes. | ||||
| CVE-2026-129705 | 2026-11-18 | N/A | ||
| In Eclipse Mosquitto versions 2.1.0 to 2.1.2, a broker with a listener that is configured to use the PROXY protocol v2 is vulnerable to an untrusted proxy providing details that cause the broker to accept fake SSL information. This can be mitigated by following the documented requirements for PROXY listeners: It is very important that only trusted proxies are allowed to connect to any listener using the PROXY protocol, and that clients are not allowed to connect to the listener at all. | ||||
| CVE-2026-129509 | 2026-11-18 | N/A | ||
| In the Apache Airflow Microsoft Azure provider 10.2.0 through 15.3.0, `S3ToAzureBlobStorageOperator` turned off TLS certificate verification for its connection to Amazon S3 by default (`s3_verify=False`), whatever the AWS connection's own verification settings were. An attacker positioned on the network between an Airflow worker and S3 could intercept that traffic, read the signed requests and alter the listed object keys and the copied file contents. Deployments are affected when a Dag uses `S3ToAzureBlobStorageOperator` without setting `s3_verify`. Users are advised to upgrade to apache-airflow-providers-microsoft-azure 15.3.1 or later, which uses the AWS connection's verification settings by default. | ||||
| CVE-2026-129149 | 2026-11-18 | N/A | ||
| In Eclipse Mosquitto versions 2.1.0 to 2.1.2, using the mosquitto_ctrl utility in interactive shell mode to interact with a malicious server could result in a crash of the utility if the server sent a hostile response. | ||||
| CVE-2026-126706 | 2026-11-18 | N/A | ||
| In Eclipse Mosquitto versions 2.1.0 to 2.1.2, the mosquitto_ctrl utility would crash if attempting to interact with a hostile broker and the broker sent a non-string "error" value. | ||||
| CVE-2026-110486 | 2026-11-18 | 9.8 Critical | ||
| In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with `protocol websockets` mishandles empty WebSocket data frames. `net__read_ws()` in `lib/net_ws.c` returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. The MQTT packet reader in `packet__read_single()` (`lib/packet_mosq.c`) trusts that return value as a payload byte count. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned `to_process` counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when `allow_anonymous false` is set. Combining the disclosure and the write allows remote code execution as the broker’s user by any client able to establish a session. | ||||
| CVE-2026-106096 | 1 Redhat | 2 Confidential Compute Attestation, Openshift | 2026-11-18 | 6.4 Medium |
| A flaw was found in CRI-O. When the optional Linux LinkLogs feature is enabled, the host pod log directory is bind-mounted into a pod emptyDir and is intended to be read-only, but Linux ignores MS_RDONLY on the initial bind and the CRI mount stays writable. A non-privileged UID 0 container can place a symlink at a future kubelet log path so that privileged conmon later appends attacker-controlled log data to an existing host file. This is an append-only host integrity issue, not universal remote code execution; LinkLogs is not enabled by default. | ||||