CVE-20XX-?
agent?

CVEs of 2026.

Every CVE published in 2026 that we hold, ranked by exploit odds.

4,290 CVEs · updated 2026-11-20 23:16 UTC

Reset all
  1. CVE-2026-129553

    Tensei through 0.11.5 contains an open redirect vulnerability in the @tensei/social-auth SocialAuthCallbackController that allows unauthenticated attackers to redirect users by supplying an unvalidated clientCallback query parameter. Attackers can craft links to the /:provider/callback route that send victims to attacker-controlled sites for phishing and leak the issued temporary access token appended after login.

    Other Web app Tenseijs @tensei/social-auth

    5.3 MEDIUM 0.2% exploit odds No fix listed
  2. CVE-2026-116561

    Improper cleanup on thrown exception vulnerability in Apache Tomcat meant that an HTTP 200 response was sent rather than an HTTP 500 response after a AuthException was thrown during Jakarta Authentication secureResponse(). This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through 10.1.61, from 9.0.0.M1 through 9.0.123. The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.29, 10.0.62 or 9.0.124, which fix the issue. Note: Tomcat 11.0.28 was not released

    Other Web app Apache Software Foundation Apache Tomcat

    9.1 CRITICAL 0.2% exploit odds Fix listed
  3. CVE-2026-129315

    Dokploy is a free, self-hostable Platform as a Service (PaaS). In 0.31.0 and earlier, the hosted installer and manual installation instructions set /etc/dokploy to mode 0777, allowing a local non-root user on a shared host to replace root-owned schedule or Traefik configuration directories. Dokploy subsequently consumes those paths as trusted configuration and can execute substituted scheduled-task scripts as root, resulting in local privilege escalation.

    Auth & access Server Dokploy

    8.5 HIGH 0.2% exploit odds Fix listed
  4. CVE-2026-130359

    AdminNeo before 5.9.1 contains a stored cross-site scripting vulnerability in SlugifyEditPlugin::getFieldInput() that embeds column names unescaped in an inline initSlugField() call. Attackers with DDL privileges can create a slug column whose name contains a single quote, injecting JavaScript that runs under the page's CSP nonce when victims open the table's edit form.

    XSS Web app

    2.0 LOW 0.2% exploit odds Fix listed
  5. CVE-2026-115846

    The Libreswan IKEv2 state machine did not verify that an IKE_INTERMEDIATE exchange was required to satisfy the addke= PostQuantum algorithm component of the exchange. A connecting client could (maliciously or by implementation error) skip the IKE_INTERMEDIATE exchange and start an IKE_AUTH exchange prematurely. The result is as if the addke= option had not been specified, and such connections are only protected by the classic key exchange algorithm (such as P-256 or Curve25519), allowing "store now, decrypt later" attacks once a quantum computer becomes available. Only connections with the addke= keyword in the ike= and/or esp= configuration option are affected. PostQuantum Hybrid Key Exchange support was added in version 5.4.

    Crypto Network gear

    3.7 LOW 0.2% exploit odds No fix listed
  6. CVE-2026-129945

    Keystatic through 0.6.9 contains a login cross-site request forgery vulnerability in the githubOauthCallback handler that allows unauthenticated remote attackers to sign victims in with the attacker's GitHub account by omitting state validation. Attackers can induce victims to visit the OAuth callback with an attacker-obtained authorization code, causing victim edits in the admin UI to be committed under the attacker's GitHub identity.

    Auth & access Web app

    5.3 MEDIUM 0.2% exploit odds No fix listed
  7. CVE-2026-99783

    In the Linux kernel, the following vulnerability has been resolved: net/9p/usbg: Fix use-after-free in disable_usb9pfs() disable_usb9pfs() frees the IN and OUT usb_request objects before it disables the corresponding endpoints. If either request is still queued, the later usb_ep_disable() call cancels the endpoint queue and the UDC driver can still access the already freed request. With dummy_hcd and KASAN, this is reproducible by queueing the OUT request and then disconnecting the configfs gadget: BUG: KASAN: slab-use-after-free in dummy_disable+0x2b4/0x300 Read of size 8 at addr ffff888009702400 by task sh/1 usb_ep_disable+0x8e/0x1f0 usb9pfs_func_unbind+0x193/0x350 gadget_dev_desc_UDC_store+0x135/0x280 dummy_free_request() also warns because the request is freed while its queue entry is still linked. Disable both endpoints before freeing the request objects. This lets usb_ep_disable() cancel any queued transfers and invoke the completion callback while the request storage is still valid. The request objects are then freed only after they have been removed from the endpoint queues.

    Memory safety OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  8. CVE-2026-99784

    In the Linux kernel, the following vulnerability has been resolved: 9p/xen: fix refcount leak in p9_xen_response() on wrong tag p9_xen_response() looks up the request for an incoming reply with p9_tag_lookup(), which takes a reference on the returned p9_req_t. When the tag does not resolve to a request in REQ_STATUS_SENT, the function warns and continues the loop without dropping that reference, permanently leaking the p9_req_t and its msize buffers. The reply header, including the tag, is supplied by the backend, so a malicious or buggy 9P backend can leak kernel memory on every crafted response. Drop the reference before continuing.

    Memory safety OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  9. CVE-2026-99785

    In the Linux kernel, the following vulnerability has been resolved: 9p/trans_virtio: reject mount tags longer than NAME_MAX at probe p9_virtio_probe() reads a 16-bit mount tag length (tag_len) from the device config and kzalloc()s tag_len + 1 bytes for chan->tag with no upper bound. A malicious or compromised host can present a tag of up to 65535 bytes; that tag is later copied into the single-page sysfs buffer by p9_mount_tag_show() (memcpy(buf, chan->tag, tag_len + 1)), a host-controlled out-of-bounds write of up to ~64 KiB past the PAGE_SIZE attribute buffer. Reject an overlong tag at probe time. A 9p mount tag is a name-like identifier, so bound it by NAME_MAX (255): that limit is independent of the sysfs/seq_file page size and is far above any legitimate mount tag, which keeps p9_mount_tag_show() safe at the root without hard-coding a seq_file implementation detail.

    Memory safety OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  10. CVE-2026-99786

    In the Linux kernel, the following vulnerability has been resolved: xfrm: retry inexact policy lookup after node reinsertion An inexact policy lookup first records pointers to candidate hlist heads and then traverses the lists. A concurrent policy insertion can merge inexact tree nodes between those operations: lookup policy insertion ------ ---------------- find inexact candidates save obsolete hlist head write_seqcount_begin(&bin->count) merge inexact tree nodes hlist_del_rcu(&policy->bydst) reinsert policy->bydst in survivor write_seqcount_end(&bin->count) evaluate saved candidate list miss the moved policy The merge immediately reinserts the same hlist node into the surviving tree node. RCU keeps the policy alive, but it does not provide a consistent view while its list node is moved. A lookup that selected the obsolete list can observe it empty. A lookup already traversing a moved policy can instead follow the next pointer rewritten by the reinsertion. Either case can return an incorrect IPsec policy result. The per-bin sequence counter already brackets calls to xfrm_policy_inexact_insert_node(), including node merges. The read side, however, currently validates the counter only while searching an individual rb-tree. A successful search returns without validation, and the later candidate-list traversal is outside that read-side section. Snapshot the per-bin sequence before discovering candidate heads and validate it after evaluating all candidate lists. Retry the lookup if the inexact policy tree changes while it is being searched.

    Other OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  11. CVE-2026-99779

    In the Linux kernel, the following vulnerability has been resolved: net/9p/usbg: call disable_usb9pfs() from usb9pfs_disable() usb9pfs_disable() is the usb_function ->disable callback, invoked by the composite gadget core whenever the host resets or unconfigures the gadget. The gadget function API requires this callback to disable its endpoints; every other in-tree function driver does so from its ->disable hook. usb9pfs_disable() never called disable_usb9pfs(), so the IN/OUT endpoints and their usb_request objects were left active and allocated across a host-driven disable. When the host later reconfigures the device, enable_usb9pfs() calls alloc_requests() again and unconditionally overwrites usb9pfs->in_req/out_req, permanently leaking the previous allocations, while the endpoints themselves are left enabled underneath the function's own idea of being disabled. Call disable_usb9pfs() before reinit_completion(&usb9pfs->send), mirroring the same sequence already used in p9_usbg_close(). Placing it before the reinit_completion() also ensures usb_ep_disable() has synchronously flushed any requests still queued in hardware before the completion is reset, closing the same race that motivated resetting the completion here in the first place.

    Other OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  12. CVE-2026-99747

    In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix NULL pointer dereference in session_user_name() and session_account_type() session_user_name() and session_account_type() dereference session->user without checking for NULL. A session can be published and exposed via the procfs session interface before authentication completes, during which session->user is NULL: show_proc_session() -> session_user_name(sess) -> user_guest(session->user) -> NULL->flags -> oops Guard both functions by treating a NULL session->user as an explicit not-yet-authenticated state rather than dereferencing it.

    Other OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  13. CVE-2026-130179

    The Okta .NET SDK Abstractions library systematically writes per-request authentication credentials to a shared HTTP client instance, rather than being isolated to individual outbound request objects. When using scoped child clients, a subsequent scoped request can overwrite the shared client configuration. Because the original parent client credential has not been restored, subsequent outbound requests may be transmitted using the newly written credential, which can result in subsequent actions being executed under the context of an incorrect security principal in the Okta Management API and improper attribution in audit logs.

    Other Library Okta .NET SDK Abstractions Library

    8.5 HIGH 0.2% exploit odds No fix listed
  14. CVE-2026-99417

    In the Linux kernel, the following vulnerability has been resolved: ovl: fix a torn path in ovl_get_redirect() A hard link of a metacopy file that races with a rename of an ancestor stores a redirect to the wrong lower file. Each component of an absolute redirect must be the name that a dentry has in the parent that the walk continues with. ovl_get_redirect() copies the name under d_lock and calls dget_parent() after the unlock, and the callers for a hard link hold no lock that stops a rename across directories. A rename between the two steps combines the old name with the new parent. With delays in ovl_get_redirect(), an unprivileged user hard-linked a metacopy file while renaming its ancestor to another directory, the stored redirect named another lower path, and after a remount the file showed the data of a root-only file. Fix this by taking the parent first and checking it again under d_lock.

    Other OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  15. CVE-2026-99418

    In the Linux kernel, the following vulnerability has been resolved: ovl: do not copy up an xattr value that was never read Copy-up stores uninitialized kernel memory in an xattr of the upper file, where the user can read it. ovl_copy_xattr() may only pass bytes to ovl_do_setxattr() that ovl_do_getxattr() has read. When the read fails with -ERANGE the function asks for the size again, and if the new size fits the buffer it stores the buffer although nothing was read into it. The buffer comes from kvmalloc(), or it still holds the value of the previous xattr. A FUSE lower layer that answers every sized GETXATTR with -ERANGE made copy-up store 4096 bytes that the server never sent, with a kernel pointer in them, as an xattr of the upper file. Fix this by failing the copy-up with -EIO when the size that follows -ERANGE fits the buffer.

    Memory safety OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  16. CVE-2026-99419

    In the Linux kernel, the following vulnerability has been resolved: ovl: do not copy up a dentry that was removed A change to a removed file through an open descriptor replaces whatever has its old name in the upper layer. Copy up must only create a name in the upper directory, never replace one. After an unlink, an rmdir or a rename over a lower dentry, a dentry that an open file keeps alive still has its old parent and name, but in the upper directory that name is now a whiteout or a new object. ovl_copy_up_workdir() renames the copy over it, which brings back the removed object and destroys whatever took its name. An unprivileged user opened a lower FIFO and unlinked it, root created a file at that name, and fchmod on the old descriptor replaced the file of root with the FIFO. Fix this by looking up the target name of the rename in ovl_copy_up_workdir() with LOOKUP_EXCL, so that copy up fails with -EEXIST if the name is taken, as copy up with O_TMPFILE already does when it links the copy to the name. [amir: use LOOKUP_EXCL instead of relying on d_unhashed()]

    Other OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  17. CVE-2026-54747

    Chamilo LMS is an open-source learning management system. Prior to 2.0.3, public/main/course_description/course_description_controller.php assigns contentDescription directly from a teacher's request in the Doctrine-based add and edit paths without cross-site scripting sanitization. The stored value is rendered by src/CoreBundle/Resources/views/Course/about.html.twig through description with raw output, and the /course/{id}/about route is publicly accessible. A teacher can store active content that executes when an authenticated or unauthenticated visitor views the course description, enabling session theft, credential phishing, defacement, or actions in an authenticated victim's session. This issue is fixed in version 2.0.3.

    XSS Web app Chamilo chamilo-lms

    6.4 MEDIUM 0.2% exploit odds Fix listed
  18. CVE-2026-99319

    In the Linux kernel, the following vulnerability has been resolved: ALSA: usx2y: Refuse a retried DSP load after a failure snd_usx2y_hwdep_dsp_load() sets up the asynchronous sequence URBs and the interrupt URB when the FPGA firmware image with index 1 is loaded, and then creates the ALSA devices. If usx2y_in04_init() or usx2y_create_alsa_devices() fails, the URBs that were already set up are left in place. The core keeps the index unloaded when the callback fails, so user space may issue the same request again. The second attempt then enters usx2y_async_seq04_init() or usx2y_in04_init() with the URBs still allocated and trips WARN_ON(usx2y->as04.buffer) or WARN_ON(usx2y->in04_urb). The URBs cannot be released at this point: the card may already have registered PCM devices that user space can still open, and the disconnect handler accesses the URBs without holding the DSP lock. Mark the chip as hung instead, so that a retried request is refused with -ENODEV and the assertions keep their meaning. The URBs are released by snd_usx2y_card_private_free() when the card is freed. A failing usx2y_async_seq04_init() still releases its own URBs, so that path remains retryable.

    Other OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  19. CVE-2026-99314

    In the Linux kernel, the following vulnerability has been resolved: ALSA: us122l: Add missing NULL check in usb_stream_hwdep_mmap() usb_stream_hwdep_mmap() reads us122l->sk.s and dereferences it without checking for NULL. The stream object is released by usb_stream_free(), which is reached through us122l_stop() both when the device is disconnected and when us122l_start() fails, and it leaves us122l->sk.s set to NULL. The hwdep file stays usable after that, so a later mmap() KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] RIP: 0010:usb_stream_hwdep_mmap+0x107/0x890 sound/usb/usx2y/us122l.c:182 crashes while reading s->read_size, which sits at offset 0x10. That NULL is an expected state for this field: usb_stream_hwdep_vm_fault(), usb_stream_hwdep_poll(), usb_stream_hwdep_ioctl(), usb_stream_stop() and usb_stream_free() all test it before use. Only the mmap callback misses the check, so let it return -ENODEV, matching what the other hwdep mapping in usx2yhwdeppcm.c does when its shared buffer has not been allocated.

    Memory safety OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  20. CVE-2026-99315

    In the Linux kernel, the following vulnerability has been resolved: ALSA: us122l: Fix NULL dereference at hwdep open and release usb_stream_hwdep_open() and usb_stream_hwdep_release() pass the result of usb_ifnum_to_if() straight to usb_autopm_get_interface() and usb_autopm_put_interface(), without checking it for NULL. usb_ifnum_to_if() returns NULL once the device is gone, since usb_disable_device() clears udev->actconfig on disconnect. The hwdep file can outlive the disconnect: the card is released with snd_card_free_when_closed(), so a process that keeps the character device open reaches the driver's release callback after the USB configuration has been dropped, and interface_to_usbdev() then dereferences the NULL interface at offsetof(struct device, parent). The open callback has the same problem when it races with the disconnect. Check both lookups and fail the open with -ENODEV; in release, skip the runtime PM put when the interface is already gone and still run the rest of the per-file cleanup. Move the us122l->first bookkeeping after the checks so that a failed open no longer leaves a stale file pointer behind.

    Other OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  21. CVE-2026-99318

    In the Linux kernel, the following vulnerability has been resolved: ALSA: bcd2000: Fix use-after-free of MIDI URBs on file close bcd2000_disconnect() calls snd_card_disconnect(), which only prevents new opens, and then frees the MIDI URBs. A rawmidi file that was already open can still be closed afterwards, and its close callback, bcd2000_midi_output_close(), calls usb_kill_urb() on midi_out_urb. The URB pointers are cleared on disconnect and their accesses are serialized with midi_lock, but bcd2000_midi_output_close() reads midi_out_urb without that lock. The check can therefore pass just before the pointer is cleared, and usb_kill_urb() then runs on the URB that has already been freed: BUG: KASAN: slab-use-after-free in usb_kill_urb+0x74/0x80 Read of size 8 at addr ffff8880078e7d40 usb_kill_urb bcd2000_midi_output_close close_substream rawmidi_release_priv snd_rawmidi_release Allocated by: usb_alloc_urb <- bcd2000_init_midi <- bcd2000_probe Freed by: usb_free_urb <- bcd2000_midi_free <- bcd2000_disconnect Take the lock in bcd2000_midi_output_close() and reference the URB with usb_get_urb() before releasing it. The URB then stays valid until usb_put_urb() after usb_kill_urb() has returned, even if a disconnect frees it in the meantime. usb_kill_urb() itself cannot run under midi_lock, as the completion handler takes the same lock.

    Memory safety OS & kernel Linux

    unscored 0.2% exploit odds No fix listed
  22. CVE-2026-131843

    Poppler pdftohtml through 26.11.0 contains a cross-site scripting vulnerability in HtmlLink::getLinkStart() in utils/HtmlLinks.cc that writes PDF link annotation URIs into href attributes without escaping in HTML output modes. Attackers can craft a PDF whose /URI entry contains a double quote followed by HTML markup or event handlers to execute script in browsers viewing the generated HTML.

    XSS

    5.3 MEDIUM 0.2% exploit odds No fix listed
  23. CVE-2026-129041

    Missing Authorization vulnerability in WP User Manager WP User Manager wp-user-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Manager: from n/a through 2.10.4.

    Auth & access Web app WP User Manager

    5.3 MEDIUM 0.2% exploit odds No fix listed
  24. CVE-2026-129051

    Missing Authorization vulnerability in WP User Manager WP User Manager wp-user-manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP User Manager: from n/a through 2.10.4.

    Auth & access Web app WP User Manager

    5.3 MEDIUM 0.2% exploit odds No fix listed
  25. CVE-2026-129009

    Missing Authorization vulnerability in Knit Pay UPI QR Code Payment Gateway for WooCommerce upi-qr-code-payment-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects UPI QR Code Payment Gateway for WooCommerce: from n/a through 1.7.0.

    Auth & access Knit Pay UPI QR Code Payment Gateway For WooCommerce

    5.3 MEDIUM 0.2% exploit odds No fix listed
  26. CVE-2026-129046

    Missing Authorization vulnerability in Crocoblock JetFormBuilder jetformbuilder allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JetFormBuilder: from n/a through 3.6.8.1.

    Auth & access Web app

    5.3 MEDIUM 0.2% exploit odds No fix listed
  27. CVE-2026-125739

    Missing Authorization vulnerability in ThimPress LearnPress learnpress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LearnPress: from n/a through 4.4.13.

    Auth & access Web app

    5.3 MEDIUM 0.2% exploit odds No fix listed
  28. CVE-2026-125681

    Missing Authorization vulnerability in ThimPress LearnPress learnpress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LearnPress: from n/a through 4.4.13.

    Auth & access Web app

    5.3 MEDIUM 0.2% exploit odds No fix listed
  29. CVE-2026-128974

    temporary redacted

    Disclosure Tbc

    5.4 MEDIUM 0.2% exploit odds No fix listed
  30. CVE-2026-127354

    Vulnerability in the Oracle Hyperion Financial Close Management product of Oracle Hyperion (component: Reconciliation Manage). The supported version that is affected is 11.2.26.0.000. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hyperion Financial Close Management. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Hyperion Financial Close Management accessible data. CVSS 3.1 Base Score 3.1 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N).

    Auth & access Oracle Corporation Oracle Hyperion Financial Close Management

    3.1 LOW 0.2% exploit odds Fix listed
  31. CVE-2026-115029

    Vulnerability in the Oracle Hyperion Data Relationship Management product of Oracle Hyperion (component: Access and security). The supported version that is affected is 11.2.26.0.000. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Hyperion Data Relationship Management. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Hyperion Data Relationship Management, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Hyperion Data Relationship Management accessible data. CVSS 3.1 Base Score 3.4 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:N).

    Auth & access Web app Oracle Corporation Oracle Hyperion Data Relationship Management

    3.4 LOW 0.2% exploit odds Fix listed
  32. CVE-2026-115009

    Vulnerability in the Oracle Hyperion Data Relationship Management product of Oracle Hyperion (component: Access and security). The supported version that is affected is 11.2.26.0.000. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Hyperion Data Relationship Management. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Oracle Hyperion Data Relationship Management accessible data. CVSS 3.1 Base Score 3.1 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N).

    Auth & access Oracle Corporation Oracle Hyperion Data Relationship Management

    3.1 LOW 0.2% exploit odds Fix listed
  33. CVE-2026-130356

    phpMyFAQ from 4.2.0-alpha.2 before 4.2.0-RC.2 contains an authorization bypass that lets category- or language-restricted editors rewrite visibility ACLs and tags of any FAQ. Attackers send faq/update requests with a target faqId and an untranslated lang to expose restricted FAQs, wipe tags, or overwrite orphaned FAQs.

    Auth & access Web app

    5.3 MEDIUM 0.2% exploit odds Fix listed
  34. CVE-2026-110984

    The RegistrationMagic WordPress plugin before 6.1.0.4 does not sanitise and escape a parameter before using it in a SQL statement, which could allow high privilege users such as admin to perform SQL injection attacks.

    Injection Web app

    4.1 MEDIUM 0.2% exploit odds No fix listed
  35. CVE-2026-133625

    iLBC audio codec crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Memory safety Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  36. CVE-2026-130466

    ERF file parser crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Memory safety Library Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  37. CVE-2026-130469

    RTSE protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Memory safety Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  38. CVE-2026-130458

    IrDA protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Memory safety Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  39. CVE-2026-130460

    Multiple protocol dissector crashes in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Memory safety Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  40. CVE-2026-130462

    Multiple protocol dissector and file parser hangs in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Denial of service Library Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  41. CVE-2026-130463

    Android Logcat file parser crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Denial of service OS & kernel Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  42. CVE-2026-130453

    OpenWire protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Denial of service Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  43. CVE-2026-130454

    IEEE 1905 protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Memory safety Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  44. CVE-2026-130455

    Kafka protocol dissector infinite loop in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Memory safety Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  45. CVE-2026-130457

    Matter protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service

    Denial of service Wireshark Foundation Wireshark

    5.5 MEDIUM 0.2% exploit odds No fix listed
  46. CVE-2026-116600

    Missing release of memory after effective lifetime vulnerability in Apache Tomcat via WebSocket. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.27, from 10.1.0-M1 through 10.1.61, from 9.0.22 through 9.0.123 The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100, from 7.0.43 through 7.0.109. Other unsupported versions may also be affected. Users are recommended to upgrade to version 11.0.29, 10.0.62 or 9.0.124, which fix the issue. Note: Tomcat 11.0.28 was not released

    Memory safety Web app Apache Software Foundation Apache Tomcat

    7.5 HIGH 0.2% exploit odds Fix listed
  47. CVE-2026-92907

    IBM watsonx.data 2.4.0 through 2.4.0 patch 8 could allow a remote authenticated attacker to conduct a server-side request forgery due to a server-side request forgery (SSRF) vulnerability.

    Disclosure Server IBM watsonx.data

    4.3 MEDIUM 0.2% exploit odds Fix listed
  48. CVE-2026-131302

    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.

    Auth & access Splunk AI Assistant

    4.3 MEDIUM 0.2% exploit odds No fix listed
  49. CVE-2026-131251

    In Splunk SOAR versions below 8.8.0, a user with permission to view and modify containers with an allowed label could add artifacts to containers that the user cannot view or modify. The vulnerability is possible because the Representational State Transfer (REST) API artifact-creation workflow does not preserve the authorization boundary for the selected container.

    Auth & access Server Splunk SOAR

    4.3 MEDIUM 0.2% exploit odds No fix listed
  50. CVE-2026-131241

    In Splunk SOAR versions below 8.8.0, a user with edit permission for containers on only a subset of container labels could modify container pins outside the container labels that the role permits. The vulnerability is possible because the Container Pin Representational State Transfer (REST) API does not enforce the container label authorization boundary when handling requests. For more information see Manage roles and permissions in Splunk SOAR (On-premises) (https://help.splunk.com/en/splunk-soar/soar-on-premises/administer-soar-on-premises/6.4.1/manage-your-splunk-soar-on-premises-users-and-accounts/manage-roles-and-permissions-in-splunk-soar-on-premises) in the Splunk documentation.

    Auth & access Server Splunk SOAR

    4.3 MEDIUM 0.2% exploit odds No fix listed

CVE records published in 2026 (ids starting CVE-2026-), sorted by how likely they are to be exploited.