Export limit exceeded: 429072 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429072 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429072 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-128846 | 1 Fastify | 1 Fastify/busboy | 2026-11-18 | 3.7 Low |
| @fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 3.2.1 through 3.2.5, the parser can interpret the same multipart bytes differently depending on how they are split across socket reads: when the sequence that terminates a part's header block arrives split exactly at the configured header size limit, an off by one error drops the final header line, so a part declared as a binary file attachment is emitted as an ordinary text field instead of a file. A remote client controls both the multipart body and the header padding needed to reach the boundary and can influence segmentation, so an application that applies upload validation such as malware scanning or extension checks only to file events while trusting plain field values may process the payload through the wrong path. The parser level type confusion is fully reproducible, while the downstream validation bypass depends on the application. The issue is fixed in @fastify/busboy 3.2.6, which tracks how many terminator bytes were actually buffered when the limit is reached so a split terminator no longer corrupts the final header, and users should upgrade to 3.2.6 or later. As a workaround, apply the same validation to field values as to file uploads rather than treating file events as a trust boundary. | ||||
| CVE-2026-124724 | 1 Fastify | 1 Fastify/busboy | 2026-11-18 | 7.5 High |
| @fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 1.0.0 through 3.2.5, when a request reaches the configured limit on the number of multipart parts, each further part is skipped without attaching an error listener to the skipped part stream. If the request body ends in the middle of such a skipped part, the vendored Dicer parser emits an error on that stream, and because nothing is listening Node.js raises an unhandled error event and the process exits. A single crafted unauthenticated request is therefore enough to crash the server. The bug is latent in the parser on its own and was first demonstrated through @fastify/multipart versions 10.1.2 through 10.1.4, which keep feeding the request body to the parser after a limit error, and it affects any consumer that sets a finite parts limit and parses request bodies that can be terminated early. The issue is fixed in @fastify/busboy 3.2.6, and users should upgrade to 3.2.6 or later. There is no complete application level workaround because the crash happens inside the parser before application code runs, though consumers that set a finite parts limit should also attach an error listener to the parser stream. | ||||
| CVE-2026-61581 | 1 Datadog | 1 Datadog-agent | 2026-11-18 | 7.4 High |
| The Datadog Agent collects events and metrics from hosts and sends them to Datadog. Prior to datadog-apm-inject 0.66.0, the Datadog Single Step Instrumentation injector stores helper tooling in a predictable host directory. On Linux or Kubernetes systems with SSI enabled and at least one Java service instrumented through SSI, a local unprivileged attacker with shell access to the same host can influence that tooling and execute code with the privileges of the instrumented Java service. Services that use dd-java-agent without SSI and non-Java language runtimes are not affected. This issue is fixed in datadog-apm-inject 0.66.0. | ||||
| CVE-2026-75521 | 1 Mirendev | 1 Runtime | 2026-11-18 | N/A |
| Miren Runtime provides the runtime component for the Miren application platform. Prior to 0.11.1, the QUIC/HTTP3 RPC server on the default port 8443 uses tls.RequestClientCert and does not verify that presented certificates chain to the configured cluster certificate authority. The RPC authenticators derive a caller identity from PeerCertificates[0].Subject.CommonName without requiring a non-empty VerifiedChains value, and certificate identities bypass all RBAC checks. A network attacker who can reach the listener can present a self-signed certificate with an issuer distinguished name matching the public cluster CA subject and gain cluster superuser access, allowing disclosure, modification, or disruption of applications, sandboxes, disks, credentials, and other managed resources. This issue is fixed in version 0.11.1. | ||||
| CVE-2026-71481 | 1 Altcha-org | 1 Altcha-lib-php | 2026-11-18 | 7.5 High |
| ALTCHA PHP is a lightweight PHP library for creating and verifying ALTCHA challenges. From 2.0.0 until 2.0.3, the verifySolution method skips HMAC signature verification when a challenge payload omits the signature field, even when hmacSignatureSecret is configured. An attacker can remove the signature, supply attacker-selected low-difficulty challenge parameters, solve the resulting proof of work, and submit a payload that verifies successfully, bypassing the CAPTCHA control. This issue is fixed in version 2.0.3. | ||||
| CVE-2026-73864 | 1 Uhop | 1 Install-artifact-from-github | 2026-11-18 | 7.5 High |
| install-artifact-from-github installs prebuilt native artifacts hosted by GitHub without compiling them locally. Prior to 1.7.0, bin/install-from-cache.js downloads a native .node artifact, allows RE2_DOWNLOAD_MIRROR to select a source, follows HTTP redirects including HTTPS-to-HTTP downgrades, and writes the decompressed response to the artifact path without cryptographic integrity verification before writing or loading it. An attacker who controls a configured mirror, replaces a release asset, or can modify plaintext transport can supply native code that executes when the consumer loads the artifact. Version 1.7.0 adds SHA-256 verification for default-GitHub-source downloads when the consuming package publishes an artifactHashes bag; configured mirrors and packages without a bag remain outside that verification. | ||||
| CVE-2026-131096 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Missing authorization in Editing in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-131081 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Incorrect authorization in Media in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-131064 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Incorrect authorization in WebAppInstalls in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-131029 | 1 Google | 1 Chrome | 2026-11-18 | 8.1 High |
| Improper input validation in Extensions in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy into a privileged page via a crafted Chrome extension. (Chromium security severity: Low) | ||||
| CVE-2026-131028 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Incorrect authorization in WebAppInstalls in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-131027 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Observable discrepancy in Browser in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially obtain cross-origin data via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-131003 | 1 Google | 1 Chrome | 2026-11-18 | 8.1 High |
| Confused deputy in TabModel in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to bypass web origin policy via UI Interaction. (Chromium security severity: Medium) | ||||
| CVE-2026-130984 | 1 Google | 1 Chrome | 2026-11-18 | 8.1 High |
| Incorrect authorization in Canvas in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-130983 | 1 Google | 1 Chrome | 2026-11-18 | 8.1 High |
| Incorrect authorization in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy into a privileged page via a crafted Chrome extension. (Chromium security severity: Low) | ||||
| CVE-2026-130961 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Incorrect authorization in Media in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-130947 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Integer overflow in Autofill in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-130946 | 1 Google | 1 Chrome | 2026-11-18 | 8.1 High |
| Incorrect authorization in PerformanceAPIs 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: High) | ||||
| CVE-2026-130942 | 1 Google | 1 Chrome | 2026-11-18 | 3.1 Low |
| Observable discrepancy in Extensions in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to obtain cross-origin data via a crafted Chrome extension. (Chromium security severity: Medium) | ||||
| CVE-2026-130934 | 1 Google | 1 Chrome | 2026-11-18 | 3.1 Low |
| Incorrect authorization in Autofill in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to obtain cross-origin data via a crafted HTML page. (Chromium security severity: High) | ||||