Export limit exceeded: 26676 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430549 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430549 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-131219 | 1 Splunk | 1 Splunk App For Pci Compliance | 2026-11-20 | 3.7 Low |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in network traffic data. Another user who holds the "pci_user" role could later click the corresponding row in the Traffic Detail panel of the Network Traffic Activity report. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access data and perform actions available to that user. The vulnerability is possible because the Network Traffic Activity report does not treat network traffic values as literal search values when it builds the Traffic Detail drilldown search. For more information see Network Traffic Activity (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-reports/network-traffic-activity) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation. | ||||
| CVE-2026-131224 | 1 Splunk | 1 Splunk App For Pci Compliance | 2026-11-20 | 3.7 Low |
| In Splunk Enterprise Security versions below 8.7.0, a user that holds a role with the run_collect capability could store attacker-controlled values in data that populates the Endpoint Changes report. Another user who holds the "pci_analyst" role could later click a corresponding table row. Splunk Enterprise Security could then run attacker-controlled Search Processing Language (SPL) commands using the permissions of the user who clicked the row. The commands could access or modify data available to that user. The vulnerability is possible because the Endpoint Changes report does not treat dynamic report values as literal search values when it builds table-row drilldown searches. For more information see Reports (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/user-manual/8.7/using-the-splunk-app-for-pci-compliance/reports) and Configure users and roles (https://help.splunk.com/en/splunk-enterprise-security-8/splunk-app-for-pci-compliance/installation-and-configuration-manual/8.7/configure-the-app/configure-users-and-roles) in the Splunk documentation. | ||||
| CVE-2026-131302 | 1 Splunk | 1 Splunk Ai Assistant | 2026-11-20 | 4.3 Medium |
| In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could turn on the AI chat training-data consent setting through the Representational State Transfer (REST) API. The missing authorization is possible because the affected configuration endpoint does not enforce authorization checks. | ||||
| CVE-2026-131304 | 1 Splunk | 1 Splunk Ai Assistant | 2026-11-20 | 8.1 High |
| In Splunk AI Assistant versions below 2.0.0 a user who does not hold the "admin" or "power" Splunk roles could access data associated with another tenant and cause actions to be attributed to that tenant through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk AI Assistant accepted a client-controlled tenant identifier when selecting the authorization context for a request. | ||||
| CVE-2026-131305 | 1 Splunk | 1 Splunk Ai Assistant | 2026-11-20 | 8.1 High |
| In Splunk AI Assistant versions below 2.0.0, a user who does not hold the "admin" or "power" Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration. The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary. | ||||
| CVE-2026-104199 | 1 Yakifo | 1 Amqtt | 2026-11-20 | N/A |
| aMQTT is an open source MQTT broker and client. From 0.11.0 until 0.11.4, add_subscription() in amqtt/broker.py accepts malformed single-level + wildcard placement because it checks substrings instead of validating each slash-delimited level. The _matches() function converts each + into a greedy regular-expression fragment and evaluates it with re.fullmatch(), allowing a filter containing many adjacent + characters to trigger catastrophic backtracking when compared with a topic that partially matches but ultimately fails. Because matching runs synchronously in _run_broadcast(), one subscription followed by a publish can block the broker event loop, stopping message delivery and new connection processing until restart. Anonymous clients can trigger the issue with the default configuration. Any authenticated client permitted to create arbitrary subscriptions and publish messages may still exploit it when authentication is enabled. This issue is fixed in version 0.11.4. | ||||
| CVE-2026-133528 | 1 Beamng Gmbh | 1 Beamng.drive | 2026-11-20 | 8.6 High |
| BeamNG.drive before 0.40.6 contains an out-of-bounds write vulnerability because JIT-compiled LuaJIT traces omit FFI array bounds checks, letting untrusted Lua escape the sandbox. Attackers supplying a malicious mod can JIT-compile an FFI store loop, write out of range using a tostring() address leak, re-enable ffi.load, and run commands as the game user. | ||||
| CVE-2026-130652 | 1 Imagemagick | 1 Imagemagick | 2026-11-20 | 3.3 Low |
| ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability that allows attackers to read beyond allocated heap memory by triggering the -copy operation. Attackers can supply crafted images or arguments processed with -copy to crash the application or disclose adjacent heap memory contents. | ||||
| CVE-2026-130653 | 1 Imagemagick | 1 Imagemagick | 2026-11-20 | 3.3 Low |
| ImageMagick before 7.1.2-35 contains a policy bypass vulnerability that allows attackers to read from disallowed paths due to a missing policy check when decoding MPC files. Attackers can supply crafted MPC files that reference restricted locations to access files the configured security policy should block. | ||||
| CVE-2026-130661 | 1 Imagemagick | 1 Imagemagick | 2026-11-20 | 5.3 Medium |
| ImageMagick before 7.1.2-35 contains a policy bypass vulnerability in the ASE decoder caused by a missing security policy check. Attackers can supply crafted ASE files that evade configured resource policies to cause excessive memory usage and denial of service. | ||||
| CVE-2026-133274 | 1 Vanhauser-thc | 1 Thc-hydra | 2026-11-20 | 6.5 Medium |
| THC-Hydra through 9.7 contains a stack buffer overflow vulnerability in analyze_server_response() of hydra-http-form.c that allows malicious HTTP servers to corrupt memory via crafted Set-Cookie headers. Attackers can send a Set-Cookie header with an extra leading space followed by a repeated cookie name, causing a negative strncpy length that overflows tmpcookie and crashes Hydra. | ||||
| CVE-2026-133276 | 1 Pydantic | 1 Pydantic | 2026-11-20 | 5.3 Medium |
| When extra data is allowed (extra=Extra.allow), providing a __pydantic_initialised__ key when validating a Pydantic V1 dataclass makes it considered as already validated, resulting in field values not being validated. The __init__() method of Pydantic V1 dataclasses stores all the provided keyword arguments in the instance __dict__ before validation, so a __pydantic_initialised__ keyword argument overrides the internal flag used to skip validation of already validated instances. As a result, data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into Pydantic V1 dataclasses allowing extra data. The issue was fixed in Pydantic 1.10.27. Users relying on the pydantic.v1 namespace in Pydantic V2 should upgrade to 2.14.2 or later. | ||||
| CVE-2026-47278 | 1 Frappe | 1 Frappe | 2026-11-20 | N/A |
| Frappe is a full-stack web application framework. Prior to 15.108.0 and 16.18.3, the add_comment handler in frappe/templates/includes/comments/comments.py trusts the client-provided comment_by and comment_email fields. A caller can submit chosen identity metadata that is stored with a comment, causing the comment to appear to originate from another name or email address. This issue is fixed in versions 15.108.0 and 16.18.3. | ||||
| CVE-2026-130964 | 1 Google | 1 Chrome | 2026-11-20 | 8.1 High |
| 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-130962 | 2 Apple, Google | 2 Iphone Os, Chrome | 2026-11-20 | 8.1 High |
| Incomplete cleanup in Navigation in Google Chrome on on iOS prior to 158.0.8127.36 allowed a remote attacker to potentially bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-130666 | 1 Imagemagick | 1 Imagemagick | 2026-11-20 | 5.3 Medium |
| ImageMagick before 7.1.2-35 contains a policy bypass vulnerability that allows attackers to evade resource limits because a policy check is missing when reading XMP profiles. Attackers can supply an image with a crafted XMP profile to trigger excessive memory usage and cause denial of service. | ||||
| CVE-2026-130670 | 1 Imagemagick | 1 Imagemagick | 2026-11-20 | 3.3 Low |
| ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability that allows attackers to read beyond allocated memory when BGRO image data is imported. Attackers can supply crafted BGRO data for processing to crash the application or leak adjacent heap memory contents. | ||||
| CVE-2026-130684 | 2 Vllm, Vllm-project | 2 Vllm, Vllm | 2026-11-20 | 5.4 Medium |
| vLLM before 0.33.0 contains a path traversal vulnerability that allows malicious model publishers to redirect the served model and tokenizer by setting speculators_config verifier.name_or_path in config.json. Attackers can point this field at another local checkpoint directory to leak its tokenizer vocabulary via unauthenticated /detokenize requests and gain query access to private models. | ||||
| CVE-2026-133113 | 1 Gogs | 1 Gogs | 2026-11-20 | 6.5 Medium |
| Gogs through 0.14.4 contains an authorization bypass vulnerability that allows collaborators with write access to push to protected branches by merging pull requests. Because MergePullRequest skips branch protection checks and PullRequest.Merge omits hook environment variables, attackers can merge commits into branches restricted to allowlisted users. | ||||
| CVE-2026-133169 | 1 Modified-shop | 2 Modified-shop, Modified Ecommerce Shopsoftware | 2026-11-20 | 4.8 Medium |
| modified eCommerce Shopsoftware through 3.3.0 contains a stored cross-site scripting vulnerability that allows authenticated administrators to inject scripts via the unsanitized products_model field. Attackers with product editing permission can store JavaScript that executes in browsers of other administrators, storefront visitors, and customers viewing carts and order history. | ||||