Overview 112,709 matches · 4,921 in Waratek scope · 484 protected · 1,768 exploited · 576 CISA KEV · 2,660 public PoC · 773 EPSS ≥ 0.5
112,709matches
4,921in Waratek scope4.4%
484protected0.4%
1,768exploited1.6%
576CISA KEV0.5%
2,660public PoC2.4%
773EPSS ≥ 0.50.7%
Protected by Waratek
484
0.4%
Rule in development
3
0.0%
Mitigation candidate
67
0.1%
No exploit published
4,367
3.9%
Outside Waratek scope
585
0.5%
Not applicable
107,203
95.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
484
0.4%
partly blocked
0
0.0%
not blocked
112,224
99.6%
not established
1
0.0%
unrecorded
0
0.0%
split by
peak 42,181 / year
20207,782
Protected by Waratek66
Mitigation candidate9
No exploit published326
Outside Waratek scope106
Not applicable7,275
High7,782
blocked by ARMR today66
not blocked7,716
Exploited144
Working exploit published249
Proof of concept only90
Forecast only35
No public exploit7,264
20218,770
Protected by Waratek47
Mitigation candidate11
No exploit published293
Outside Waratek scope144
Not applicable8,275
High8,770
blocked by ARMR today47
not blocked8,723
Exploited213
Working exploit published124
Proof of concept only84
Forecast only86
No public exploit8,263
202210,337
Protected by Waratek77
Rule in development1
Mitigation candidate7
No exploit published246
Outside Waratek scope110
Not applicable9,896
High10,337
blocked by ARMR today77
not blocked10,260
Exploited175
Working exploit published173
Proof of concept only1,182
Forecast only41
No public exploit8,766
202311,637
Protected by Waratek70
Mitigation candidate13
No exploit published272
Outside Waratek scope78
Not applicable11,204
High11,637
blocked by ARMR today70
not blocked11,566
not established1
Exploited233
Working exploit published174
Proof of concept only1,923
Forecast only59
No public exploit9,248
202415,332
Protected by Waratek47
Mitigation candidate13
No exploit published196
Outside Waratek scope59
Not applicable15,017
High15,332
blocked by ARMR today47
not blocked15,285
Exploited324
Working exploit published146
Proof of concept only2,422
Forecast only57
No public exploit12,383
202516,670
Protected by Waratek27
Rule in development2
Mitigation candidate3
No exploit published182
Outside Waratek scope39
Not applicable16,417
High16,670
blocked by ARMR today27
not blocked16,643
Exploited263
Working exploit published217
Proof of concept only2,705
Forecast only7
No public exploit13,478
202642,181
Protected by Waratek150
Mitigation candidate11
No exploit published2,852
Outside Waratek scope49
Not applicable39,119
High42,181
blocked by ARMR today150
not blocked42,031
Exploited416
Working exploit published179
Proof of concept only7,367
Forecast only2
No public exploit34,217
2020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-96771 | High | 2026-11-20 | Not applicable | No public exploit | The Hydrogen Calendar Embeds plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via ICS Feed Event Fields (SUMMARY/DESCRIPTION/LOCATION) in all versions up to, and including, 3.0.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the attacker to have write access to an ICS feed that has been configured as a calendar source on the target WordPress site. |
| CVE-2026-89095 | High | 2026-11-20 | Not applicable | No public exploit | The Shortcodes and extra features for Phlox theme plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.17.22 via the 'extra_template_path' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. The slug-based allowlist introduced as the fix for CVE-2023-37888 constrains only the template_part_file filename suffix and does not validate the extra_template_path directory component, meaning path traversal sequences are fully functional against this parameter. |
| CVE-2026-133710 | High | 2026-11-20 | Not applicable | No public exploit | llama.cpp b11003 before b12556 contains an integer overflow in the hrm_text loader load_arch_hparams() that allows attackers to bypass the block count check using crafted GGUF metadata. Attackers can supply a GGUF model whose layer factors wrap modulo 2^32, causing load_arch_tensors() to write tensor pointers past model.layers, corrupting heap memory and potentially enabling code execution. |
| CVE-2026-133708 | High | 2026-11-20 | Not applicable | No public exploit | diffpy.structure before 3.5.1 contains a code execution vulnerability that allows attackers to run Python code by supplying crafted CIF symmetry operations passed to eval() in get_symop(). Attackers can embed expressions in the _space_group_symop_operation_xyz or _symmetry_equiv_pos_as_xyz loop to execute code with victim privileges when the CIF file is parsed locally. |
| CVE-2026-133707 | High | 2026-11-20 | Not applicable | No public exploit | The targets R package before 1.12.1 contains a code execution vulnerability that allows attackers to run arbitrary R code by planting format functions in the data store metadata file. Attackers can supply a crafted _targets data store whose custom format or CAS repository functions are passed to eval(parse()), executing code when victims call tar_read(), tar_load() or tar_workspace(). |
| CVE-2026-133705 | High | 2026-11-20 | Not applicable | No public exploit | Hanko before 3.2.0 contains an open redirect vulnerability in Saml.IsAllowedRedirect that allows unauthenticated attackers to bypass the redirect allowlist by appending attacker-controlled domain suffixes to allowed hostnames. Attackers can lure victims through a crafted /saml/auth login link to capture the one-time hanko_token and redeem it without PKCE to hijack the victim's session. |
| CVE-2026-133665 | High | 2026-11-20 | Not applicable | No public exploit | flowintel contains an information disclosure vulnerability that allows authenticated non-administrative users to access sensitive configuration data and logs intended for administrators only. The notification page and alert API responses exposed sensitive fields, including webhook URLs, signing secrets, IMAP credentials, and delivery logs, in the initial data or JSON responses. Although the user interface hid the configuration form from non-admin users, the underlying data remained accessible via the page source or API endpoints. This exposure included historical webhook URLs that may contain active bearer tokens. An attacker with a valid non-admin account could retrieve these credentials and logs, potentially leading to unauthorized access to notification services, impersonation of the application in webhook deliveries, or further lateral movement within the infrastructure. Affected versions: flowintel < 4.1.0 |
| CVE-2026-133663 | High | 2026-11-20 | Not applicable | No public exploit | flowintel contains an Insecure Direct Object Reference (IDOR) vulnerability affecting multiple endpoints that manage child records of cases and tasks. An authenticated user with access to one case or task could read or modify records belonging to other cases by supplying identifiers of those records directly in the request. Affected operations include: - Reading task notes, subtasks, and URL tools by referencing their IDs without verifying they belong to the authorized task - Retrieving task assignees for a task belonging to a different case - Editing or deleting timeline events and timeline event links belonging to another case - Editing or removing case connectors belonging to another case - Invoking connector module operations (MISP, generic connectors, worker calls) by combining an authorized case with a connector link from a different case The root cause is that the application authorized the parent resource (case or task) in the URL but then fetched or operated on the child record independently without verifying the child's ownership relationship to the authorized parent. Security impact: an authenticated user can exfiltrate sensitive threat intelligence data from cases they do not have access to, and can modify or delete timeline entries, connector configurations, and other records in unauthorized cases, leading to data integrity loss and potential disruption of incident response workflows. Affected versions: flowintel prior to 4.1.0 |
| CVE-2026-133662 | High | 2026-11-20 | Not applicable | No public exploit | flowintel contains multiple authorization bypass vulnerabilities in its Analyzer (MISP Modules) functionality, affecting both the web interface and the REST API. - Saving analyzer results to a case or task accepted caller-supplied case and task identifiers without verifying that the authenticated user is a member of the target case or holds the required restricted-task permissions. An authenticated user could write notes, create tasks, and attach MISP objects or attributes into another organization's case. - Stored analyzer results were retrievable by UUID by any authenticated user. Both the web endpoint and the API endpoint returned the full result payload without checking ownership, exposing another user's analysis output. - The save handler did not validate the structure of the request, did not reject conflicting destination selections, and did not halt processing when a task-note operation failed, allowing partial or unintended writes. Preconditions: the attacker must possess a valid authenticated session (or API token) in flowintel. No administrative role is required. Security impact: unauthorized cross-tenant data disclosure (analyzer results) and unauthorized cross-tenant data modification (notes, tasks, MISP objects/attributes in another organization's case). Affected versions: flowintel prior to 4.1.0. |
| CVE-2026-133660 | High | 2026-11-20 | Not applicable | No public exploit | FlowIntel contains an authorization bypass in its user directory and assignment endpoints that allows authenticated users to access data belonging to other organisations. When the LIMIT_USER_VIEW_TO_ORG setting is enabled to restrict directory visibility to the caller's organisation, several API endpoints (user lookup by ID, last name, Matrix ID, and role-based listings) did not consistently enforce the organisation boundary. An authenticated non-admin user could retrieve profiles of users in other organisations by supplying their identifiers. Additionally, OrgAdmin users could retrieve the task assignments of any user in the system, including tasks and case titles from private cases to which they had no access. The assignment endpoints did not verify that the requested user belonged to the caller's organisation or that the underlying cases were visible to the caller. Security impact: - Exposure of user identities (names, Matrix IDs, roles) across organisation boundaries - Disclosure of task assignments, case titles, and workflow details from private cases - Potential enumeration of other organisations' membership and case activity Affected versions: FlowIntel prior to 4.1.0 |
| CVE-2026-133659 | High | 2026-11-20 | Not applicable | No public exploit | Flowintel contains multiple SSO identity and organisation trust boundary violations that collectively allow account takeover, privilege escalation, and unauthorized access to private case data. - Keycloak SSO accepted unverified email claims, and all SSO providers (Keycloak, Entra ID, SimpleSAML) could resolve a claimed email address to an existing account that was created via a different sign-in method, enabling cross-provider account collision and unauthorized access to another user's account and data. - Entra ID role mapping relied on group display names, which tenant members could duplicate by creating a group with the same name as a privileged group (e.g. FlowintelAdmin), resulting in unauthorized role escalation. - SSO provisioning reused organisations whose display names matched user-controlled profile names, granting the new SSO user access to that organisation's private cases without explicit administrator assignment. - Case sharing via the API resolved organisations by name using a first-match query, so ambiguous names could silently resolve to the wrong organisation. Preconditions: an attacker must have a valid SSO identity (Keycloak, Entra ID, or SimpleSAML) or be a member of the relevant Entra tenant. No local administrator access is required. Security impact: unauthorized access to private case data, privilege escalation to Editor or higher roles, and account takeover across authentication providers. Affected versions: Flowintel prior to 4.1.0. |
| CVE-2026-133652 | High | 2026-11-20 | Not applicable | No public exploit | Flowintel , contained a session management vulnerability in its browser authentication mechanism. The session identifier used a bare numeric user ID rather than a credential-bound token, resulting in several related weaknesses: - Remembered logins (remember-me cookies) remained valid after a user changed their password, allowing an attacker holding a previously issued cookie to retain access indefinitely. - Server-side session identifiers were not rotated upon login (local, SSO, or remembered), enabling session fixation. - Self-service email and password changes did not require verification of the current password, permitting an attacker with an active session to modify account credentials without knowledge of the existing password. - Administrator-initiated password resets did not revoke other browser sessions, invalidate remembered logins, or rotate the affected user's API key. An attacker who obtained a valid session or remember-me cookie (e.g., through XSS, network interception, or cookie theft) could maintain unauthorized access even after the legitimate user changed their password. Additionally, an attacker with any valid session could change the account's email address or password without knowing the current credentials, effectively taking over the account. Affected versions: Flowintel prior to 4.1.0. |
| CVE-2026-133631 | High | 2026-11-20 | Not applicable | No public exploit | FlowIntel contains multiple security flaws in its note variable resolution, chatbot API tooling, and AI report generation. - Note variable references (e.g. cross-case or cross-task lookups) were resolved using the viewing user's privileges rather than the destination case's audience. An authenticated user with access to a shared or imported note could embed references to private cases, causing sensitive case data to be pulled into AI report requests, exports, and MISP sends without the referenced case's audience having granted read access. - The chatbot API tool permitted the language model to invoke any FlowIntel API endpoint, including administrative routes and state-changing GET operations, without an allow-list or path validation. An attacker who can influence the model's instructions (e.g. via untrusted case content) could induce data modification or access restricted endpoints. - AI report generation passed the Ollama bearer token and full case content as command-line arguments to a child process, exposing them in the system process table to any local user. Affected versions: FlowIntel prior to 4.1.0. |
| CVE-2026-133626 | High | 2026-11-20 | Not applicable | No public exploit | FlowIntel contains a resource exhaustion vulnerability in its file-to-note conversion feature. When a user converts an attached CSV or JSON file into a case note, the application renders the data as a Markdown table by padding every row to the maximum column count. A crafted file with a small number of filled cells but a very large number of columns (or keys) causes the application to allocate a quadratic number of padded table cells, potentially exhausting a worker process in memory or CPU. The same issue affects nested JSON values rendered inside table cells, where pretty-printed indentation further inflates the output size. Preconditions: - An authenticated user with access to a case in FlowIntel - Ability to attach and convert a CSV or JSON file to a note Impact: - Denial of service: exhaustion of a worker process, potentially disrupting service for other users - No confidentiality or integrity impact Affected versions: FlowIntel prior to 4.1.0 |
| CVE-2026-133577 | High | 2026-11-20 | Not applicable | No public exploit | A flaw was found in the Kuadrant WebAssembly (WASM) shim shipped in Red Hat Connectivity Link 1.5. When a TokenRateLimitPolicy is attached to an HTTPRoute that also has an AuthPolicy - or when a RateLimitPolicy with defaults or overrides is attached to the Gateway or listener of such routes - the shim's action pipeline fails to dispatch the authentication guard at request time, and the request is forwarded upstream. Unauthenticated requests return 200 OK instead of 401, and neither authentication nor rate limiting is enforced. Both policies continue to report Enforced, leaving no status-level indication of the failure. |
| CVE-2026-133553 | High | 2026-11-20 | Not applicable | No public exploit | A flaw was found in crun. When copying files onto a tmpfs mounted with tmpcopyup, crun opens the destination a second time by name. A container that shares a writable volume with the container being created can change that path between the two lookups, so crun copies image files onto host files, including files under /proc/sys. |
| CVE-2026-133534 | High | 2026-11-20 | Not applicable | No public exploit | PowerLink developed by Neotroni Lighting has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read database contents. |
| CVE-2026-131804 | High | 2026-11-20 | Not applicable | No public exploit | The Seraphinite Accelerator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'HTTP_USER_AGENT' parameter in all versions up to, and including, 2.31 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that an administrator has previously enabled the 'Enable logging' and 'HTTP trace' diagnostic options in the plugin's Advanced → Debug settings, both of which are disabled by default. |
| CVE-2026-131797 | High | 2026-11-20 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Imran Tauqeer CubeWP Forms cubewp-forms allows DOM-Based XSS.This issue affects CubeWP Forms: from n/a through 1.1.12. |
| CVE-2026-131795 | High | 2026-11-20 | Not applicable | No public exploit | Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in thembay Aora aora allows PHP Local File Inclusion.This issue affects Aora: from n/a through 1.3.5. |
| CVE-2026-131645 | High | 2026-11-20 | Not applicable | No public exploit | The Kognetiks Chatbot plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 2.5.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The TeX payload survives WordPress core comment kses intact because it contains no HTML tags, and MathJax is active on fresh installs by default due to the 'chatbot_chatgpt_enable_mathjax' option defaulting to 'Yes' with no page or shortcode presence guard on enqueue. |
| CVE-2026-131582 | High | 2026-11-20 | Not applicable | No public exploit | The PagBank / PagSeguro e Vindi para WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'customer.name' parameter in all versions up to, and including, 5.1.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload can be planted via the legitimate hosted-checkout (Checkout PB) flow simply by entering it as a customer name on PagBank's payment page, requiring no hash brute-forcing whatsoever; the woocommerce_api_rm_ps_notif webhook path is additionally exploitable because its only gate is a 5-character (20-bit) truncated wp_hash() that is trivially brute-forceable. |
| CVE-2026-131167 | High | 2026-11-20 | Not applicable | No public exploit | pretix offloads certain processes to background tasks that are run by a different server to avoid HTTP workers being clogged with processes that take longer than a usual web request. The browser periodically polls the server to see if the task is already finished using a UUID-shaped task ID. Once the task is completed, pretix resumes to the next step of the operation based on the result of the task. The system does however not check if the result stems from the correct type of task. Therefore, an attacker can supply the UUID of a task of a different type and pretix will continue with the result from the wrong task. In most cases, this will just result in an error because the return types do not match up, but in some cases this can be abused to extract objects the attacker usually should not see. Specifically, a vector was discovered that allowed to abuse this for unauthorized access to other people's ticket purchases. The attacker can, however, not control which purchases they get access to. |
| CVE-2026-131163 | High | 2026-11-20 | Not applicable | No public exploit | A stored XSS in pretix-adyen has been discovered where an attacker could configure his own ticket shop in a way that API calls are not made to Adyen, but an attacker-controlled server. Results of these API calls would then be embedded in a part of the shop without proper escaping, leading to full XSS including potential session takeover. |
| CVE-2026-130813 | High | 2026-11-20 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Liquid Web / StellarWP GiveWP give allows Reflected XSS.This issue affects GiveWP: from n/a through 4.19.2. |
| CVE-2026-130494 | High | 2026-11-20 | Not applicable | No public exploit | An improper firmware authenticity verification vulnerability exists in the affected Ethernet Switches products. An authenticated remote attacker with administrative privileges could exploit the lack of cryptographic signature verification to install unauthorized firmware, potentially leading to arbitrary code execution on the affected device. |
| CVE-2026-130493 | High | 2026-11-20 | Not applicable | No public exploit | A hard-coded cryptographic key vulnerability exists in affected Ethernet swiches. The use of a shared cryptographic key with insufficient key strength could allow an unauthenticated remote attacker, under certain conditions, to impersonate affected devices and potentially compromise the confidentiality and integrity of communications. |
| CVE-2026-130055 | High | 2026-11-20 | Not applicable | No public exploit | The VidShop for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.10.0 via the /vsfw/v1/products/{id} REST API endpoint. This is due to the endpoint's permission_callback (check_public_permission) returning true unconditionally and the get_item() handler only checking that the product and video exist — it does not check the product's post_status or catalog visibility, nor does it verify that the product is actually linked to the supplied video_id. This makes it possible for unauthenticated attackers to enumerate product IDs and read private, draft, and catalog-hidden WooCommerce products' names, short descriptions, prices, variations, attributes, and stock information that would otherwise be hidden from public view. |
| CVE-2026-130010 | High | 2026-11-20 | Not applicable | No public exploit | The Chatterbug Forms – Fast, Flexible WordPress Form Builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the cbforms_delete_uploaded_files function in all versions up to, and including, 1.1 This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). Exploitation requires an administrator to delete the attacker-planted form entry, and the attacker must know or be able to guess the absolute path of a file writable by the PHP process. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. |
| CVE-2026-129972 | High | 2026-11-20 | Not applicable | No public exploit | A buffer overflow vulnerability exists in the web management service of the Ethernet Remote I/Os products. An unauthenticated remote attacker could exploit insufficient bounds checking of specially crafted HTTP requests, potentially causing the web management service to crash and resulting in a denial-of-service condition. |
| CVE-2026-129971 | High | 2026-11-20 | Not applicable | No public exploit | A buffer overflow vulnerability exists in the SNMP service of the Ethernet Remote I/Os products. An unauthenticated remote attacker could exploit improper handling of specially crafted SNMP requests, potentially leading to a denial-of-service condition on the affected device. |
| CVE-2026-129840 | High | 2026-11-20 | Not applicable | No public exploit | In the nrfconnect/ncs-zigbee repository, the GitHub Actions workflow .github/workflows/build_documentation.yml used the pull_request_target trigger while checking out and executing untrusted pull request code. This allowed a pull request from a fork to run attacker-controlled code in the base repository context with a write-scoped GITHUB_TOKEN (contents: write, pages: write, pull-requests: write), enabling remote code execution in CI, token exfiltration, and unauthorized modification of repository content and GitHub Pages. The workflow was disabled and then rewritten to remove the issue. |
| CVE-2026-129423 | High | 2026-11-20 | Not applicable | No public exploit | Joomla Extension - phoca.cz - Stored XSS through author website in frontend upload in Phoca Download extension 3.0.6-6.1.6 - The author website field of the frontend upload form was validated with an overly permissive URL check and rendered without escaping, allowing users with frontend upload permission to inject HTML attributes into the file and category views. |
| CVE-2026-129327 | High | 2026-11-20 | Not applicable | No public exploit | The Apaczka.pl WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '_apaczka[<id>][error_messages] (and sibling subkeys inside _apaczka[])' parameter in all versions up to, and including, 1.4.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable during WooCommerce classic guest checkout because WooCommerce's legacy order storage fires the save_post action with the checkout $_POST still populated, giving unauthenticated attackers a direct write path to order post meta without an authenticated session. |
| CVE-2026-129075 | High | 2026-11-20 | Not applicable | No public exploit | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Imran Tauqeer CubeWP Forms cubewp-forms allows DOM-Based XSS.This issue affects CubeWP Forms: from n/a through 1.1.12. |
| CVE-2026-129065 | High | 2026-11-20 | Not applicable | No public exploit | Missing Authorization vulnerability in Backup For WP WP Database Backup wp-database-backup allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Database Backup: from n/a through 7.14. |
| CVE-2026-129036 | High | 2026-11-20 | Not applicable | No public exploit | Incorrect Privilege Assignment vulnerability in weDevs WP ERP erp allows Privilege Escalation.This issue affects WP ERP: from n/a through 1.17.11. |
| CVE-2026-129015 | High | 2026-11-20 | Not applicable | No public exploit | Improper Restriction of XML External Entity Reference vulnerability in ReviewX ReviewX reviewx allows XML Entity Linking.This issue affects ReviewX: from n/a through 3.0.1. |
| CVE-2026-128915 | High | 2026-11-20 | Not applicable | No public exploit | Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in InstaWP InstaWP Connect instawp-connect allows Blind SQL Injection.This issue affects InstaWP Connect: from n/a through 0.1.4.4. |
| CVE-2026-128102 | High | 2026-11-20 | Not applicable | No public exploit | The rtMedia for WordPress, BuddyPress and bbPress plugin for WordPress is vulnerable to generic SQL Injection via the 'custom_fields' parameter in all versions up to, and including, 4.7.17 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The upload endpoint's only access control is a nonce check, and the 'rtmedia_upload_nonce' value is localized to every unauthenticated visitor on every front-end page via wp_enqueue_scripts, making it freely obtainable without an account. |
| CVE-2026-127112 | High | 2026-11-20 | Not applicable | No public exploit | The Events Made Easy plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'event[event_notes]' parameter in all versions up to, and including, 3.3.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is only exploitable when the plugin's 'Allow guest submit?' Frontend Submit option is enabled, though the required nonce is freely obtainable by any anonymous visitor as it is printed on every frontend page. |
| CVE-2026-126716 | High | 2026-11-20 | Not applicable | No public exploit | The Mega Forms – Drag & Drop Form Builder with Multi-Step & Conditional Logic plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_entry function in all versions up to, and including, 1.7.9 This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The attacker-supplied path is stored via the unauthenticated form submission endpoint, but the actual file deletion only occurs when an administrator subsequently deletes the stored entry — a routine housekeeping action that serves as the detonation trigger. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own. |
| CVE-2026-125094 | High | 2026-11-20 | Not applicable | No public exploit | The Optimole – Optimize Images | Convert WebP & AVIF | CDN & Lazy Load | Image Optimization plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.2.19 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the AMP plugin to be active in Transitional or Standard template mode, and comments must be open on the target post, which is the WordPress default. |
| CVE-2026-125085 | High | 2026-11-20 | Not applicable | No public exploit | The Nexter Extension – Security, Performance, Code Snippets & Site Toolkit plugin for WordPress is vulnerable to Privilege Escalation in versions up to, and including, 4.9.0 This is due to the role_switcher_to_view_admin_as() function handling the `reset-view` branch without a capability check or nonce when the caller's own login is supplied, combined with an incomplete cleanup hook (maybe_prevent_switchback_to_administrator) that exits early when the user's current roles equal the stored view role and that is never triggered when WordPress core's WP_User::set_role() short-circuits because the account already has only the target role. This makes it possible for authenticated attackers, with subscriber-level access and above, to elevate their privileges to Administrator. |
| CVE-2026-125080 | High | 2026-11-20 | No exploit published | No public exploit | Improper neutralization of special elements in data query logic (Cypher injection) in the orderBy placeholder handling for custom queries in Neo4j Spring Data Neo4j versions 6.1.0 through 8.0.8 and 8.1.0 through 8.1.2 allows a remote attacker to read database contents via blind reads, write read content into new nodes, or, if APOC and APOC file export are enabled, to write query results to a file in the database's accessible file system via crafted sort order parameters. Exploitation requires an application that passes unvalidated user input as the orderBy value to a custom Cypher query using the placeholder directive. |
| CVE-2026-125059 | High | 2026-11-20 | Not applicable | No public exploit | The Mang Board plugin for WordPress is vulnerable to Arbitrary File Deletion via Path Traversal in versions up to, and including, 2.4.8 via the `file_path` column handled by the `mbw_board_files_api_body()` function. The plugin stores an attacker-supplied value directly into the files admin table (no realpath, dot-segment, or directory-containment filtering) and later concatenates it onto `MBW_UPLOAD_PATH` before passing the result to `@unlink()`. This makes it possible for unauthenticated attackers to delete arbitrary files on the affected site's server, including `wp-config. |
| CVE-2026-124768 | High | 2026-11-20 | Not applicable | No public exploit | Authorization bypass via a user-controlled key in XOneManager 3.8.3.0. The 'ConvertBDToProject' operation selects the database based on 'databasename' without verifying the user’s permissions on it. An authenticated user can link a project to a database outside their scope and identify existing databases based on API responses. |
| CVE-2026-124767 | High | 2026-11-20 | Not applicable | No public exploit | Authorization bypass in the creation of projects in XOneManager 3.8.3.0. The server processes POST requests to ‘/xmanagercore/api/Project/ConvertBDToProject/’ without verifying the administrative role. An authenticated user with basic privileges can create a project and execute SQL queries on the linked database from that project. |
| CVE-2026-121985 | High | 2026-11-20 | Not applicable | No public exploit | The FV Flowplayer Video Player plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 7.5.57.7212 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the plugin's 'Parse Vimeo and YouTube links' setting to be enabled, which wires do_shortcode into the comment_text filter chain and allows the [fvplayer] shortcode to be rendered from comment content. |
| CVE-2026-121790 | High | 2026-11-20 | Not applicable | No public exploit | The CWILL (Formerly ParcelPanel) – Shipment Tracking, Tracking & Order Tracking for WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'data[].courier_code, data[].tracking_number (plus pp_sign for the auth bypass)' parameter in all versions up to, and including, 4.6.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The authentication bypass is reachable only when the parcelpanel_api_key WordPress option is non-empty, which occurs automatically once an admin has opened or connected the ParcelPanel admin page; at that point any unauthenticated attacker can bypass the sole access gate by supplying a JSON boolean true as pp_sign, which PHP's loose == operator coerces to true when compared against the non-empty md5 hex string. |
| CVE-2026-120556 | High | 2026-11-20 | Not applicable | No public exploit | The Toocheke Companion plugin for WordPress is vulnerable to Missing Authorization leading to arbitrary post and attachment deletion in versions up to, and including, 2.38. This is due to a missing object-level capability check in the toocheke_tapas_ajax_cleanup_start() and toocheke_tapas_ajax_cleanup_step() AJAX handlers; the toocheke_tapas_cleanup_ajax_guard() method only verifies the primitive delete_posts capability (held by every Contributor) and never calls current_user_can('delete_post', $post_id) or delete_others_posts before passing the attacker-supplied series_post_id to wp_delete_post() and wp_delete_attachment() with force-delete enabled. The required nonce is emitted on the Import: Tapas admin page, which is gated only by edit_posts, so a Contributor can read it. This makes it possible for authenticated attackers, with Contributor-level access and above, to permanently delete any importer-created series post, every child 'comic' post attached to it, and every Media Library attachment belonging to those posts — regardless of which user originally created them. |
| CVE-2026-120508 | High | 2026-11-20 | Not applicable | No public exploit | The Charitable – Donation & Fundraising Platform (Donation Forms, Recurring Donations & Fundraising Campaigns) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'stripe_payment_method' parameter in all versions up to, and including, 1.8.15.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The nonce required to reach the nopriv AJAX endpoint is publicly obtainable from any rendered campaign donation form, making exploitation trivially accessible to unauthenticated visitors on sites with Stripe configured as a payment gateway. |
| CVE-2026-119611 | High | 2026-11-20 | Not applicable | No public exploit | The NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting in versions up to, and including, 4.5.5 via the 'ajax_pagination_referrer' request parameter used on the /ngg_tag/<tag>/ taxonomy page. This is due to the plugin reading the pagination base URL from $_REQUEST, preserving the attacker-supplied host on the tag route (where ngg_wprouting_add_post_permalink is forced to false so the plugin does not re-base the links to the site's own permalink), and caching the fully rendered page in a transient keyed only on the request URI (not the request body) for 1800 seconds via NGG_RENDERING_CACHE / PHOTOCRATI_CACHE. This makes it possible for unauthenticated attackers to poison the cached /ngg_tag/<tag>/ page so that its pagination links point to an attacker-controlled host; the plugin's own ajax_pagination. |
| CVE-2026-118522 | High | 2026-11-20 | Not applicable | No public exploit | The Video & Photo Gallery for Ultimate Member plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to, and including, 1.1.4 This is due to the um_gallery_add_videos() AJAX handler persisting user-supplied videos[] values into the file_name column after only esc_url() — which preserves path-traversal sequences — and the companion um_gallery_delete_photo() helper passing that stored value to unlink() through get_user_image_path() with no canonicalization or allowed-directory check. This makes it possible for authenticated attackers, with Subscriber-level access and above, to delete arbitrary files on the server, which can be leveraged to achieve remote code execution when the right file (such as wp-config. |
| CVE-2026-116550 | High | 2026-11-20 | Not applicable | No public exploit | The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 4.5.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the plugin's "What must the lightbox be applied to?" setting (thumbEffectContext) to be configured as "Try to apply to all images" or "Try to apply to all images that link to image files," which is not the shipping default, and also requires the attacker's comment to reach a publicly rendered state. |
| CVE-2026-113347 | High | 2026-11-20 | Not applicable | No public exploit | Multiple products produced by Ruijie Networks Co., Ltd. contain an OS command injection vulnerability that may lead to arbitrary OS commands being executed by an attacker with the administrative privilege. |
| CVE-2026-109387 | High | 2026-11-20 | Not applicable | No public exploit | The Photo Gallery, Sliders, Proofing and Themes – NextGEN Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'IPTC 2#120 (caption) / 2#005 (title) inside the image file' parameter in all versions up to, and including, 4.5.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an authenticated user with image-edit permissions to import an attacker-supplied image file, which is the plugin's standard workflow for photographer uploads, client galleries, and contest submissions. |
| CVE-2026-105074 | High | 2026-11-20 | Not applicable | No public exploit | Cross-Site Request Forgery (CSRF) vulnerability in ShortPixel ShortPixel Image Optimizer shortpixel-image-optimiser allows Cross Site Request Forgery.This issue affects ShortPixel Image Optimizer: from n/a through 6.6.1. |
| CVE-2026-104927 | High | 2026-11-20 | Not applicable | No public exploit | The King Addons for Elementor – 100+ Elementor Widgets, 4 000+ Elementor Templates, WooCommerce Builder, Mega Menu, Popup Builder plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 51.1.89. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to read arbitrary post meta values — including private contact data, API keys, license keys, and plugin-internal metadata — for any published post by supplying an arbitrary meta key name via the unauthenticated AJAX endpoint. The nonce check present in the handler provides no effective barrier because the nonce is emitted into every front-end page for logged-out visitors via wp_localize_script. |
| CVE-2026-99320 | High | 2026-11-19 | Not applicable | No public exploit | In the Linux kernel, the following vulnerability has been resolved: ipv6: raw: fix use-after-free in rawv6_send_hdrinc() rawv6_send_hdrinc() caches the route before handing the skb to l3mdev_ip6_out(). The VRF output path may replace skb->dst and release the original route, leaving the cached pointer stale. The function later dereferences that pointer for statistics accounting and as the output device passed to NF_HOOK(). Its RCU read-side critical section starts after l3mdev_ip6_out(), so it cannot prevent the old route from being reclaimed in between. Reload the route from the current skb destination after l3mdev_ip6_out() returns. KASAN reports a slab-use-after-free in rawv6_sendmsg(), with the route allocated by ip6_dst_alloc(), freed by dst_destroy() from rcu_core(), and the related RCU callback queued from vrf_l3_out(). |
| CVE-2026-93917 | High | 2026-11-19 | Not applicable | No public exploit | An improper authorization vulnerability in WatchGuard Dimension's device management registration process allows an attacker who controls one enrolled managed device's credentials to take over another managed device's identity. This allows the attacker to receive the victim device's queued configuration and apply attacker-supplied configurations under the victim device's identity. |
| CVE-2026-93916 | High | 2026-11-19 | Not applicable | No public exploit | An insufficient session expiration vulnerability in WatchGuard Dimension's administrator session management allows an attacker holding a valid Super Administrator WebUI session to retain full Super Administrator privileges after that account has been downgraded or deleted by another administrator. |
| CVE-2026-93915 | High | 2026-11-19 | Not applicable | No public exploit | A missing authorization vulnerability in WatchGuard Dimension's legacy system settings configuration handler allows a low-privileged authenticated user to execute arbitrary commands with elevated privileges on the underlying OS. |
| CVE-2026-93914 | High | 2026-11-19 | Not applicable | No public exploit | An improper input validation vulnerability in WatchGuard Dimension's database snapshot restore feature allows an authenticated Dimension Administrator to execute arbitrary operating system commands as root by uploading a specially crafted database snapshot archive. |
| CVE-2026-93912 | High | 2026-11-19 | Not applicable | No public exploit | A code injection vulnerability in WatchGuard Dimension's log notification processing allows an authenticated managed device, or an attacker in possession of a valid device logging key, to achieve arbitrary code execution on the Dimension appliance. |
| CVE-2026-93911 | High | 2026-11-19 | Not applicable | No public exploit | A SQL injection vulnerability in WatchGuard Dimension's log collection service allows an authenticated managed device, or an attacker in possession of a valid device logging key, to achieve arbitrary code execution on the Dimension appliance. |
| CVE-2026-87868 | High | 2026-11-19 | Not applicable | No public exploit | MRemoteNG uses single MD5 hash with no salt and no iterations for key-derivation. An attacker who obtains the encrypted data can brute-force a weak or moderate passphrase offline at extreme speed and then decrypt every stored connection password. When the default passphrase is in use, no cracking is needed at all; the key is derived from a publicly known value. Vendor did not provide the range of vulnerable versions. Only version 1.76.20 was tested and confirmed vulnerable. Other versions may also be vulnerable. |
| CVE-2026-87867 | High | 2026-11-19 | Not applicable | No public exploit | MRemoteNG establishes encrypted but unauthenticated channel with Microsoft SQL Server backend. Client accepts any certificate the server presents, including a self-signed certificate supplied by an attacker. An attacker positioned between the client and the SQL server (for example via ARP/DNS spoofing) can transparently pintercept the connection (man-in-the-middle) and read all traffic, including the encrypted connection-password table read and the database login. Vendor did not provide the range of vulnerable versions. Only version 1.76.20 was tested and confirmed vulnerable. Other versions may also be vulnerable. |
| CVE-2026-86126 | High | 2026-11-19 | Not applicable | No public exploit | A Cross-Site Request Forgery (CSRF) vulnerability in WatchGuard Dimension's user management interface allows a remote, unauthenticated attacker to create a persistent local Super Administrator account by tricking an authenticated Super Administrator into visiting a malicious web page. |
| CVE-2026-85776 | High | 2026-11-19 | Not applicable | No public exploit | The WP Duplicate – WordPress Migration Plugin plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 1.1.11. This is due to a missing capability check and missing nonce check on the start_zip_creation, start_zip_download, local_sync_get_init_root_files, and local_sync_get_files_by_key AJAX actions in the start_zip_creation_dev() and sibling functions. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite the plugin's prod_site_url setting so it points at an attacker-controlled host and enumerate arbitrary server directories, which when combined with a subsequent administrator-triggered sync results in an unsigned attacker-supplied ZIP archive being fetched, extracted via a WordPress-independent bridge deployed under the web root, resulting in remote code execution on the affected site. |
| CVE-2026-85018 | High | 2026-11-19 | Not applicable | No public exploit | IBM Guardium Data Protection 12.2 is vulnerable to improper TLS certificate validation in the GDP Terraform provider, allowing a network attacker with a man-in-the-middle position to intercept sensitive credentials transmitted to the Guardium appliance. |
| CVE-2026-84998 | High | 2026-11-19 | Not applicable | No public exploit | The NextScripts: Social Networks Auto-Poster plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'comment_author' and 'comment_agent' Comment Fields in all versions up to, and including, 4.4.8 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload executes in an administrator's browser session when the administrator views the WordPress comment moderation queue, including pending and unapproved comments, meaning no prior approval of the comment is required for exploitation. |
| CVE-2026-84273 | High | 2026-11-19 | Not applicable | No public exploit | IBM Guardium Data Protection 12.2 is vulnerable to path traversal in the datasource functionality. An authenticated attacker could exploit this vulnerability to delete arbitrary files on the appliance. |
| CVE-2026-84087 | High | 2026-11-19 | Not applicable | No public exploit | IBM Guardium Data Protection 12.2 is vulnerable to local privilege escalation via the SUID-root podman_wrapper binary on the Collector appliance. A local attacker with low-privileged access to the Collector can exploit insufficient argument validation in the SUID binary to execute arbitrary commands as root, resulting in full compromise of the Collector appliance. |
| CVE-2026-82950 | High | 2026-11-19 | Not applicable | No public exploit | The device only supports Wi-Fi protocols vulnerable to deauthentication attacks (WEP/WPA/WPA2). Should any event which would typically be logged to the user’s mobile device (such as arming or disarming the alarm or any tamper events) be incurred whilst the device is temporarily disconnected from its Wi-Fi network (such as via a deauthentication attack), those alerts will not be sent even after connection is regained. |
| CVE-2026-82949 | High | 2026-11-19 | Not applicable | No public exploit | The static codes used for information transmission throughout the 433.92 MHz system of the Guardian 2 system allow an attacker in proximity to monitor the movements of users inside the premises where the sensors are set up. This is further aided by the fact that codes transmitted reveal sensor type, although sensor location cannot be inferred from this traffic alone. |
| CVE-2026-82948 | High | 2026-11-19 | Not applicable | No public exploit | The Guardian 2 alarm unit lacks a mechanism to authenticate control commands sent over 433.92 MHz, which allows an attacker to replay the static commands to impersonate activity. The attacker can also disarm or arm the system at will if a Nexsmart keypad (product link) is in use, thus compromising the functionality of the alarm system completely. |
| CVE-2026-82342 | High | 2026-11-19 | Not applicable | No public exploit | IBM Guardium Data Protection 12.2 is vulnerable to a stack-based buffer overflow when processing a specially crafted PROXY protocol v1 header. A remote attacker can exploit this vulnerability to cause a denial of service or potentially execute arbitrary code. |
| CVE-2026-81430 | High | 2026-11-19 | Not applicable | No public exploit | A vulnerability in WatchGuard Dimension's system upgrade process allows an authenticated administrator to create or overwrite arbitrary files on the appliance filesystem by uploading a specially crafted upgrade archive. |
| CVE-2026-77318 | High | 2026-11-19 | Not applicable | Proof of concept only | Jupyter MCP Server is a Model Context Protocol server for Jupyter. Prior to 1.0.3, standalone streamable-http mode can enforce MCP_TOKEN on /mcp while leaving the state-changing /api/connect and /api/stop management routes unauthenticated. An unauthenticated network caller can use /api/connect to replace runtime_url and document_url values and their tokens, reset ServerContext, and start a kernel client against attacker-controlled infrastructure, causing the server to send Jupyter API and WebSocket traffic to that backend. The caller can also use /api/stop to stop the current notebook kernel. This boundary failure does not require explicit insecure no-auth mode and occurs outside normal MCP JSON-RPC tool dispatch. This issue is fixed in version 1.0.3. |
| CVE-2026-77316 | High | 2026-11-19 | Not applicable | No public exploit | Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, validate_url_ssrf() in src/core/utils.py validates one DNS answer and then returns the hostname, while guarded_aiohttp_request(), enforce_outbound_url(), and validate_url_with_env_config() allow the outbound connection to perform an independent second lookup. A caller with control of the hostname's DNS can make validation see a public address and make the connection see an internal address, bypassing the guard across its outbound consumers and exposing readable internal or metadata-service responses. The attack requires low or zero DNS TTL behavior and a successful timing-dependent answer change; static multiple-address answers are checked and do not provide the same bypass. This issue is fixed in version 2.26.8. |
| CVE-2026-77315 | High | 2026-11-19 | Not applicable | No public exploit | Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, http.paginate in src/core/modules/atomic/http/paginate.py validates only the initial base_url, and _paginate_link_header then follows a server-supplied Link: rel="next" URL without calling the SSRF guard again. A low-privileged caller can make an allowed first page point the next request at an internal or metadata service, causing a readable second-order SSRF whose response body is aggregated into all_items and returned. This issue is fixed in version 2.26.8. |
| CVE-2026-77313 | High | 2026-11-19 | Not applicable | No public exploit | Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, validate_url_ssrf in src/core/utils.py resolves and checks a hostname but returns the hostname URL rather than the validated address, and session.get in http.get performs an independent DNS lookup when connecting. A low-privileged caller with control of the hostname's DNS can make the first lookup return a public address and the connection-time lookup return an internal address, bypassing the SSRF guard for all modules that call it and exposing readable internal or metadata-service responses. Successful exploitation requires attacker-controlled DNS and a successful timing-dependent answer change between the two lookups. This issue is fixed in version 2.26.8. |
| CVE-2026-76544 | High | 2026-11-19 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause scheduled metric alert searches to run arbitrary Search Processing Language (SPL) commands and access credentials stored in cleartext. This requires at least one non-internal metric index on the instance. The vulnerability is possible because Splunk Enterprise does not fully validate metric alert filter input before using it in a scheduled search. |
| CVE-2026-76540 | High | 2026-11-19 | Not applicable | No public exploit | In Splunk Enterprise versions below 9.4.17, 10.0.12, 10.2.9, and 10.4.5, a user who does not hold the "admin" or "power" Splunk roles can configure a metric alert through the Representational State Transfer (REST) API that runs a search with elevated privileges. The vulnerability lets the user access or modify data and disrupt the Splunk Enterprise instance. The vulnerability occurs because Splunk Enterprise does not enforce the required role-based authorization when it processes metric alert configuration through the REST API. Splunk Enterprise schedules the resulting search with elevated authorization and runs attacker-controlled search processing with that authorization. For more information see About configuring role-based user access (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.6/manage-splunk-platform-users-and-roles/about-configuring-role-based-user-access) in the Splunk documentation. |
| CVE-2026-76538 | High | 2026-11-19 | Not applicable | No public exploit | In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.16, a user who does not hold the "admin" or "power" Splunk roles could cause Splunk Enterprise to run arbitrary Search Processing Language (SPL) searches with elevated privileges through data model acceleration. The vulnerability is possible because Splunk Enterprise does not correctly neutralize caller-supplied data model acceleration values before it places them into generated summarization searches. |
| CVE-2026-69261 | High | 2026-11-19 | Not applicable | No public exploit | Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS may forward a Cookie header after an HTTP redirect to a host other than the one for which the header was intended. That unintended host can therefore receive cookies containing credentials or other confidential values. Authorization headers are never forwarded to inappropriate hosts and are not the affected secret in this vulnerability. This issue is fixed in version 3.8.1. |
| CVE-2026-69260 | High | 2026-11-19 | Not applicable | No public exploit | Git LFS is a Git extension for versioning large files. From 0.5.0 until 3.8.1, Git LFS does not format the SSH URL path component as a single argument when constructing remote object-transfer or authentication commands. Shell metacharacters in the SSH URL can therefore escape the intended path argument and cause arbitrary command execution when the remote Git LFS service passes received commands to a shell without adequate sanitization. Git LFS also incorrectly encodes default HTTPS URLs when an SSH URL is configured and the remote host either does not support Git LFS remote commands over SSH or supports HTTP authentication over SSH but git-lfs-authenticate does not return an explicit HTTP URL. This issue is fixed in version 3.8.1. |
| CVE-2026-63390 | High | 2026-11-19 | Not applicable | No public exploit | HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, the BCF reader can experience an integer overflow in a record-length check that verifies whether a record contains enough bytes for the expected number and size of stored items. A crafted BCF record can bypass this check, causing reads beyond the stored data and, in some cases, writes beyond the heap buffer when the reader sets the least significant bit of accessed bytes. Opening such a file can crash the process, corrupt data or heap structures, and may permit arbitrary code execution. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24. |
| CVE-2026-63202 | High | 2026-11-19 | No exploit published | No public exploit | netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, BinaryHttpParser.readFieldSection in codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java loops while fieldSectionLength is nonzero and relies on disabled-by-default assertions to require BinaryHttpParser.readFieldLine to return a value and consume bytes. A corrupt field line can consume more bytes than its understated declared section length and drive the counter negative, or a truncated field line can return without consuming data and leave the parser in the same state. An unauthenticated OHTTP peer can encrypt such Binary HTTP content under the gateway public configuration, reach OHttpRequestResponseContext.ContentDecoder.decodeChunk, and permanently pin a Netty event-loop thread at full CPU before application business logic. Multiple requests can exhaust the event-loop group and deny service until restart. This issue is fixed in version 0.0.23.Final. |
| CVE-2026-63124 | High | 2026-11-19 | No exploit published | No public exploit | netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, BinaryHttpParser.readFieldLine in codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java treats a complete field line that ends exactly at a known field-section boundary as incomplete and returns without consuming bytes. BinaryHttpParser.readFieldSection then leaves fieldSectionLength unchanged and repeats the loop because its forward-progress checks are Java assertions, which are normally disabled in production. A remote peer that sends a known-length Binary HTTP header or trailer section ending at that boundary can make the parser spin indefinitely and pin the Netty event-loop or worker thread responsible for the channel. This issue is fixed in version 0.0.23.Final. |
| CVE-2026-62955 | High | 2026-11-19 | Not applicable | No public exploit | baserCMS is a website development framework. From 5.2.3 until 5.3.0, BcThemeFileService::getFullpath() in plugins/bc-theme-file/src/Service/BcThemeFileService.php skips its path containment check when realpath() fails for a nonexistent theme subdirectory selected by the type parameter. An authenticated administrator can supply a traversal path through the theme-file API to access locations outside the theme directory. The bypass of the CVE-2026-30940 fix can permit file writes, overwrites or deletion within the PHP process permissions and, where executable PHP can be written, remote code execution. This issue is fixed in 5.3.0. |
| CVE-2026-62258 | High | 2026-11-19 | Not applicable | No public exploit | HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, the CRAM decoder validates the 254-character query-name limit only after decoding the name into a 1024-byte stack array. An attacker-controlled CRAM record can provide an overlong query name and overflow the local stack buffer before the later validation runs; all CRAM format versions are affected. Opening such a file can crash the process, corrupt stack data, and may permit arbitrary code execution. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24. |
| CVE-2026-62257 | High | 2026-11-19 | Not applicable | No public exploit | HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, the experimental CRAM v4 XPACK and XRLE decoders cache expanded block pointers at indexes beyond the 512-element slice->block_by_id array. An array index partially controlled by data in the input file first causes an out-of-bounds read to determine whether a block is cached; a null value then causes allocation of a block and an out-of-bounds pointer write to the same element. The invalid read may crash the process, while the write may corrupt heap state and could permit arbitrary code execution. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24. |
| CVE-2026-62256 | High | 2026-11-19 | Not applicable | No public exploit | HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, fai_retrieve does not verify that the line width recorded in a FASTA .fai index is greater than or equal to the number of bases per line. When the line width is exactly one less than the base count, retrieval allocates an undersized heap buffer and writes one byte beyond its end; larger discrepancies instead cause an allocation failure that is handled. This issue can corrupt heap memory and crash the process. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24. |
| CVE-2026-62255 | High | 2026-11-19 | Not applicable | Proof of concept only | HTSlib is a library for reading and writing bioinformatics file formats. Prior to 1.21.2, 1.22.3, 1.23.2, and 1.24, cram_index_load does not verify that the number of reference sequences in a CRAM .crai index does not exceed the CRAM header reference count. A malformed index can drive unbounded index-array allocation, and when the number of references in the index is within two of INT_MAX, the growth calculation can wrap, read beyond a heap buffer, and use the resulting value as a pointer for an unchecked memory write. Any region query can trigger the flaw, causing denial of service or memory corruption. This issue is fixed in versions 1.21.2, 1.22.3, 1.23.2, and 1.24. |
| CVE-2026-61827 | High | 2026-11-19 | No exploit published | No public exploit | netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, BinaryHttpParser does not enforce limits on encoded variable-length fields controlled by a remote peer. A remote peer can cause the decoder to buffer data indefinitely until memory is exhausted, causing denial of service. This issue is fixed in version 0.0.23.Final. |
| CVE-2026-61798 | High | 2026-11-19 | No exploit published | No public exploit | netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, BoringSSLAsymmetricCipherKeyPair.toString in codec-ohttp-hpke-classes-boringssl/src/main/java/io/netty/incubator/codec/hpke/boringssl/BoringSSLAsymmetricCipherKeyPair.java includes its private parameter, BoringSSLAsymmetricKeyParameter.toString in codec-ohttp-hpke-classes-boringssl/src/main/java/io/netty/incubator/codec/hpke/boringssl/BoringSSLAsymmetricKeyParameter.java renders the complete private-key byte array when isPrivate is true, and BoringSSL.EVP_HPKE_KEY_init_or_throw in codec-ohttp-hpke-classes-boringssl/src/main/java/io/netty/incubator/codec/hpke/boringssl/BoringSSL.java includes rejected privateKeyBytes in an exception message. Applications that log affected key-pair objects or initialization exceptions can persist complete HPKE private key material in logs or telemetry. Anyone who can read those records can recover the key and may compromise OHTTP message confidentiality or authenticity expectations while the key remains usable. This issue is fixed in version 0.0.23.Final. |
| CVE-2026-59988 | High | 2026-11-19 | Not applicable | No public exploit | django-docutils provides reStructuredText support for Django. Prior to 0.30.0, public rendering paths including publish_doctree, publish_html_from_source, publish_html_from_doctree, publish_parts_from_doctree, the {% rst %} template tag, the rst template filter, DocutilsTemplates, and DocutilsView pass lower-trust reStructuredText to Docutils without disabling file_insertion_enabled, raw_enabled, ambient docutils.conf processing, or unsafe URI schemes and without consistently sanitizing doctrees. An attacker who can influence rendered reStructuredText can use include or csv-table directives to read local files or cause server-side URL requests, or use raw HTML and unsafe URI output to inject stored script-capable content. Applications that render only trusted static reStructuredText are not affected unless attackers can influence it. This issue is fixed in version 0.30.0. |
| CVE-2026-22311 | High | 2026-11-19 | Not applicable | No public exploit | The failed-login limiter of the JTL-Wawi synchronisation interface of JTL-Shop derives the client identity from the client-controlled X-Forwarded-For header and counts requests without credentials as failed logins. An unauthenticated remote attacker can block the synchronisation between JTL-Shop and JTL-Wawi with a few requests and repeat this indefinitely, so that orders are no longer handed over to JTL-Wawi. No data is disclosed and no code is executed. |