N-able N-central versions before 2026.4.1 HF3 have a vulnerability in the ServerMMS2 RemoteExecutionTaskSubmit operation where callers are not authenticated and task ownership is not verified. This allows a remote unauthenticated attacker to submit forged results for remote execution tasks of any customer.
N-able N-central versions before 2026.4.1 HF3 contain a vulnerability where the ServerMMS2 AssetDiscoSimplifiedInfoSubmit operation does not authenticate callers. This allows a remote, unauthenticated attacker to overwrite asset data for any appliance managed by the system.
N-able N-central versions prior to 2026.4.1 HF3 contain a vulnerability where the repositoryItemGet operation can be invoked without authentication. This allows a remote attacker who knows a policy identifier to download Automation Manager policies of any customer, including embedded scripts and parameter values.
The Patch Management Engine in N-central contains a vulnerability that allows local privilege escalation (LPE) through attacker-controlled metadata. This flaw could enable a user with limited privileges to gain higher-level access on the affected system. The vulnerability is identified as CVE-2026-129271 and has a high severity rating with a CVSS score of 8.5.
N-able N-central versions prior to 2026.4.1 HF3 contain a vulnerability where control characters in an Audit Export setting are not properly neutralized before being written to the system logging configuration. This flaw allows an authenticated attacker with product administrator privileges to inject configuration data and execute commands with root privileges on the N-central server.
N-able N-central versions prior to 2026.4.1 HF3 have a vulnerability in the password reset function that allows remote unauthenticated attackers to distinguish valid user accounts by the responses returned. This enables enumeration of valid email addresses.
This vulnerability is a reflected Cross-Site Scripting (XSS) issue in the Novanet Web platform affecting the GET parameters cod_primaria and cod_secundaria in specific endpoints. It allows an unauthenticated attacker to inject and execute arbitrary JavaScript in the context of the affected site when a victim visits a crafted URL. The flaw stems from improper sanitization and encoding of user input within JavaScript blocks. No patch or remediation information is currently provided.
N-able released a critical security update for its N-central product addressing 17 zero-day vulnerabilities, including those already exploited in the wild. The update removes legacy API support, blocking exploitation of a known exploit chain called 4EverAble2Shell that combined an Apache Axis RCE with an N-central privilege escalation bug. The patches also improve authentication, agent communication, and device verification. N-able has applied these patches to hosted environments and urges on-premises users to upgrade immediately. Failure to update leaves agents and probes vulnerable to impersonation and remote code execution attacks.
CVE-2026-127174 is a permission bypass vulnerability in pretix affecting scheduled exports. When changing the settings of a scheduled export, the system does not verify whether the user has permission to access the new export target after the change. This allows an attacker with permission to modify organizer settings and access certain data (e.g., all orders) to change the export to data they should not access (e.g., gift cards). The vulnerability is fixed by disallowing changes to the export type of existing scheduled exports, which is a breaking API change but expected to have minimal impact on typical usage.
CVE-2026-127140 is a server-side request forgery (SSRF) vulnerability in the pretix Widget WordPress Plugin. The plugin uses wp_remote_get instead of wp_safe_remote_get to fetch CSS and JS files, allowing SSRF with body extraction. Exploitation requires WordPress permissions to create or modify pages. The issue is fixed in version 1.1.2.
CVE-2026-127139 is a vulnerability in pretixSCAN Proxy where a cryptographically weak pseudo-random number generator is used to create initialization tokens and API keys. This weakness could allow an attacker with access to some tokens to predict others. The exposure risk depends on the local network structure where pretixSCAN is deployed. A fix is available in version 2.7.3.
A vulnerability in pretixSCAN Android apps allows attackers to circumvent the offline barcode revocation check by exploiting faulty QR code parsing. This enables the use of crafted QR codes for revoked tickets to gain event entry when scanning offline. The issue affects multiple versions prior to fixed releases and requires the use of the "pretix signature scheme 1". The ticket appears valid on the scanner but is invalid on the server. No evidence of exploitation has been found.
This vulnerability exists in e-Sushrut HMIS due to insufficient server side object level authorization validation in the API endpoint. An unauthenticated remote attacker could exploit this vulnerability by modifying the parameter value in the API request.
Successful exploitation of this vulnerability could allow the attacker to enumerate and gain unauthorized access to sensitive information of patients on the targeted healthcare organization.
Zammad before 7.2.3 contains a missing authorization vulnerability that allows authenticated customers to delete agents' shared ticket drafts by supplying a shared_draft_id. Attackers can create tickets via POST /api/v1/tickets or reply to accessible tickets referencing a draft id, destroying draft text prepared by agents.
This vulnerability exists in e-Sushrut HIMS due to the use of a static and predictable value in the client-side password hashing mechanism, which is embedded in the login page and accessible to unauthenticated users. An unauthenticated remote attacker could exploit this vulnerability by accessing the login page, extracting the embedded value and using it to reproduce the password hashing process.
Successful exploitation of this vulnerability could weaken the security of the authentication mechanism and potentially facilitate authentication related attacks on the targeted healthcare organization.
WordPress Core versions 4.7.0 through 7.1.3 contain a remote code execution vulnerability due to predictable, web-accessible staging paths during full-package core upgrades. This flaw allows unauthenticated attackers to execute code on the server during the upgrade window. Multiple versions prior to fixed releases are affected. The issue has been addressed in versions 5.7.21, 5.8.19, 5.9.20, 6.0.18, 6.1.16, 6.2.15, 6.3.14, 6.4.14, 6.5.14, and 6.6.11.
Apache ZooKeeper versions 3.8.0 through 3.8.7 and 3.9.0 through 3.9.6 contain a vulnerability where unbounded recursion during snapshot serialization can exhaust the JVM stack. A client with permission to create znodes can craft a deeply nested znode structure that causes the server's snapshot thread to crash, resulting in a denial of service. This denial of service is persistent because the server fails to recover on restart due to the same deep tree being rebuilt from the transaction log, potentially causing data loss. The issue can propagate across an ensemble affecting leader and follower nodes. Fixed in versions 3.8.8 and 3.9.7.
Apache ZooKeeper versions 3.7.0 through 3.9.6 are vulnerable to a denial of service caused by unbounded memory allocation in the multiRead request handler. A remote attacker can send a small request that references a large znode multiple times, causing the server to exhaust JVM heap memory and crash. The vulnerability arises because the multiRead handler does not limit the number of read operations or the cumulative response size in memory. Version 3.9.7 introduces configurable limits to mitigate this issue.
Apache ZooKeeper contains a vulnerability in its quota subsystem that allows unauthenticated attackers to cause a persistent denial of service by crashing the server's critical request-processing thread. This occurs due to improper handling of exceptional conditions when writing under the /zookeeper/quota subtree, which is world-writable by default. The issue affects versions up to 3.9.6 and can render the on-disk data directory permanently unbootable. Fixed versions are 3.8.8 and 3.9.7.
Apache ZooKeeper contains an improper authorization vulnerability in its SASL authentication on the client port. When enabled, the server grants any client-requested authorization identity without verifying it against the authenticated principal if the principal is not covered by auth_to_local rules. This allows an authenticated client to assume arbitrary SASL identities, including superuser access if the identity matches a configured superUser. The issue is fixed in versions 3.8.8 and 3.9.7.