CVE-20XX-?
agent?

CVEs of 2026.

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

1,391 CVEs · updated 2026-11-19 15:32 UTC

Reset all
  1. CVE-2026-133037

    In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the GitHub App repository selector was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  2. CVE-2026-133038

    In JetBrains TeamCity before 2026.2.1 stored XSS in the Maven Build Info project header was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  3. CVE-2026-133039

    In JetBrains TeamCity before 2026.2.1 stored XSS in the Pull Requests health report for Space connections was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  4. CVE-2026-133041

    In JetBrains TeamCity before 2026.2.1, 2026.1.5 stored XSS in the Commit Status Publisher settings was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  5. CVE-2026-133043

    In JetBrains TeamCity before 2026.2.1 missing authorization allowed reading VCS file contents and patches of other projects

    Auth & access Web app JetBrains TeamCity

    6.5 MEDIUM No fix listed
  6. CVE-2026-133046

    In JetBrains TeamCity before 2026.2.1 stored XSS in recipe export errors was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  7. CVE-2026-133029

    In JetBrains TeamCity before 2026.2.1 missing authorization allowed guests to push VCS labels using stored VCS credentials

    Auth & access Web app JetBrains TeamCity

    6.5 MEDIUM No fix listed
  8. CVE-2026-133031

    In JetBrains TeamCity before 2026.2.1 stored XSS in Git VCS root settings was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  9. CVE-2026-133032

    In JetBrains TeamCity before 2026.2.1 reflected XSS on the Cloud Profiles page was possible

    XSS Web app JetBrains TeamCity

    6.1 MEDIUM No fix listed
  10. CVE-2026-133033

    In JetBrains TeamCity before 2026.2.1 stored XSS in Maven Build Info module links was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  11. CVE-2026-133034

    In JetBrains TeamCity before 2026.2.1 stored XSS on the Changes page was possible

    XSS Web app JetBrains TeamCity

    6.4 MEDIUM No fix listed
  12. CVE-2026-133035

    In JetBrains TeamCity before 2026.2.1 stored XSS on the change Files tab was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  13. CVE-2026-133036

    In JetBrains TeamCity before 2026.2.1 stored XSS in the Issue Trackers health report was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  14. CVE-2026-133025

    In JetBrains TeamCity before 2026.2.1 missing authorization allowed project viewers to download project settings

    Auth & access Web app JetBrains TeamCity

    7.7 HIGH No fix listed
  15. CVE-2026-133027

    In JetBrains TeamCity before 2026.2.1, 2026.1.5 privilege escalation was possible via username handling in token authentication

    Auth & access Web app JetBrains TeamCity

    8.8 HIGH No fix listed
  16. CVE-2026-125061

    The administration page "Offene Bestellungen" (open orders) of the JTL PayPal Checkout plugin for JTL-Shop outputs the customer name of pending orders without output encoding. A registered customer (free self-registration) can submit an HTML-entity-encoded name, which is decoded to markup when the billing address of an order is written. If the PayPal payment is left unfinished, the order is listed on the page and the name is rendered as markup in the browser of an administrator who opens the page. The script code runs with the privileges of that administrator and can, for example, create a new administrator account. Guest orders are not affected, because the name is encoded again.

    XSS Web app JTL-Software GmbH JTL PayPal Checkout Plugin (jtl Paypal commerce)

    8.5 HIGH Fix listed
  17. CVE-2026-123972

    The WP-Slimbox2 Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.1.3.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. Successful exploitation requires a logged-in user, typically an administrator, to click the attacker's image link in the comment; however, because unmoderated comments appear in the WordPress moderation queue where administrators routinely interact with them, the moderation gate does not meaningfully prevent exploitation. Successful exploitation causes the attacker's own account to receive the complete Administrator role.

    XSS Web app Malcalevak WP-Slimbox2 Plugin

    7.2 HIGH No fix listed
  18. CVE-2026-132128

    @fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions up to and including 9.3.6, middie does not honor the router's caseSensitive setting and matches path-scoped middleware mount paths with a case-insensitive regular expression that does not fold non-ASCII characters, while Fastify's router, when caseSensitive is set to false, lowercases the request path with a Unicode-aware conversion that maps the KELVIN SIGN character (U+212A) to the ASCII letter k. A request that spells a k in a protected mount path as the percent-encoded KELVIN SIGN is therefore routed to the protected handler while the middleware mounted on that path, such as authentication, authorization, or rate limiting, never matches and is skipped, letting an unauthenticated client reach the handler. Only applications that set caseSensitive to false and protect a mount path containing the letter k are affected. The issue is fixed in @fastify/middie 9.3.7, and users should upgrade to 9.3.7 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after routing, or keep routing case-sensitive, which is the default.

    Other Web app @fastify/middie

    7.4 HIGH Fix listed
  19. CVE-2026-132131

    @fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions 8.3.0 through 9.3.6, the internal helper that normalizes a path-scoped middleware's mount path only handles string inputs, but the use method also accepts an array of mount paths and passes it through unchanged, so the normalization silently does nothing. As a result, a trailing slash on an array element survives into the generated route-matching regular expression, and an element that is exactly the root path, meaning a catch-all mount, is dropped entirely. Requests to subroutes of the affected mount paths then skip the path-scoped middleware, such as authentication, authorization, or rate limiting, while Fastify's router still dispatches them to the handler, allowing an unauthenticated client to reach protected routes. Applications are affected when they mount middleware on an array of paths in which an element ends with a slash, including one introduced by a plugin prefix that ends with a slash, or is exactly the root path. The issue is fixed in @fastify/middie 9.3.7, and users should upgrade to 9.3.7 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after routing, and avoid array mount paths with a trailing slash element for security relevant middleware.

    Other Web app @fastify/middie

    7.4 HIGH Fix listed
  20. CVE-2026-125060

    The checkout of JTL-Shop stores the delivery address ID submitted by the customer in the session and adopts it into the order without verifying that the address belongs to the ordering customer. A remote attacker with access to the checkout, including a guest, can thereby attach the delivery address of another customer to their own order. Name and address of the other customer, and depending on the shop configuration further contact data, then appear in the order confirmation and customer account. As the IDs are sequential, addresses can be enumerated. Goods may also be shipped to the wrong address.

    Auth & access Web app JTL-Software GmbH JTL-Shop

    8.8 HIGH Fix listed
  21. CVE-2026-132133

    @fastify/middie is the middleware engine that adds Express and Connect style middleware support to Fastify. In versions up to and including 9.3.6, middie builds the match regular expression for each path-scoped middleware from its mount path without collapsing duplicate slashes, even when the application enables the ignoreDuplicateSlashes router option. Under that option Fastify's router collapses duplicate slashes in both the registered route and the request path, so a mount path containing a doubled slash is served by the router at its single-slash form while the middleware's compiled match still requires the doubled slash and never matches. A path-scoped middleware such as authentication, authorization, or rate limiting is therefore skipped while the router dispatches the request to the protected handler, without any authentication required. Applications are affected when they enable ignoreDuplicateSlashes and a middleware mount path reaches middie with a duplicate slash, most commonly when a plugin prefix that ends with a slash is joined to a mount path that starts with one. The issue is fixed in @fastify/middie 9.3.7, and users should upgrade to 9.3.7 or later. As a workaround, enforce authorization in a Fastify hook such as preHandler that runs after routing, and avoid mount paths and plugin prefixes that introduce duplicate slashes.

    Other Web app @fastify/middie

    4.8 MEDIUM Fix listed
  22. CVE-2026-123968

    The Slimbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (anchor title within comment HTML)' parameter in all versions up to, and including, 1.0.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. WordPress core comment KSES permits unauthenticated commenters to post anchor elements with href and title attributes, so an entity-encoded payload stored in the title attribute survives sanitization verbatim; the browser then decodes the entities when populating the DOM .title property, and the Slimbox library's jQuery .html() caption sink renders it as executable HTML.

    XSS Web app Kevinsylvestre Slimbox

    7.2 HIGH No fix listed
  23. CVE-2026-123969

    The Fancy Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 1.0.0 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. Successful exploitation without administrator interaction requires that the attacker first have one comment approved so that a subsequent payload comment is auto-published; the injected script only executes when a user clicks the malicious image link inside the comment. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

    XSS Web app Alobaidi Fancy Lightbox

    6.1 MEDIUM No fix listed
  24. CVE-2026-123971

    The Slimbox Plugin plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'el.title (HTML-decoded title attribute of a stored <a rel^=lightbox> element)' parameter in all versions up to, and including, 1.3 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. Exploitation requires a companion plugin such as bbPress that permits low-privileged users to store anchor elements with arbitrary title and rel attributes, as WordPress core comment handling does not preserve rel on anchor tags by default.

    XSS Web app Peppolone Slimbox Plugin

    6.4 MEDIUM No fix listed
  25. CVE-2026-123058

    The web installer of JTL-Shop executes its state-changing installation tasks without checking whether the shop is already installed, and was not removed or locked after the installation. An unauthenticated remote attacker who can reach the installer directory can supply their own database credentials, create administrator and synchronisation accounts and overwrite the shop configuration. This can lead to a full takeover of the shop, including code execution on the server.

    Auth & access Web app JTL-Software GmbH JTL-Shop

    9.2 CRITICAL Fix listed
  26. CVE-2026-132988

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 the Cloud Profiles page disclosed cloud profiles of projects the user could not access

    Auth & access Web app JetBrains TeamCity

    2.7 LOW No fix listed
  27. CVE-2026-132990

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in Change Log revision tooltips was possible

    XSS Web app JetBrains TeamCity

    3.1 LOW No fix listed
  28. CVE-2026-132991

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Slack connection test page was possible

    XSS Web app JetBrains TeamCity

    3.1 LOW No fix listed
  29. CVE-2026-132992

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the agent info popup was possible

    XSS Web app JetBrains TeamCity

    3.1 LOW No fix listed
  30. CVE-2026-132993

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the notification rules editor was possible

    XSS Web app JetBrains TeamCity

    3.7 LOW No fix listed
  31. CVE-2026-132994

    In JetBrains TeamCity before 2026.2 the REST API exposed details of users not visible in the UI

    Disclosure Web app JetBrains TeamCity

    2.7 LOW No fix listed
  32. CVE-2026-132995

    In JetBrains TeamCity before 2026.2 stored XSS on the build step settings page was possible

    XSS Web app JetBrains TeamCity

    3.5 LOW No fix listed
  33. CVE-2026-132989

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the SSH Keys page was possible

    XSS Web app JetBrains TeamCity

    3.5 LOW No fix listed
  34. CVE-2026-132980

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger branch filter settings was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  35. CVE-2026-132981

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Versioned Settings page was possible

    XSS Web app JetBrains TeamCity

    4.8 MEDIUM No fix listed
  36. CVE-2026-132982

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the build Report Tab dialog was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  37. CVE-2026-132983

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Report Tabs settings page was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  38. CVE-2026-132984

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the project Report Tab dialog was possible

    XSS Web app JetBrains TeamCity

    5.4 MEDIUM No fix listed
  39. CVE-2026-132971

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Schedule Trigger dependency settings was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  40. CVE-2026-132972

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Slack Notifier settings page was possible

    XSS Web app JetBrains TeamCity

    4.8 MEDIUM No fix listed
  41. CVE-2026-132973

    In JetBrains TeamCity before 2026.2, 2026.1.5 stored XSS on the external Kotlin DSL editor status page was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  42. CVE-2026-132975

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in issue tracker links was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  43. CVE-2026-132977

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Agent Statistics tooltip was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  44. CVE-2026-132979

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules editor was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  45. CVE-2026-132963

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules path preview was possible

    XSS Web app JetBrains TeamCity

    5.4 MEDIUM No fix listed
  46. CVE-2026-132964

    In JetBrains TeamCity before 2026.2 stored XSS on the Duplicates report tab was possible

    XSS Web app JetBrains TeamCity

    5.4 MEDIUM No fix listed
  47. CVE-2026-132965

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the unknown VCS root page was possible

    XSS Web app JetBrains TeamCity

    4.8 MEDIUM No fix listed
  48. CVE-2026-132966

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in build statistics charts was possible

    XSS Web app JetBrains TeamCity

    5.4 MEDIUM No fix listed
  49. CVE-2026-132967

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the build Issues tab was possible

    XSS Web app JetBrains TeamCity

    6.8 MEDIUM No fix listed
  50. CVE-2026-132968

    In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Large Build Log health report was possible

    XSS Web app JetBrains TeamCity

    5.4 MEDIUM No fix listed

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