-
CVE-2026-118535
•
published on November 15, 2026
A repository registered by its owner as a source of scoped workflows kept that registration when it was transferred to another owner. The new owner could then change the workflows in the transferred repository, and they kept running in the previous owner's repositories with access to their Actions secrets and job tokens. A transfer now removes the owner-level registrations of the repository, and registrations whose source repository no longer belongs to the registering owner are ignored.
-
CVE-2026-118389
•
published on November 15, 2026
The RubyGems package registry accepted gems whose platform, dependency names or dependency version requirements contain newline characters. Because the compact index served to clients is line-based, a user who can publish a gem to an owner's registry could forge index entries, such as packages that do not exist or additional versions of an existing gem with dependencies of their choice. Clients that resolve gems from that registry could then be led to install attacker-chosen dependencies. Gems with such metadata are now rejected.
-
CVE-2026-116559
•
published on November 15, 2026
The A2Reviews WordPress plugin through 1.2.3 does not properly verify authorization on several of its API command handlers, relying on a signature keyed on a value that is empty by default on an unconnected install, allowing unauthenticated attackers to modify A2Reviews WordPress plugin through 1.2.3 settings and product review metadata and to read non-public product metadata.
-
CVE-2026-116288
•
published on November 16, 2026
In affected versions of Octopus Server, a user with permission to edit team scoped roles could escalate their privileges to deploy to projects and environments that they were not authorised to so.
-
CVE-2026-115846
•
published on November 16, 2026
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.
-
CVE-2026-115690
•
published on November 16, 2026
Apache WSS4J remembers the UsernameToken Nonce, the Timestamp and signature of a signed message, and the ID of a SAML 2.0 "OneTimeUse" assertion, so that a captured message cannot be accepted twice. It checked whether a value had already been seen, validated the message, and only then remembered the value, as two separate steps. If several copies of the same message were processed at the same time, they could all pass the check before any of them was remembered, and all be accepted. An attacker who obtained a valid message before the recipient first processed it could send several copies at once, so that the same authenticated request was executed more than once. Where a UsernameToken is not bound to the message by a signature, the copies could carry different message bodies. The attacker needs to obtain the message while it is still in transit; a message captured after it has been accepted cannot be replayed. Affects deployments with a replay cache configured, as Apache CXF has by default. The value is now checked and remembered in a single atomic step. Custom ReplayCache implementations should override the new ReplayCache.addIfAbsent method with an operation that is atomic in their underlying store. Users are recommended to upgrade to versions 4.0.3 or 3.0.7 or 2.4.5, which fix this issue.
-
CVE-2026-115563
•
published on November 16, 2026
The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. From 1.9.1 until 1.30.0 and 2.2.0, OAuth client support in mcp.client.auth can send credentials to an authorization server chosen by an untrusted MCP server. ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider cannot identify the authorization server that owns their credentials. Affected HTTP clients using those providers, OAuthClientProvider, or the deprecated 1.x RFC7523OAuthClientProvider can disclose a client_secret, authorization code, PKCE code_verifier, or signed client assertion. MCP servers, stdio clients, and clients that attach their own tokens or headers are not affected. Interactive OAuthClientProvider use requires a person to start sign-in, while the unattended providers do not. For ClientCredentialsOAuthProvider and PrivateKeyJWTOAuthProvider, callers must configure issuer= after upgrading because omission still follows the MCP server's advertised authorization server, and the deprecated RFC7523OAuthClientProvider must be replaced because it has no issuer option. A stored client registration without an issuer remains unbound after upgrading, so stored OAuth client information must be cleared once to register again or a manually pre-registered record must be updated with its issuer. This issue is fixed in versions 1.30.0 and 2.2.0.
-
CVE-2026-114737
•
published on November 16, 2026
The fix for CVE-2026-23903 https://shiro.apache.org/security-reports.html#cve_2026_23903 was incomplete for manually-created ShiroFilterFactoryBean, which still matched paths case-sensitively by default.
This issue affects Apache Shiro version 3.0.1, only when ShiroFilterFactoryBean is created manually by the application and static files are served from a case-insensitive filesystem.
Applications that let Shiro Spring (Boot) Starter create the bean are not affected.
Mitigation: Upgrade to version 3.0.2 or later, which fixes the issue.
Alternatively, call setCaseInsensitive(true) on the ShiroFilterFactoryBean.
-
CVE-2026-114505
•
published on November 16, 2026
OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Prior to 7.260722.0, the GraphQL endpoint accepts query operations over HTTP GET because CSRF prevention is disabled (csrfPrevention: false), placing the complete GraphQL query and its arguments in the request URL. Server and reverse-proxy logs, browser history, and shared caches can retain sensitive filters, marking-restricted identifiers, and investigation search arguments, allowing a person with access to those records to recover legitimate users' query contents. GraphQL mutations are not accepted over GET, and the issue does not permit code execution. This issue is fixed in version 7.260722.0.
-
CVE-2026-114453
•
published on November 16, 2026
The Kadence Memberships WordPress plugin before 4.0.6 does not check that the membership level submitted when renewing a membership matches the level being renewed, pricing the renewal from the submitted level while activating the membership at its own level, allowing unauthenticated users to activate a paid membership without paying on sites that also offer a free level.
-
CVE-2026-114452
•
published on November 15, 2026
The Membership Plugin WordPress plugin before 4.0.6 does not verify that the membership referenced in a saved-card payment request belongs to the user making it, allowing subscriber-level members to disclose another member's Stripe payment client secret and attach a payment method of their choosing to another member's pending payment.
-
CVE-2026-114451
•
published on November 15, 2026
The Membership Plugin WordPress plugin before 4.0.6 does not perform any authorization or CSRF check before running a schema-altering database maintenance routine, allowing unauthenticated users to convert the Membership Plugin WordPress plugin before 4.0.6's own tables to a narrower character set, which irreversibly replaces every 4-byte character (such as emoji and some CJK characters) in the membership level, discount code and payment records with a question mark.
-
CVE-2026-113631
•
published on November 16, 2026
Incorrect authorization in the sendForm RPC handler and Session JWT reconnect handling in ONLYOFFICE Docs (Document Server) 9.4.0-129 on the official onlyoffice/documentserver container allows an authenticated view-only user to export a reconstructed copy of a document, including content the viewer never displayed such as custom XML, custom document properties and field instruction text, even when download and form-filling are disabled. The attacker reconnects with a valid Session JWT while substituting an attacker-controlled callback URL, which the Session JWT does not bind, then invokes sendForm over RPC, causing DocumentServer to send the reconstructed DOCX to that URL.
-
CVE-2026-113630
•
published on November 16, 2026
Command injection in the documentserver-flush-cache.sh maintenance helper in ONLYOFFICE Docs (Document Server) 9.4.0-129 on the official onlyoffice/documentserver container allows a local attacker with command execution as the ds user to execute arbitrary commands as root via a crafted --hash argument that is interpolated unvalidated into a GNU sed expression, where the sed e flag runs attacker-controlled commands. The packaged sudoers policy permits ds to run the helper as root without a password and with unrestricted arguments.
-
CVE-2026-113456
•
published on November 16, 2026
visualTicket exposes sensitive information in error messages in the cinema report generator. An authenticated attacker with an admin privileges can supply an invalid date_from value causing the application to return a detailed error page that discloses the full SELECT statement (table and column names, JOIN, GROUP BY and ORDER BY clauses, bind parameter placeholders) and a PHP DateTime parsing exception.
This issue was fixed in version 20260817.
-
CVE-2026-113455
•
published on November 16, 2026
visualTicket displays secret token value in admin settings panel. The "KSeF - Token API" edit form renders a pre-filled field containing the actual KSeF API integration secret without any masking.
This issue was fixed in version 20260817.
-
CVE-2026-113454
•
published on November 16, 2026
visualTicket exposes sensitive information in error messages in the administrative report generator. Because application exception details and SQL queries are rendered in the HTTP response in the production environment, an authenticated administrator submitting an invalid date_from value in the report request receives a detailed error page disclosing the full SELECT statement, table and column names, JOINs, bind parameters, and a PHP DateTime exception.
This issue was fixed in version 20260817.
-
CVE-2026-113453
•
published on November 16, 2026
visualTicket does not require authentication for the PDF invoice file serving functionality. Invoice PDF files reside in a web-accessible static path without a session check, while authorization is enforced only at the invoice registry page. A remote unauthenticated attacker who obtains the URL of an invoice PDF can download the document without authorization.
This issue was fixed in version 20260817.
-
CVE-2026-113452
•
published on November 16, 2026
visualTicket is vulnerable to Reflected Cross-Site Scripting via the selectedDate parameter in the order summary page. An attacker can prepare a specially crafted URL that, when opened, results in arbitrary JavaScript execution in the victim's browser.
This issue was fixed in version 20260817.
-
CVE-2026-113451
•
published on November 16, 2026
visualTicket is vulnerable to Cross-Site Request Forgery (CSRF) across multiple endpoints. State-changing operations are exposed via GET requests without any CSRF protection. A remote attacker can persuade an authenticated user (including administrator) into navigating to a prepared URL, causing the victim's browser to issue requests that carry the active session cookie and perform unintended actions.
This issue was partially addressed in version 20260817: settings changes and bulk refunds require POST with a CSRF token, and the session cookie is set with SameSite=Lax, which limits cross-site requests.