The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to time-based SQL Injection via the 'staff_ids' parameter in all versions up to, and including, 27.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires a two-request chain: an attacker first calls the unauthenticated bookly_get_form_id action to seed a booking session carrying malicious staff_ids values, then triggers bookly_render_time to cause the tainted array to reach the vulnerable query; CSRF/nonce validation is absent on both endpoints, meaning this chain can be initiated cross-site.
In the Linux kernel, the following vulnerability has been resolved: x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled The architecture updates the cpu_mask in a domain's header to track which online CPUs are associated with the domain. When this mask becomes empty the architecture initiates offline of the domain that includes calling on resctrl fs to offline the domain. If it is a monitoring domain in which LLC occupancy is tracked resctrl fs forces the limbo handler to clear all busy RMID state associated with the domain. The limbo handler always reads the current event value associated with a busy RMID irrespective of it being checked as part of regular "is it still busy" check or whether it will be forced released anyway. When reading an RMID on a system with SNC enabled the "logical RMID" is converted to the "physical RMID" and this conversion requires the NUMA node ID of the resctrl monitoring domain that is in turn determined by querying the NUMA node ID of any CPU belonging to the monitoring domain. When the monitoring domain is going offline its cpu_mask is empty causing the NUMA node ID query via cpu_to_node() to be done with "nr_cpu_ids" as argument resulting in an out-of-bounds access. Refactor the limbo handler to skip reading the RMID when the RMID will just be forced to no longer be dirty in the domain anyway. Add a safety check to the architecture's RMID reader to protect against this scenario.
The Hubuum client library for Rust versions prior to 0.6.1 can expose sensitive data through its default diagnostics. This occurs because error handling and diagnostic outputs may include full request URLs with query parameters, server response bodies, and other secret-adjacent details. Applications that log these diagnostics risk writing sensitive information such as credentials, tokens, and internal data to logs. The issue is addressed by redacting sensitive query values and sanitizing diagnostic outputs to exclude secret or sensitive content.
Budibase server versions up to 3.38.1 have a critical vulnerability where stored REST datasource credentials (Bearer/Basic tokens and static headers) are attached to outgoing requests without verifying the destination host. This allows an unauthenticated attacker to craft a query with a request path pointing to an attacker-controlled server, causing the server to leak sensitive credentials. The vulnerability is exploitable via the public role, requiring only one HTTP request. Credentials are masked in the API but can be recovered in cleartext through this flaw.
Budibase server contains an authenticated Server-Side Request Forgery (SSRF) vulnerability via DNS rebinding in two outbound fetch paths: OpenAPI import and REST query execution. A builder-level user can cause the server to issue HTTP requests to internal or loopback addresses by exploiting a gap between hostname validation and actual DNS resolution during fetch. This bypasses Budibase's outbound fetch protections, allowing access to internal services that should be blocked.
In Eclipse BaSyx Go Components versions up to and including 1.0.0, ABAC-enabled deployments are vulnerable to an authorization bypass caused by inconsistent trailing-slash handling between the ABAC middleware and the HTTP router.
The shared router configuration used Chi's `middleware.StripSlashes`, so a request such as `GET /shells/` was dispatched to the registered `GET /shells` route. However, the ABAC middleware evaluated the original request path including the trailing slash. If ABAC route lookup did not find a matching slash-suffixed route, the request was passed onward and the router then stripped the slash and executed the protected handler without the intended ABAC authorization decision and without the expected ABAC query filters.
An unauthenticated or unauthorized network attacker could append a trailing slash to protected API routes to reach handlers that should have been denied by ABAC policy. Depending on the exposed component, HTTP method, and deployed policy, this could allow unauthorized read, create, update, delete, or upload operations.
The issue affects ABAC-enabled deployments of services that use the shared router and ABAC middleware, including AAS Repository, Submodel Repository, AAS Registry, Submodel Registry, Concept Description Repository, Discovery, AAS Environment upload, and related services. The issue is fixed in Eclipse BaSyx Go Components v1.0.1.
The AI Copilot – Content Generator plugin for WordPress is vulnerable to generic SQL Injection via 'order[0][dir]' Parameter in all versions up to, and including, 1.5.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The required waic-nonce is emitted on the front-end whenever the [waic_form] or [aiwu-form] shortcode is rendered, enabling contributor-level users who can publish shortcodes to obtain a valid nonce and reach the vulnerable AJAX handler, which performs no capability check beyond nonce verification when the shortcodes are not already embedded in a page.
The Tickera – Sell Tickets & Manage Events plugin for WordPress is vulnerable to generic SQL Injection via the 'tc_event_filter' parameter in all versions up to, and including, 3.6.0.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with staff-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The vulnerable code path is reachable by users holding the plugin's custom Staff role, as the plugin's add_required_capabilities() function grants that role the edit_tc_tickets_instances capability, providing access to the tc_tickets_instances admin list screen where the filter is applied.
NLnet Labs Unbound versions 1.22.0 through 1.25.1 have a vulnerability in DNS-over-QUIC (DoQ) query handling where client-terminated queries are not properly accounted for. This causes an inflation in the count of waiting replies for in-flight queries, leading to degraded resolution service for new clients. Exploitation requires Unbound to be compiled with DoQ support and configured with a quic-port, as well as an attacker controlling multiple source IPs to bypass default limits.
Unbound versions 1.9.0 through 1.25.1 contain a vulnerability in the DNSCrypt TCP query handling where the reply encryption routine does not properly bound the reply length against the destination buffer size. This can cause a heap buffer overflow when processing replies larger than 65504 bytes, leading to a denial of service via resolver crash. The vulnerability requires Unbound to be compiled with DNSCrypt support and configured to enable the 'dnscrypt:' clause on listening interfaces.
This update for unbound fixes the following issues:
Update to version 1.25.2.
Security issues fixed:
- CVE-2026-14586: DoS via assertion in `libngtcp2` for DNS-over-QUIC environments with high concurrency (bsc#1271879).
- CVE-2026-32665: Remote DNS-over-QUIC denial of service due to `quic-size` budget bypass (bsc#1271873).
- CVE-2026-40691: DoS due to heap overflow via single bad DNSCrypt query over TCP (bsc#1271875).
- CVE-2026-41637: Degradation of resolution service due to improperly accounted client-terminated DNS-over-QUIC queries
(bsc#1271891).
- CVE-2026-42955: Ghost domain window can be extended by up to one cached TTL configured value for A/AAAA glue records
(bsc#1271892).
- CVE-2026-44621: Libunbound applications configured with `unwanted-reply-threshold` could eventually be abruptly
terminated (bsc#1271876).
- CVE-2026-44687: Off-by-one error in `harden-below-nxdomain` logic can shadow a stub/forward zone by a legitimate
parent's `NXDOMAIN` (bsc#1271893).
- CVE-2026-44690: Cross-zone wildcard cache poisoning via `RRSIG.labels` manipulation (bsc#1271877).
- CVE-2026-46582: Replay of a wildcard `rrset` as another piece of data triggers poisoning in the server expired reply
path (bsc#1271894).
- CVE-2026-50045: `max-global-quota` bypass via single client queries for a deeply nested name under a DNSSEC-signed
parent (bsc#1271878).
- CVE-2026-50046: Possible heap use-after-free in an error path when a DoT forwarded query is jostled out (bsc#1271882).
- CVE-2026-50243: `response-ip`/`rpz` can rewrite BOGUS answers instead of returning SERVFAIL (bsc#1271880).
- CVE-2026-50248: BOGUS configured primary hostname accepted for XFR in auth/rpz zones (bsc#1271881).
- CVE-2026-50251: Attacker supplied `0.0.0.0`/`::` glue triggers defensive full-cache flush (bsc#1271883).
- CVE-2026-50252: Possible cache poisoning attack by mapping source port population per thread (bsc#1271884).
- CVE-2026-54478: DNS Cookie bypass when proxy-protocol with with `answer-cookie:yes` is used (bsc#1271895).
- CVE-2026-55708: Privacy/configuration issue when adding local data in views through `unbound-control` (bsc#1271896).
- CVE-2026-55717: `serve-expired-client-timeout` and `response-ip` CNAME redirect could lead to a crash (bsc#1271886).
- CVE-2026-55973: DoS due to stack overflow triggered crash when `dns-error-reporting: yes` is set (bsc#1271874).
- CVE-2026-55990: Crash via crafted client UDP query due to DNSCrypt faulty configuration (bsc#1271887).
- CVE-2026-55991: Remote DNS-over-QUIC (DoQ) flow-control reacheable assertion failure in `libngtcp2` (bsc#1271888).
- CVE-2026-56416: Possible heap buffer overflow when validator canonicalizes RDATA that contains domain name
(bsc#1271889).
- CVE-2026-56444: Degradation of resolution service when `discard-timeout` and `serve-expired-client-timeout` are
combined in unusual configuration (bsc#1271890).
Other updates and bugfixes:
- Version 1.25.2:
+ Features:
* TTL behavior changes: cached records reaching TTL 0 are expired;
TTL 0 upstream answers are no longer cached by cachedb;
serve-expired-reply-ttl is now capped by the original TTL value;
TTL decoding updated to adhere to RFC 8767 section 4
* Add new statistics: num.queries.replyaddr_limit and
requestlist.current.replies
* Add 'log-thread-id' configuration option to log the system-wide
Linux thread ID for easier debugging
* Add ECC-GOST12 support per RFC 9558 (available as
contrib/gost12.patch)
* Allow synthesized DNAME TTL=0 to be served from cache within a
1-second grace period, reducing recursion for TTL=0 DNAMEs
(RFC 2308)
* Fix DoT/DoH/DoQ to reload certificates on config reload without
requiring a full restart; fast_reload now supports changes to
tls-service-key, tls-service-pem and tls-cert-bundle
* Allow ip@port notation in control-interface configuration
* Add iter-scrub-rrsig option (default: 8) to limit the number of
RRSIGs processed by the scrubber
* Add 'tls-protocols' configuration option to select which TLS
protocol versions are used; TLSv1.2 is re-enabled by default
* Add pthread_setname_np support for named threads
+ Bug Fixes:
* Fix handle leak in pythonmod on pythonmod_init
* Fix crash when mesh_detect_cycle_found() is called with no mesh
state
* Fix modstack_call_init to use the original string when it has
changed
* Fix fr_atomic_copy_cfg
* Fix auth-zone empty label for $ORIGIN when downloading via HTTP
* Fix respip and dns64 to be usable simultaneously; RPZ now works
with DNS64
* Fix HTTPS and QUIC not being enabled when port is listed in
interface-automatic-ports
* Allow wait-limit-cookie: 0 to disable cookie-validated wait limits
* Fix FIPS mode in OpenSSL causing unit test failure
* Fix discard-timeout to only drop UDP, not stream connections
* Reply with SERVFAIL when the wait-limit is exceeded
* A
In NLnet Labs Unbound 1.4.22 up to and including 1.25.1, UDP source port is randomized and intended to serve as a secret value that increases the entropy of DNS transactions. When resolver load balancing policies depend on the source port while their outcome is revealed this secrecy is undermined. The vulnerability arises when the load balancing policy is consistent with respect to the incoming source UDP port and IP address while heavily depending on the incoming source UDP port as a randomization source. When the SO_REUSEPORT configuration option is enabled ('so-reuseport: yes') in Unbound (by default), it meets these conditions, making it vulnerable for DNS cache poisoning attacks. Upon startup, Unbound randomly partitions the available UDP source port space into disjoint subsets of (almost) equal size, assigning each subset to a specific worker thread. When an incoming DNS query is received, the kernel’s SO_REUSEPORT load balancing mechanism deterministically assigns the query to a socket associated with a particular thread. All outgoing DNS queries generated during the resolution of that request use source ports selected exclusively from the port subset assigned to the corresponding thread. Since these port subsets are disjoint across threads, the source port observed in a resolver’s outgoing query to an authoritative name server serves as a reliable indicator of the worker thread that processed the original client query. A malicious actor can acquire the mapping between incoming UDP source ports (for a given fixed source IP address) and Unbound worker threads and leverage it to conduct DNS cache poisoning attacks by effectively lowering the random port population per thread.
In NLnet Labs Unbound 1.16.2 up to and including 1.25.1, a similar vulnerability as with CVE-2026-40622 in the 'ghost domain names' family of attacks was found in Unbound that could extend the ghost domain window by up to one cached TTL configured value for A/AAAA glue records. Similar to other 'ghost domain names' attacks, an adversary needs to control a (ghost) zone and be able to query a vulnerable Unbound. A single client A/AAAA query can cause Unbound to overwrite the cached expired parent-side glue rrset and essentially extend the ghost domain window by up to one cached TTL configured value ('cache-max-ttl'). In configurations where 'harden-referral-path: yes' is used (non-default configuration), no client query is required since Unbound implicitly performs that query. This is a variant of CVE-2026-40622 which only addressed the NS query.
n8n before 1.123.64, 2.29.8, and 2.30.1 fails to enforce the "Allowed HTTP Request Domains" restriction on HTTP-based credentials (Header Auth, Basic Auth, Query Auth, OAuth) in the GraphQL node, unlike the HTTP Request node. An authenticated user able to create or edit workflows can point the node's endpoint at a server they control and exfiltrate restricted credentials. Only instances where a credential has "Allowed HTTP Request Domains" configured and is usable by non-owner users are affected.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead to denial of service via Exponential Data Expansion (CAPEC-197). An authenticated user may submit a specially crafted query to the ES|QL engine that causes exponential CPU consumption during query evaluation. Because the resource exhaustion persists beyond query completion, repeated requests can fully exhaust the available query worker resources, rendering ES|QL queries unavailable until the node is restarted.
Authorization Bypass Through User-Controlled Key (CWE-639) in Kibana can lead to information disclosure via user-supplied identifiers that reference scheduled query result data from Kibana Spaces the requester is not authorized to access.
Uncontrolled Recursion (CWE-674) in Elasticsearch can lead to denial of service via a specially crafted search request submitted by a low-privileged authenticated user. A user with read-level index access can submit a request that triggers unbounded recursive processing within the Elasticsearch query evaluation component, causing a fatal error that terminates the affected node. In single-node deployments, this results in complete service outage; in multi-node clusters, it causes repeated node restarts and sustained availability degradation.
Reachable Assertion (CWE-617) in Elasticsearch can lead to denial of service via Input Data Manipulation (CAPEC-153). A specially crafted search request containing a null value in a specific query clause causes an internal assertion to be raised during query parsing. Because Elasticsearch treats assertion failures as fatal errors, this terminates the affected node process. A low-privileged authenticated user with read access to at least one index can exploit this condition with a single request to cause a node to terminate, disrupting search availability. In a single-node deployment this fully stops Elasticsearch; in a multi-node cluster it reduces cluster capacity for each affected node.