Server-side request forgery in NoMachine's nxhtd web service lets unauthenticated remote attackers make the service fetch attacker-chosen URIs in the context of the NoMachine service account. Affected installations are those exposing the nxhtd listener, described as using port 4443 by default; exploitation requires only network reachability to that service. Impact is bounded to low confidentiality and integrity, and this is a moderate-priority issue rather than a critical emergency; no public exploit was identified at time of analysis.
Splunk SOAR (On-premises) below 8.7.0 exposes authentication token values to authenticated users who hold the 'Users and Roles view' permission because the REST API accepts caller-controlled query filters on sensitive user-record fields. An attacker with that role can use filter-based inference to recover other users' tokens and, if a recovered token belongs to an administrator, escalate to full administrative control of the SOAR instance. The vendor rates this 7.2 High using CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, while independent assessment places it at CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; no public exploit was identified at time of analysis and there is no CISA KEV listing.
Cross-organization schedule deletion and disabling in Trigger.dev before 4.5.6 allows authenticated users with their own project schedule route to target another organization's IMPERATIVE cron schedule by supplying the victim schedule's friendlyId to delete or disable actions. The flaw is a CWE-639 authorization bypass/IDOR in DeleteTaskScheduleService and SetActiveOnTaskScheduleService, which resolve the friendlyId without scoping it to the caller's organization; exploitation requires authentication and knowledge or enumeration of the victim's friendlyId, and impact is limited to schedule integrity/availability with no data disclosure. No public exploit was identified at the time of analysis, and CISA KEV does not list this CVE.
Privilege escalation in the Multicluster Global Hub Operator lets an attacker who already controls the operator or holds its service-account credentials impersonate arbitrary users, groups, and service accounts cluster-wide, then use that identity to obtain full administrative control. The issue is rated CVSS 3.1 7.2 HIGH (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) and stems from an overly permissive RBAC configuration in multicluster-global-hub-operator-bundle. No CISA KEV listing, EPSS score, or public exploit code is present in the supplied data; no public exploit identified at time of analysis.
Trigger.dev deployments before 4.6.2 return environment-wide S2 stream credentials to any caller who presents a public token with session write access and initializes session input, letting that narrowly scoped token reach every stream in the environment. With the leaked credential, an attacker talks to the S2 storage API directly to append to, create, or trim other sessions' and runs' streams, forging job output or permanently deleting records. Integrity and availability are both assessed high while confidentiality is unaffected, and exploitation is gated on possession of a valid session-write-capable public token (authenticated, PR:L) with no public exploit code or CISA KEV entry identified at time of analysis.
Trigger.dev prior to 4.7.0 fails to enforce ownership checks on the parentRunId supplied to batch-creation endpoints, allowing authenticated holders of unrestricted environment API keys to suspend, indefinitely block, or inject errors into runs they do not own, including cross-organization or production runs on shared deployments. The flaw is rated CVSS 7.2 and is an IDOR-style missing authorization issue (CWE-639); no public exploit code or CISA KEV entry was identified at time of analysis. Risk is concentrated in multi-tenant or shared instances where foreign run IDs are reachable, and is materially lower in isolated single-tenant deployments.
Trigger.dev before 4.6.0 fails to enforce organization scoping in the waitpoint token wait endpoint, allowing an authenticated attacker who holds any valid secret API key to supply another organization's run ID and make that run block indefinitely on a waitpoint the victim cannot complete; the same path can also inject resume data into the targeted run. This is an IDOR-class authorization flaw (CWE-639) affecting default multi-tenant deployments prior to 4.6.0, with the greatest practical impact on shared instances where keys from one organization can reference another organization's runs. No public exploit identified at time of analysis.
Authenticated NoSQL injection in Trudesk through 1.2.11 lets any low-privilege account manipulate the MongoDB $where clause in GET /api/v1/tickets/search, causing high-impact denial of service by looping mongod and exposing full ticket documents including internal notes. The flaw requires a valid account, so exploitation is not possible pre-auth, and no public exploit was identified at time of analysis. Risk is moderate and centered on malicious or compromised low-privilege users rather than anonymous internet attackers.
Authenticated users of Cerberus FTP Server (all releases prior to 2026.3.0) can supply a UNC/SMB path such as \\attacker-host\share into a parameter that accepts path values, causing the service to initiate an outbound SMB authentication and thereby leak the Cerberus service account's Net-NTLMv2 hash to an attacker-controlled listener. Impact is credential exposure rather than code execution: confidentiality is rated high while integrity and availability are unaffected, and the assessed vector requires an existing authenticated session (PR:L) with no user interaction. No public exploit code was identified at time of analysis and the issue is not in CISA KEV; exploitation additionally depends on the server being permitted to reach the attacker over outbound TCP 139/445, so the practical risk is moderate and environment-dependent.
Crafted /inference/v1/generate requests can permanently stall vLLM before 0.31.0 by killing the EngineCore input thread with an uncaught VLLMValidationError while /health continues to return 200. The trigger is a generate request that sets max_tokens to null-causing the min_tokens <= max_tokens validation to be skipped-together with an oversized min_tokens value, after which all subsequent generation requests hang until a manual restart. This is an availability-only flaw (CWE-248); the supplied CVSS 4.0 vector scores it 7.1 with PR:L, while our independent assessment uses CVSS 3.1 with PR:N, so authentication or network ACLs in front of the inference API materially reduce exposure, and no public exploit identified at time of analysis.
Denial of service in Pillow 11.0.0 through 12.x lets an attacker-supplied PNG file consume unbounded CPU time when the application parses its EXIF metadata. Because PngImagePlugin accepts an uncapped eXIf chunk, a file stuffed with repeated six-byte 'Exif\x00\x00' headers causes Exif.load() to make a new shrinking copy of the buffer on every loop iteration, producing quadratic work that is triggered through routine calls such as Image.getexif(), Image._getexif(), or ImageOps.exif_transpose() - the latter backing many photo-upload auto-rotation workflows. The CVSS 4.0 score is 7.1 (assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H), reflecting a pure availability impact with no confidentiality or integrity loss; no public exploit code or CISA KEV entry was identified at time of analysis, and a vendor fix ships in 13.0.0.
Heap buffer over-read in Pillow's Windows-only WMF/EMF renderer (versions prior to 13.0.0) lets a crafted wide, short metafile trigger out-of-bounds memory reads during rasterization. Pillow passes unchecked 32-bit metafile dimensions into the native drawwmf handler, which allocates a DIB using 16-bit-truncated width/height fields but then copies pixel data using the original full dimensions; because the truncated geometry keeps the total pixel count small, the image passes Pillow's decompression-bomb check while the copy still walks past the end of the heap buffer. Only Windows deployments that render attacker-supplied metafiles are exposed, and rendering must be explicitly initiated (UI:R); the practical outcome is limited disclosure of adjacent heap memory or a process crash via the enlarged read, with no public exploit identified at time of analysis and no CISA KEV listing.
Memory exhaustion in Pillow's SPIDER image plugin lets an attacker-supplied multi-frame .spider stack file bypass the library's decompression-bomb guard and drive allocations of several gigabytes. The flaw lives in SpiderImageFile.seek(), which reparses a later frame and overwrites self._size without re-running Image._decompression_bomb_check(), so a tiny file with a benign first frame passes Image.open() and then declares enormous dimensions in a later mode-F frame; loading that frame consumes roughly four bytes per attacker-declared pixel. All Pillow releases prior to 13.0.0 that parse SPIDER stacks are affected, and exploitation requires the application to open an untrusted multi-frame SPIDER file and then seek past frame 0 - a niche, passive-interaction path consistent with the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor patch is 13.0.0.
Denial of service in Pillow's legacy TarIO parser (all versions before 13.0.0) allows remote unauthenticated attackers to supply a crafted TAR archive that traps the parser in an uncontrolled loop, consuming a full CPU core and never returning. The exposure is sharply limited because only applications that directly call PIL.TarIO.TarIO on attacker-controlled archives are affected; the default Image.open() path does not reach this parser. No public exploit code was identified at time of analysis, and the raw 7.1 CVSS 4.0 score should be weighed against the non-default API prerequisite and required user or service interaction to supply the malicious archive.
ZenTao PMS before 22.3 permits authenticated low-privilege users to bypass group-based access controls by invoking any controller method whose name contains 'ajax', potentially exposing sensitive data and administrative actions. The flaw in commonModel::isOpenMethod() treats such methods as open, enabling calls such as task.ajaxGetByID, system.ajaxDBAuthUrl, and admin.ajaxChangeTableEngine to read records, retrieve database credentials, trigger CI jobs, and alter tables. Exploitation requires a valid low-privilege session; no public exploit was identified at time of analysis, and the vendor has released 22.3 with an explicit privilege allow-list. The issue is rated CVSS 4.0 7.1 (High) with high confidentiality impact and low integrity impact.
Tenant isolation bypass in Trigger.dev releases before 4.7.3 lets an authenticated user read run metadata and payloads belonging to other tenants by submitting crafted queries to POST /api/v1/query that reference tables through the 'FROM {database.table}' placeholder syntax, including inside subqueries. Only confidentiality is affected - the flaw exposes data but does not allow modification, deletion, or code execution - so the practical exposure is concentrated in shared SaaS or multi-tenant self-hosted deployments, while single-tenant installations have no other tenant data to disclose. Authentication with a valid account is required (CVSS PR:L), no public exploit code has been identified at time of analysis, and the issue is not in CISA KEV; the assigned CVSS 4.0 score is 7.1, though an independent CVSS 3.1 assessment places it at 6.5 given the read-only impact.
Heap-based out-of-bounds read in FreeRDP before 3.32.1 allows an attacker-controlled RDP server to disclose heap memory when a victim pastes a crafted low-bit-depth PNG clipboard payload. The client-side flaw occurs in WinPR's PNG-to-CF_DIB conversion, where a bit-packed buffer is allocated for sub-8-bit PNGs but rows are copied as one byte per pixel, and exploitation requires clipboard redirection plus user paste interaction. Impact is information disclosure only; no public exploit code or confirmed active exploitation was identified at time of analysis.
Cache aliasing in vLLM before 0.31.0 allows authenticated users of a shared deployment to receive another request's cached processed media or reuse first-block KV cache state by supplying colliding EXIF ImageID or cache_salt values. The flaw is only exploitable when image-processing and/or prefix-KV caches are shared across distinct callers or tenants and the attacker can control the relevant cache-key inputs; single-tenant or isolated-cache deployments have no cross-request target. No public exploit identified at time of analysis; the vendor CVSS 4.0 score is 7.1, and the independent assessment rates confidentiality impact high with limited integrity impact.
Dulwich before 1.2.9 can be driven into an infinite recursion loop by a crafted packfile containing an OFS_DELTA object whose delta_offset is 0, causing CPU exhaustion during clone, fetch, cat-file, or internal object lookups. The flaw is availability-only and requires the victim or service to process an attacker-supplied packfile; publicly available exploit code exists.
Client-side denial of service in FreeRDP 3.0.0 through 3.31.x occurs when the smartcard emulation backend processes a server-supplied SCardGetStatusChange reader-state entry with a null szReader name, causing a null-pointer dereference in strcmp/_wcscmp that crashes the RDP client process. Exploitation is server-to-client: an attacker-controlled or compromised RDP server can trigger the crash against a victim who connects using a FreeRDP client with the smartcard channel/emulation enabled, requiring the user to initiate or accept the session. Impact is limited to availability (client crash) with no code execution or data disclosure, and no public exploit has been identified at time of analysis.
Denial of service in FreeRDP 3.32.0: a use-after-free in the drdynvc dynamic virtual channel allows a malicious RDP server to crash the client during teardown by sending one crafted Virtual Channel PDU with a totalLength smaller than the chunk size. The victim must initiate an RDP session to the attacker-controlled or compromised server (UI:P), so passive clients are not exposed; the assessed impact is availability-only with no confidentiality or integrity loss. No public exploit code was identified at time of analysis, and this CVE is not in CISA KEV.
Reflected cross-site scripting (XSS) in the Live Summary for Gravity Forms plugin (versions through 1.2.10) allows remote attackers to execute arbitrary script in a victim's browser by tricking them into visiting a crafted URL. Exploitation requires the victim to interact with the link and the targeted site to have the plugin active alongside Gravity Forms, with the highest risk when an authenticated administrator is tricked. No public exploit has been identified at the time of analysis.
Improper authorization in Trigger.dev 4.5.0 through 4.6.1 lets authenticated holders of a valid public session token obtain presigned S3 write URLs and overwrite their own session's durable chat snapshot, forging the agent's conversation history. The PUT snapshot-url session endpoint lacks a secret-key-only authorization check, and the affected range ends before 4.6.2. No public exploit code has been identified at the time of analysis, and the independent assessment limits impact to the token holder's own session with no confidentiality, availability, or cross-tenant effect.
WarehousePG 6.27.1 through 6.27.6 and 7.2.1 through 7.6.0 permits any authenticated database role to invoke built-in cluster-expansion functions that perform no privilege check, enabling a low-privileged user to hold catalog locks cluster-wide or repeatedly force session reconnections. The result is a sustained availability outage - DDL, temporary table creation, GRANT and CREATE ROLE are blocked until a superuser terminates the offending session - rather than data disclosure or modification. No public exploit code has been identified at time of analysis, although exploitation only requires valid database credentials and network reachability to the cluster.
A stale-state flaw in Zephyr's experimental MCTP-over-I2C+GPIO target binding lets any device that can act as an I2C controller on the shared management bus crash the target with two ordinary transactions, because the selected pseudo-register and data-phase flag are never reset at STOP. The resulting NULL pointer dereference occurs inside the I2C target interrupt handler, so on parts that trap address-0 accesses it produces a fatal exception and device reset or halt; on other parts it degrades to a malformed packet buffer reaching the MCTP stack and silently dropped transmit packets. Only builds with CONFIG_MCTP and CONFIG_MCTP_I2C_GPIO_TARGET=y are exposed, exploitation requires a pre-existing foothold on the same physical bus (compromised peer endpoint or BMC), and no public exploit code was identified at time of analysis; the authoritative assessment scores this as availability-only impact (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) rather than the C:L/I:N variant in the published vector.
Denial of service in vLLM before 0.31.0 allows remote attackers to crash the entire serving instance by forging or reusing a client-supplied multimodal UUID so the P0/P1 processor caches disagree on token placeholders and hit a fatal mismatch. The flaw is reachable only when the deployment serves a multimodal model and exposes the multimodal inference API; text-only vLLM deployments are not affected. No public exploit was identified at time of analysis, and authentication requirements are conflicting in the supplied data: the CVSS 4.0 vector is PR:L while the independent assessment uses PR:N and the description says unauthenticated, so exposure depends on whether the endpoint is protected (vLLM's default server has no authentication per the assessment).
Stored cross-site scripting in the WordPress plugin Ninja Forms affects all versions through 3.15.5, allowing remote unauthenticated attackers to submit crafted form input that is later rendered without proper neutralization when an administrator views the stored entry, at which point the injected script executes in the privileged user's browser session. The flaw is rated CVSS 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L); the requirement that a victim interact with the stored content is the primary limiting factor, and no public exploit code or confirmed active exploitation was identified at time of analysis. Impact is bounded to confidentiality, integrity and availability of the administrative session and whatever that session can reach, but the scope change (S:C) means the malicious script can affect resources beyond the plugin itself, such as the wider wp-admin context.
Stored cross-site scripting in the Strong Testimonials WordPress plugin through version 3.3.12 allows an attacker to place a script payload in testimonial content that executes when a victim views the rendered testimonial, potentially in an administrative or page-rendering context. This is a moderate-priority issue: exploitation depends on a victim viewing the stored content and on whether testimonial submission is reachable by low-privileged users; under the assessed vector the attacker needs at least low-privileged authenticated access, though a public front-end submission configuration can lower that barrier. No public exploit code or confirmed active exploitation was identified at time of analysis.
Arbitrary file deletion and out-of-directory archive extraction in Trudesk through 1.2.11 let authenticated administrators turn backup-management endpoints into filesystem write and delete primitives. Exploitation requires an existing administrator account plus access to DELETE /api/v1/backup/:backup and POST /api/v1/backup/restore, where encoded traversal sequences and unvalidated file values bypass intended directory confinement. No public exploit identified at time of analysis, and no CISA KEV confirmation is present in the supplied data; the supplied CVSS:4.0 score is 7.0 and the independent CVSS:3.1 assessment is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H.
Reflected cross-site scripting in the Geo Mashup WordPress plugin through version 1.13.22 allows remote attackers to execute arbitrary script in a victim's browser via a crafted request, potentially stealing session data or manipulating page content. The CVSS 3.1 score is 7.1 with a changed-scope impact, and the vector requires user interaction from the victim. No public exploit code or confirmed active exploitation was identified at time of analysis.
Stored cross-site scripting in the SureCart WordPress plugin through 4.9.5 lets an authenticated attacker persist malicious script that runs when a victim renders the affected content, enabling browser-session actions under the victim's privileges. The issue is rated CVSS 7.1 High with UI:R and scope change; no public exploit code or CISA KEV confirmation is present in the provided intelligence.
Reflected cross-site scripting (CWE-79) in the ThemeHunk Customizer WordPress plugin, affecting every version through 2.8.7, lets an unauthenticated remote attacker run arbitrary script in a victim's browser by convincing them to open a crafted URL containing the payload. Exploitation hinges on user interaction (UI:R) and is most dangerous when the victim is a logged-in administrator, because the injected script then executes with the privileges of the WordPress admin session; the flaw alone does not yield server-side access. No public exploit code and no CISA KEV entry were identified at time of analysis, and the issue was reported through Patchstack.
Reflected cross-site scripting in the VideoWhisper 'Paid Videochat Turnkey Site' (ppv-live-webcams) WordPress plugin, affecting all versions through 7.5.14, lets an unauthenticated remote attacker inject script into a page that executes in a victim's browser once that victim follows a crafted link. Because the flaw is reflected rather than stored, exploitation is one-victim-at-a-time and depends on user interaction (the attacker must lure an administrator or paying member with an active session on the target site), and the practical payoff is session/credential theft, action forgery, or page defacement within the victim's context rather than server takeover. No public exploit code and no CISA KEV entry were identified at time of analysis, and the plugin's limited deployment base narrows the realistic target pool; reported CVSS is 7.1 (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L), with the assessed vector scoring availability impact as none.
Path traversal in gin-vue-admin through 2.9.2 allows an authenticated administrator to recursively delete arbitrary directories that are writable by the server process by supplying '../' sequences in the pluginName parameter of a POST request to /autoCode/removePlugin. The flaw is rated 7.0 (CVSS:4.0 AV:N/AC:L/PR:H, with high integrity and availability impact and no confidentiality impact); the independent assessment concurs with a 3.1 vector of AV:N/AC:L/PR:H/UI:N/I:H/A:H, so this is a moderate-priority, authentication-gated issue rather than a mass-exploitation threat. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and the practical blast radius is bounded by the admin-level login requirement and by the filesystem permissions of the account under which the Gin server runs.
Unauthenticated remote clients can force Apache Traffic Server's origin_server_auth plugin to sign attacker-chosen AWS request headers with the proxy's own AWS credentials, potentially allowing access to or modification of origin resources permitted to that identity. The issue affects ATS 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0, but only installations using the non-default plugin to sign origin requests with AWS credentials are exposed. The vendor rates it High with a CVSS 4.0 base score of 7.0; no public exploit identified at time of analysis.
HTTP request smuggling in Apache Traffic Server 8.0.0 through 8.1.11, 9.0.0 through 9.2.15, 10.0.0 through 10.1.4, and 10.2.0 allows attackers behind a front-end proxy that pools and reuses upstream connections to desynchronize responses and smuggle requests past that front end. The trigger is a client POST carrying 'Expect: 100-continue' when the origin responds before the request body is read, causing ATS to parse the unread body as the next request on the shared connection. Standalone ATS deployments, or those not fronted by a connection-reusing proxy, are not exploitable; no public exploit code or active exploitation was identified at time of analysis.
Improper link resolution in Cisco Expressway Series (TelePresence VCS Expressway lineage) lets a local attacker holding a valid low-privileged account trick a component running at higher privilege into following an attacker-controlled link, producing file read or overwrite with high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.0). Real-world risk is strongly tempered by the exploitability metrics: the attacker must already be present on the appliance (AV:L), must authenticate with low privileges (PR:L), and must satisfy a non-trivial high-complexity precondition such as a race or specific filesystem state (AC:H), with no user interaction (UI:N) and no remote or unauthenticated path indicated. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Missing scheduler-lock protection in Zephyr RTOS's z_waitq_head() helper lets a local unprivileged user-mode thread race the kernel timer expiration handler against thread abort on multi-core builds, yielding use-after-free and out-of-bounds writes performed in supervisor context along with scheduler state corruption; the more common outcome of a lost race is a kernel crash rather than controlled corruption. Only builds with CONFIG_MP_MAX_NUM_CPUS greater than one and CONFIG_USERSPACE enabled are exposed, since the affected code path is a no-op on uniprocessor targets and the required k_timer_start(), k_timer_status_sync(), k_thread_create() and k_thread_abort() primitives are syscalls. Rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H); no public exploit code or confirmed active exploitation was identified at time of analysis, and the narrow timing window keeps practical risk conditional rather than drive-by.
Out-of-bounds read in Pillow's TIFF encoder before 13.0.0 can disclose process memory or crash the application when TIFF tag values are inconsistent with the actual image data. The issue is not triggered by simply opening a malicious image; exploitation requires an application to save a TIFF using attacker-influenced tag metadata, and the assessed vector (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L) reflects that high precondition. The Pillow 13.0.0 release notes rank it High severity, but no CISA KEV listing, EPSS score, or public exploit code was provided, so no public exploit identified at time of analysis.
Multiple integer overflows in musl libc's regcomp() allow a crafted regular-expression pattern to produce undersized heap allocations and out-of-bounds writes. Any application that compiles attacker-supplied regexes through musl 0.5.0 through 1.2.6 is exposed - notably Alpine Linux, OpenWrt, and embedded musl-linked builds - with a predictable crash as the readily achievable outcome and code execution possible only in application-specific heap/concurrency conditions. Exposure requires unauthenticated remote input reaching regcomp(); no public exploit code and no CISA KEV entry were identified at time of analysis, so quantitative exploitation signals (CVSS, EPSS, KEV, POC) are entirely absent and the risk must be weighed qualitatively.
Denial of service in PowerDNS Recursor 5.3.x before 5.3.12 and 5.4.x before 5.4.8, where a crafted DNS packet containing malicious name-compression pointers can drive runaway decompression of DNS names and exhaust the recursor's CPU, degrading or halting resolution service (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5 High). Unauthenticated remote attackers can trigger it either by sending the packet straight to a reachable recursor port or by luring the recursor into resolving a name hosted on an attacker-controlled authoritative server that returns the malformed response - so open or internet-reachable resolvers carry the most risk, while recursors restricted to trusted internal clients are far less exposed. The flaw ships as part of PowerDNS Security Advisory 2026-12, a seven-CVE bundle whose most serious member (CVE-2026-85555) is a DNSSEC validation bypass and cache poisoning; no CVSS vector, EPSS score, KEV listing or public exploit code was present in the source data, so no quantitative exploitation signal is available and the assessment rests on the vendor advisory text alone (no public exploit identified at time of analysis).
DNSSEC validation bypass and cache poisoning in PowerDNS Recursor lets remote, unauthenticated attackers inject forged DNS records into a validating resolver's cache by abusing the out-of-band NS resolution path, where delegation and NS data obtained during recursion is accepted without adequate DNSSEC validation (assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - integrity-only impact, high attack complexity). Affected are the 5.3.x train prior to 5.3.12 and the 5.4.x train prior to 5.4.8; the flaw is only practically reachable when an attacker can induce the recursor to resolve a name in a zone whose authoritative responses they control or spoof, for example by luring a client query for an attacker-chosen domain. No public exploit code or confirmed active exploitation was identified at time of analysis, and the EPSS score was not available in the supplied data, but the integrity impact on DNSSEC-validating deployments makes this the highest-priority item in advisory SA-2026-12.
Unbounded resource retention in PowerDNS Recursor lets remote clients drive memory exhaustion by repeatedly opening and closing DNS-over-TCP connections. Recursor 5.3.x before 5.3.12 and 5.4.x before 5.4.8 retain entries for closed TCP client addresses until process exit, so the effect is cumulative over long uptimes and can degrade or deny DNS service; the independent assessment is availability-only (CVSS 3.1: 5.3, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L). No public exploit code or CISA KEV entry was identified at time of analysis.
Out-of-bounds read in PowerDNS Recursor's findScopeZero routine affects releases prior to 5.3.12 and 5.4.8 and is reachable by unauthenticated remote clients only when the non-default use-incoming-edns-subnet option is enabled and a scope-zero answer is produced for a query. Triggering the flaw yields limited information exposure and a plausible denial of service via process crash, reflected in the assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L vector, where the high attack complexity stems from the narrow configuration and answer-shape prerequisites rather than attacker-side effort. No public exploit code, EPSS score, or CISA KEV listing was identified at time of analysis, so exploitation has not been observed and quantitative risk signals are absent; this CVE is one of six issues bundled in PowerDNS Security Advisory 2026-12 and is among the lower-severity members of that set.
PowerDNS Recursor releases before 5.3.12 and 5.4.8 can be tied up by a client that opens a connection to the built-in web server/REST API and never completes the TLS handshake, leaving the single web handler occupied and denying web/API access to legitimate users. The flaw is one of seven issues fixed in PowerDNS Security Advisory 2026-12 (tracked as CVE-2026-85557) and only matters where the web server is enabled and reachable, since it is disabled or bound to loopback by default; DNS resolution, cache integrity and DNSSEC validation are unaffected. No public exploit code, EPSS score or CISA KEV listing was provided, and no vendor CVSS vector accompanies this specific CVE, so the recorded impact is limited to availability of the web interface (assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).
TCP connection exhaustion in PowerDNS Recursor lets a remote client drive the resolver to hold excessive numbers of sockets in TIME_WAIT state, degrading or blocking further DNS-over-TCP service. The flaw affects Recursor release trains 5.3.x before 5.3.12 and 5.4.x before 5.4.8 and is one of seven CVEs bundled in PowerDNS Security Advisory 2026-12, where it is rated Medium/Low rather than High. No authentication is needed (assessed vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), impact is limited to availability with no effect on data integrity or confidentiality, and no public exploit code or active exploitation was identified at time of analysis; no EPSS or KEV data was supplied.
Remote unauthenticated denial of service affects Apache bRPC versions before 1.18.0 when the optional RTMP service is enabled, where a single crafted RTMP Abort control message that names the chunk stream currently being parsed triggers a heap use-after-free and crashes the server. Exploitation requires the non-default ServerOptions.rtmp_service configuration and network reachability to the RTMP listener; with that precondition, no credentials, user interaction, or application-level request are needed. The assessed impact is availability-only (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), and no public exploit code, EPSS score, or CISA KEV entry was identified at time of analysis.
Memory and CPU exhaustion in Apache bRPC's Redis-protocol handler lets remote unauthenticated clients inflate server resource usage by sending long inline commands that never terminate with CRLF. The parser sizes its allocation from the current connection buffer and copies the whole buffer before it has located the inline command boundary, because the redis_max_allocation_size guard was enforced only for RESP bulk strings and arrays, not for the inline path. Every bRPC release before 1.18.0 is affected when the optional Redis protocol is enabled and reachable by untrusted clients; impact is limited to denial of service (availability only), with no code execution or data disclosure reported. No public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV), though the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L reflects a low-complexity, unauthenticated network trigger.
Out-of-bounds write in Apache bRPC's Redis RESP parser allows remote unauthenticated attackers who can reach a bRPC server with ServerOptions.redis_service enabled to send an empty RESP array header followed by a bulk string, causing a parser memory corruption and process crash. The independent assessment rates it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, with exploitation limited by the opt-in Redis service and by non-default fatal-log behavior that must fail to abort before the indexed write. No CISA KEV entry or public exploit code was identified at time of analysis, and Apache bRPC 1.18.0 contains the fix.
Memory exhaustion in Apache bRPC's RTMP AMF parser allows unauthenticated remote attackers to consume excessive resources on servers that opt into the RTMP component. Versions before 1.18.0 accept attacker-declared long-string lengths and array element counts without first confirming the payload contains enough bytes, so a small AMF message can force oversized allocations before parsing fails. RTMP is not enabled by default, and no public exploit has been identified at time of analysis.