Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429303 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-21609 | 1 Atlassian | 2 Jira Service Management, Jira Service Management Data Center | 2026-11-18 | N/A |
| This High severity Improper Authorization vulnerability was introduced in versions 5.12.0, 10.3.0, and 11.3.0 of Jira Service Management Data Center. This Improper Authorization vulnerability, with a CVSS Score of 7.1, allows an authenticated attacker to gain unintended access and can lead to the exposure of resources or functionality, possibly providing attackers with sensitive information or even execute arbitrary code. Atlassian recommends that Jira Service Management Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Jira Service Management Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 Jira Service Management Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://confluence.atlassian.com/servicemanagement/jira-service-management-release-notes-780083086.html). You can download the latest version of Jira Service Management Data Center from the download center (https://www.atlassian.com/software/jira/service-management/download-archives). This vulnerability was reported via our Bug Bounty program. | ||||
| CVE-2026-21603 | 1 Atlassian | 2 Jira Data Center, Jira Software Data Center | 2026-11-18 | N/A |
| This High severity Stored XSS vulnerability was introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center. This Stored XSS vulnerability, with a CVSS Score of 8.4, allows an authenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser. Atlassian recommends that Jira Core Data Center and Jira Software Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Jira Core Data Center and Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 * Jira Core Data Center and Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version of Jira Core Data Center and Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/download-archives). This vulnerability was reported via our Penetration Testing program. | ||||
| CVE-2026-21602 | 1 Atlassian | 2 Jira Data Center, Jira Software Data Center | 2026-11-18 | N/A |
| This High severity Stored XSS vulnerability was introduced in version 10.3.26 of Jira Core Data Center and Jira Software Data Center. This Stored XSS vulnerability, with a CVSS Score of 7.4, allows an authenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser. Atlassian recommends that Jira Core Data Center and Jira Software Data Center customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Jira Core Data Center and Jira Software Data Center 10.3: Upgrade to a release greater than or equal to 10.3.27 * Jira Core Data Center and Jira Software Data Center 11.3: Upgrade to a release greater than or equal to 11.3.13 See the release notes (https://www.atlassian.com/software/jira/download-archives). You can download the latest version of Jira Core Data Center and Jira Software Data Center from the download center (https://www.atlassian.com/software/jira/download-archives). This vulnerability was reported via our Penetration Testing program. | ||||
| CVE-2026-119793 | 1 Libp2p | 2 Gossipsub, Libp2p | 2026-11-18 | 7.5 High |
| libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 17.0.0, the @libp2p/gossipsub default configuration allows a connected remote peer to submit unsigned subscription RPC metadata for arbitrarily many distinct topic strings. handleReceivedSubscription in packages/gossipsub/src/gossipsub.ts creates a persistent topics-map entry for each accepted topic, while allowedTopics is unset by default, decodeRpc maxSubscriptions limits only one RPC rather than aggregate topic bytes, and peer scoring has no subscription-volume penalty. A single peer can therefore grow the topics map and committed heap toward out-of-memory conditions, and disconnecting additionally causes removePeer to scan all accumulated topic entries. This issue is fixed in version 17.0.0. | ||||
| CVE-2026-130776 | 1 Lxc | 1 Incus | 2026-11-18 | 7.1 High |
| Incus before 7.6.0 contains an information disclosure vulnerability that allows clients with project event-view access to read migration websocket secrets broadcast in operation metadata. Attackers can connect to in-flight migration control and fs websockets before the legitimate peer, hijacking the transfer to obtain instance configuration and filesystem data. | ||||
| CVE-2026-130779 | 1 Lxc | 1 Incus | 2026-11-18 | 9.6 Critical |
| Incus before 7.6.0 contains a path traversal vulnerability that allows users permitted to import custom volumes to store unvalidated snapshot names from the backup index configuration section. Attackers can craft a backup with traversal sequences in snapshot names so later deletion removes arbitrary host directories as root, while renaming or mounting operates on arbitrary paths. | ||||
| CVE-2026-130780 | 1 Lxc | 1 Incus | 2026-11-18 | 9.9 Critical |
| Incus before 7.6.0 contains a path traversal vulnerability that allows malicious migration peers to write outside intended directories by supplying unvalidated dependent volume and snapshot names in the migration offer header. Attackers controlling a migration source can create root-owned volumes with attacker content at arbitrary host paths, compromising hosts using dir storage pools, bypassing restricted.storage-pools.access, or crashing the daemon. | ||||
| CVE-2026-130782 | 1 Lxc | 1 Incus | 2026-11-18 | 7.7 High |
| Incus before 7.6.0 contains an improper authorization vulnerability that allows restricted and view-only clients to read default project resources by requesting the default project directly. Attackers knowing resource names can read profiles, images, network zone peer keys and stored credentials, and export custom volume or bucket backups to obtain full contents or S3 admin keys. | ||||
| CVE-2026-130784 | 1 Lxc | 1 Incus | 2026-11-18 | 9.9 Critical |
| Incus before 7.6.0 contains an authorization bypass vulnerability that allows restricted clients to create and access default project resources by exploiting entitlement checks against the requested project. Attackers can create bridge networks with raw.dnsmasq directives to execute code as root on the host, or manipulate inherited resources via the ?project= parameter. | ||||
| CVE-2026-130786 | 1 Lxc | 1 Incus | 2026-11-18 | 9.9 Critical |
| Incus before 7.6.0 contains a configuration injection vulnerability that allows users who can launch instances from controlled images to inject LXC directives by embedding line breaks in OCI config.json values or oci.entrypoint and oci.cwd keys. Attackers can add liblxc hooks or crafted tmpfs lxc.mount.entry fields to run commands as root on the host or bind-mount host paths, even from restricted projects. | ||||
| CVE-2026-130788 | 1 Semantic-mediawiki | 1 Semantic Mediawiki | 2026-11-18 | 6.1 Medium |
| SemanticMediaWiki from 3.0.0 before 7.4.0 contains a reflected cross-site scripting vulnerability in CsvFileExportPrinter and DsvResultPrinter via unescaped valuesep and separator parameters. Attackers can craft Special:Ask links using request_type=special_page so export output renders as text/html, executing JavaScript in victims' browsers under the wiki origin. | ||||
| CVE-2026-130790 | 1 Semantic-mediawiki | 1 Semantic Mediawiki | 2026-11-18 | 4.8 Medium |
| SemanticMediaWiki from 2.5.0 before 7.4.0 contains a stored cross-site scripting vulnerability that allows users with the smw-patternedit right to inject script by seeding markup reference names in MediaWiki:Smw_allows_pattern. Once an editor annotates the matching Allows pattern value, AllowsPatternValue emits it unescaped on Special:Browse, executing JavaScript in every viewer's session. | ||||
| CVE-2026-130996 | 1 Google | 1 Chrome | 2026-11-18 | 9.6 Critical |
| Out of bounds write in ANGLE in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-130320 | 1 Open Object Rexx | 1 Oorexx | 2026-11-18 | 9.3 Critical |
| In Open Object Rexx (ooRexx) before 5.2.0, RXAPI mishandles nameArg and userid bounds checking, possibly leading to arbitrary code execution via crafted messages. | ||||
| CVE-2026-130327 | 1 Open Object Rexx | 1 Oorexx | 2026-11-18 | 9.3 Critical |
| In Open Object Rexx (ooRexx) before 5.2.0, RXAPI relies on a world-writable /tmp file unless XDG_RUNTIME_DIR is set, or localhost TCP port 10010, allowing RXAPI communication by any local user, e.g., for injection of a macro that will be executed by a REXX script. | ||||
| CVE-2026-12487 | 1 Zyxel | 1 Ee5301-00 Customized Firmware | 2026-11-18 | 7.5 High |
| An incorrect authorization vulnerability in the SNMP parameter of Zyxel EE5301-00 customized firmware version 5.63(ACLD.2)b3_D0 could allow an unauthenticated attacker to cause a denial-of-service (DoS) condition on an affected device. | ||||
| CVE-2026-120387 | 1 Circutor | 1 Powerstudio Scada Wave | 2026-11-18 | N/A |
| An improper JWT signature verification vulnerability in CIRCUTOR PowerStudio SCADA WAVE desktop version allows an unauthenticated remote attacker to bypass authentication by submitting an unsigned JWT with the algorithm set to “none”. The shared JWT validation component accepts the token without verifying a cryptographic signature, allowing the attacker to impersonate another user and access protected functionality with that user's privileges. | ||||
| CVE-2026-111973 | 1 Wordpress-extensions | 1 Rss Feed Retriever | 2026-11-18 | 5.8 Medium |
| The RSS Feed Retriever WordPress plugin through 1.6.10 does not validate a user-supplied URL before fetching it server-side with a bundled HTTP library that lacks WordPress's private-network protections, allowing unauthenticated users to make the site retrieve arbitrary internal or external resources and read the response. | ||||
| CVE-2026-107904 | 1 Valorapps.com | 1 Easy File Uploader Extension For Joomla | 2026-11-18 | 9.8 Critical |
| Joomla Extension - valorapps.com - Unauthenticated Remote Code Execution in Easy File Uploader < 2.9.7 - An unauthenticated remote attacker can upload a PHP-executable file to the Joomla web root with a single multipart POST request, requiring no credentials and no CSRF token. | ||||
| CVE-2026-128038 | 2 Smub, Wordpress-extensions | 2 All In One Seo – Ai Seo Plugin To Boost Seo Rankings & Traffic (schema, Local Seo, Sitemap & Seo Insights), All In One Seo | 2026-11-18 | 6.4 Medium |
| The All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name' parameter in all versions up to, and including, 5.0.5 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires that an administrator has placed the AIOSEO breadcrumb on the author template, that the site is running WordPress 6.6 or later with the core Interactivity runtime loaded (e.g., via a block theme or core/navigation block), and that a victim clicks the rendered breadcrumb link on the author archive page. | ||||