The BPF verifier's zero-extension tracking in the Linux kernel can lose track of a register's upper 32 bits across verifier state checkpoints, allowing a loaded eBPF program to leave an arbitrary value in the upper half of a register instead of the zero-extended value BPF semantics require. Exploitation requires the ability to load an eBPF program into the kernel - CAP_BPF/CAP_SYS_ADMIN or a system with unprivileged eBPF enabled - consistent with the assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H vector, and the practical security impact is materially limited to s390, where the JIT depends on the verifier emitting explicit zero extension before 32-bit operations. No public exploit has been identified at time of analysis, EPSS is 0.15% (4th percentile), and the kernel fix is available upstream as commit 7ce090afbf725e25fff29caacce1eaf8459b1117; priority signals are largely concordant toward moderate, 'this week' handling rather than emergency response.
Code injection in Cisco Expressway Series (TelePresence Video Communication Server Expressway) allows a local attacker holding a low-privileged account to execute arbitrary code on the appliance, with high confidentiality, integrity, and availability impact. Cisco found the flaw during an internal hardening review, and the CVSS 7.8 vector is local (AV:L) with low privileges required (PR:L), so risk is confined to deployments where lower-trust users already have credentials on the system. No public exploit code or confirmed active exploitation was identified at time of analysis.
Local privilege escalation in NoMachine on Windows lets any user who can already run low-privileged code on the host obtain SYSTEM-level execution by abusing an overly permissive access-control list on a named pipe exposed by the NoMachine Device Service. The flaw is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8) and requires the Device Service to be installed and running, so it cannot be used for initial access - it is a post-compromise escalation step. No public exploit code was identified at time of analysis and the issue is not in CISA KEV, but successful exploitation yields full confidentiality, integrity and availability impact as SYSTEM; the finding was reported through Trend Micro ZDI as ZDI-CAN-31213 / ZDI-26-773.
Improper privilege management in Cisco Snort 3 allows a locally authenticated low-privilege attacker to escalate privileges on affected deployments, including Cisco Secure Firewall Threat Defense, Cisco UTD Snort IPS Engine, Cisco Cyber Vision, and Open Source Snort 3 installations. Exploitation requires an existing local foothold (AV:L, PR:L) with no user interaction, so the practical risk is post-compromise privilege escalation or abuse of malicious low-privilege local accounts rather than remote attack. No public exploit identified at time of analysis; no CISA KEV active-exploitation confirmation was provided.
User-mode-to-kernel escape in Zephyr RTOS lets a local thread that holds a granted PECI device object turn peci_transfer() into arbitrary supervisor-mode read and write primitives. The syscall verifier z_vrfy_peci_transfer() validated only the outer struct peci_msg and then handed the caller-controlled tx_buffer/rx_buffer pointers and lengths to in-tree drivers (NPCX, IT8xxx2, MCHP XEC), which dereference them in supervisor mode - allowing kernel memory to be overwritten with hardware-supplied bytes, kernel contents to be pushed onto the PECI/eSPI bus, or a supervisor fault via an unmapped address. Scoring is CVSS 3.1 7.8 (AV:L/PR:L, C:H/I:H/A:H) and exploitation is gated on CONFIG_USERSPACE=y, an enabled vulnerable PECI driver, and local code execution in a thread already granted the PECI device; no public exploit code exists at time of analysis and there is no confirmed active exploitation (CISA KEV).
Incorrect authorization in the COM administration API of hMailServer 6.3.4 through 6.3.6 lets a credential holding the serveradmin role *with* an attached domain list - an account an administrator deliberately confined to specific domains - act as full server administrator over COM, and a parallel flaw lets a domainadmin-with-list credential administer domains its list excludes when the COM domain-administrator check is invoked with no domain argument. The result is a privilege escalation from a confined, authenticated (PR:L) administrative account to whole-server control: reading and altering every domain's accounts and mail, renaming or aliasing domains, writing server settings and secrets, and minting additional server-administrator accounts. Exploitation requires local/on-host access to the COM API (via the Control Panel or a script running on the server), only versions 6.3.4-6.3.6 are affected, and serveradmin accounts with no domain list (the intended whole-server administrator) plus help desk, auditor and custom roles are unaffected; no public exploit code was identified at time of analysis and the CVE is not in CISA KEV.
Incorrect permission assignments in Cisco Expressway Series (CWE-732) can let a low-privileged local user read or modify protected resources, producing high confidentiality, integrity, and availability impact. Cisco addressed this issue, along with other internally discovered hardening problems, in Expressway Series hardening releases; no public exploit code was identified at time of analysis. The 7.8 CVSS score reflects local access requirements with low privileges, no user interaction, and unchanged scope, so this is not a remotely reachable or unauthenticated attack path.
Local command execution in Cisco Snort 3 allows an authenticated low-privileged user to run arbitrary commands as the Snort process user by connecting to the unauthenticated control channel socket. This CWE-306 missing authentication flaw is rated CVSS 7.8 (High); exploitation requires local access to the host and the control socket to be enabled, and no public exploit has been identified at time of analysis.
Apache Pulsar deployments using the filesystem packages storage provider allow an authenticated user holding packages permission on any namespace to traverse out of their authorized tenant/namespace and download, overwrite, or delete packages belonging to other tenants or namespaces. The flaw is a CWE-22 path traversal in the unvalidated package version component; exploitation requires package management to be explicitly enabled and the non-default FileSystemPackagesStorageProvider to be configured, so default BookKeeper-backed deployments are not affected. No public exploit code was identified at time of analysis, and exploitation requires at least low-privilege authenticated access unless broker authentication is disabled, in which case any client able to reach the admin REST API can perform the operations without credentials.
ArcadeDB deployments running any version before 26.10.1 can be coerced into executing arbitrary operating-system commands by any authenticated user who can reach the POST /api/v1/command/{database} endpoint, provided the Groovy scripting engine is enabled on the instance. The root cause is a missing authorization check in GremlinQueryEngine.command(), which means role restrictions are never enforced for Gremlin-submitted Groovy code, so even an account holding the read-only 'reader' role can elevate from query access to full server-process code execution. There is no indication of active exploitation in the wild and no public exploit code identified at time of analysis, but exploitation is straightforward for an insider or anyone holding low-privilege credentials, and the attack surface is limited only by whether the Groovy engine is turned on and the API is network-reachable.
Server-side request forgery in the Airbyte OneDrive source connector allows an authenticated low-privileged user to pass a crafted resource URI to the _get_shared_drive_object method, causing the Airbyte server to make arbitrary outbound requests and disclose information in the service account’s context. The flaw affects Airbyte deployments where the OneDrive connector is available, as reflected by the wildcard CPE for airbyte:airbyte, and carries a CVSS 3.1 score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N). No public exploit was identified at time of analysis, and exploitation requires valid authenticated access plus the ability to configure or run the OneDrive source connector.
Server-side request forgery in the Airbyte SharePoint source connector allows an authenticated, low-privilege user to force the Airbyte service to issue arbitrary outbound requests through the unvalidated URI handled by the _get_shared_drive_object method, disclosing information available to the service account's context. Exploitation requires a valid Airbyte account, the ability to use or configure the SharePoint connector, and network reach to the Airbyte instance; available intelligence shows no public exploit identified at time of analysis and no confirmed active exploitation, and the issue is assessed as a credible but second-tier priority. Impact is confidentiality-only (no integrity or availability effect) with changed scope because the requests originate from the service's privileged network position.
Heap-based out-of-bounds write in Pillow's JPEG encoder (9.4.0 through 12.x) can crash a process and may enable code execution when an application re-saves an attacker-supplied image while preserving both an ICC profile and a forwarded COM comment. The flaw is triggered only when the ICC profile exactly fills the 65536-byte encoder buffer, causing libjpeg's free_in_buffer accounting to wrap before the comment is written; exploitation is application-behavior-dependent and heap-layout-sensitive. Vendor-released patch: 13.0.0; no public exploit identified at time of analysis.
Apache Pulsar 2.8.1 through 4.0.13 and 4.1.0 through 4.2.4 can grant an authenticated low-privileged user the proxy's full privilege set - including superuser and tenant-admin rights - on the broker admin REST API, the functions worker, and the binary protocol when their requests are relayed by a Pulsar proxy. Two distinct weaknesses in the proxy-to-broker principal check (CWE-863) are involved: the original principal is authorized with the proxy's authentication data, letting MultiRolesTokenAuthorizationProvider or a custom data-driven provider expand the caller's roles to every role in the proxy's token, and a separate tenant-admin check succeeds whenever the proxy role itself is an admin of the tenant, even under the default provider. No public exploit code has been identified at time of analysis; exposure is limited to deployments that use the multi-role token provider or a data-driven custom provider, or that list a proxy role as a tenant admin.
Malformed padded HTTP/2 DATA frames sent to Apache Traffic Server 8.x, 9.x, or 10.x proxies that forward to HTTP/1.1 origins can trigger an integer underflow and exhaust the origin's worker pool, causing denial of service for proxied traffic. The issue is remotely reachable without authentication or user interaction when HTTP/2 is enabled on the client-facing listener (CVSS 4.0 AV:N/AC:L/PR:N/UI:N; CVSS 3.1 S:C/A:H), and the availability impact is scored against the downstream origin rather than the ATS process itself. No public exploit identified at time of analysis.
Denial of service 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 unauthenticated remote attackers to exhaust a downstream HTTP/1.1 origin's worker pool by sending a truncated HTTP/2 Content-Length value that ATS mishandles when relaying the request. The issue is limited to proxy deployments where ATS accepts HTTP/2 client connections and forwards traffic to an HTTP/1.1 origin; no public exploit code or confirmed active exploitation was identified at time of analysis.
Remote denial of service in NTPsec ntpd 1.1.4 through 1.2.5 lets an unauthenticated network attacker crash the daemon by sending a crafted NTS Authenticator and Encrypted Extension Fields (AEEF) field with an oversized nonce length, but only on instances where Network Time Security is actually configured and enabled. The out-of-bounds read terminates the process, producing a pure availability impact with no confidentiality or integrity loss, and no public exploit code has been identified at time of analysis. The NTS deployment prerequisite - not the default for many NTP installations - substantially bounds the exposed population, making this a genuine but limited availability risk.
Denial of service in Apache bRPC servers that accept HTTP/2 traffic is caused by a malformed DATA frame with the PADDED flag set and a zero-length payload. An unauthenticated remote attacker with network reachability to an h2c- or TLS-ALPN-exposed HTTP/2 listener can trigger an integer underflow and out-of-bounds read, leading to high availability impact; versions before 1.18.0 are affected. No public exploit was identified at time of analysis, and the independent assessment rates the issue as network-reachable, low complexity, and requiring no privileges or user interaction.
Missing authentication in the Trigger.dev CLI MCP server (cli-v3 3.0.0 through 4.5.3) exposes the /sse and /messages endpoints to adjacent-network attackers or malicious web pages while a developer runs 'trigger dev --mcp'. An unauthenticated attacker able to reach the bound port can issue MCP tools/call requests that use the developer's locally stored access token to trigger tasks, cancel runs, list runs, and retrieve run logs; exploitation is limited to active MCP-mode development sessions, and no public exploit was identified at time of analysis.
FreeRDP proxy deployments that lack a target-certificate verification module can be tricked into accepting a self-signed or wrong-hostname certificate, letting a network-positioned attacker impersonate the RDP target and receive proxied session data. The flaw affects FreeRDP 2.0.0 before 3.32.0 and is rated 7.6 HIGH; the assessed CVSS:3.1 vector is AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N. Exploitation requires proxy mode, no configured verification module, and an on-path position on the proxy's outbound connection; no public exploit identified at time of analysis.
Denial of service in NTPsec ntpd 1.1.4 through 1.2.5 allows a remote unauthenticated attacker to terminate the daemon by sending an NTS request that contains an excessive number of NTS Cookie Placeholder extension fields. The flaw is only reachable when Network Time Security is enabled and the daemon is accepting NTS requests; deployments without NTS configured are not exposed. No CISA KEV entry was identified, and no public exploit was identified at time of analysis; the assessed impact is availability-only with no confidentiality or integrity effect.
Denial of service in Apache bRPC before 1.18.0 allows remote attackers to crash the server by sending deeply nested mcpack data to endpoints serving nshead_mcpack, ubrpc, or public_pbrpc requests. The issue is reachable only when the service uses a recursive/self-referential protobuf schema and the endpoint is exposed to untrusted networks; the assessed vector is AV:N/AC:L/PR:N/UI:N with availability-only impact. No public exploit identified at time of analysis.
Assertion failure and null-pointer abort in ISC BIND 9 recursive resolvers terminate the named process, denying DNS resolution to every downstream client until the service is restarted. Only resolvers configured with BOTH a 'redirect' zone AND 'qname-minimization strict' are affected - a non-default, operator-chosen combination that sharply narrows the realistically exposed population, so despite the 7.5 CVSS base score all qualitative signals point to a low real-world priority. The trigger is unauthenticated and remote (PR:N/AV:N, no user interaction), but no public exploit identified at time of analysis and no active exploitation has been reported; vendor fixes are published as 9.20.30 and 9.21.27.
Remote unauthenticated denial of service in BIND 9 recursive resolvers can be triggered by a crafted query sequence when at least two RPZ zones are configured with conflicting recursive-only settings. The issue affects BIND 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, and corresponding -S1 subscription releases, causing an assertion failure and server exit when an RD=1 query is followed by an RD=0 query. ISC advisories reference fixed releases 9.20.30 and 9.21.27; no public exploit code or CISA KEV entry was identified at time of analysis, and exposure is limited to recursive servers with the uncommon mixed-RPZ configuration.
CPU and memory exhaustion in ISC BIND 9 recursive resolvers is possible when a remote, unauthenticated attacker sends a crafted DNS message containing a maliciously large number of a particular message structure, causing disproportionate processing. Affected builds span BIND 9.11.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, and the corresponding subscription editions; risk is highest for internet-reachable recursive resolvers, while authoritative-only or ACL-restricted deployments have a much smaller surface. Vendor patches are available in 9.20.30 and 9.21.27; no public exploit code or CISA KEV active-exploitation entry was identified at time of analysis.
Denial of service in Django REST Framework prior to 3.18.2 allows a remote unauthenticated client to pin synchronous workers for prolonged periods by sending Accept headers packed with a large number of media-type tokens carrying oversized quoted parameter values and many semicolons; the Content-Type header is a secondary, now length-capped, vector. Impact is availability-only (CVSS 3.1 AV:N/AC:L/PR:N/UI:N/A:H, 7.5) and self-healing once requests stop, but on WSGI/sync worker deployments (e.g. gunicorn sync workers) concurrent requests can exhaust the worker pool and take the service offline. No public exploit code and no active exploitation are indicated in the supplied intelligence, and no EPSS score was provided, so this reads as a genuine but bounded availability risk rather than an emergency.
Unauthenticated network access to D365 F&O MCP Server instances prior to version 1.11.0 exposes indexed proprietary X++ source code and metadata through the /mcp JSON-RPC endpoint. The officially documented Azure one-click deployment (infrastructure/azuredeploy.json and infrastructure/main.bicep) defaults the optional apiKey parameter to an empty string and passes it into the App Service API_KEY setting; with that value empty, src/middleware/apiKeyAuth.ts lets requests through without authentication while src/index.ts binds the listener to 0.0.0.0, so any deployer who leaves the key blank and adds no network restrictions or upstream authentication publishes the server to the internet. Attackers can then invoke read/search tools (search, get_object_info, batch_get_info, extension_info, security_info, find_references, find_event_handlers) to harvest business logic, extension and event-handler wiring, and security-role and privilege structure; the CVSS 3.1 score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) matching CWE-306, and no public exploit was identified at time of analysis.
Unauthenticated denial of service in Splunk Enterprise deployments below 10.4.4, 10.2.8, and 10.0.11 is reachable through the Edge Processor package download endpoint in the Splunk Pipeline Builders app. Repeated unauthenticated requests force the Splunk daemon to read and base64-encode the complete package in memory for each request, exhausting system resources and potentially making the service stop responding (CVSS 7.5, CWE-400). Exposure is limited to instances running Edge Processor/Pipeline Builders, and no public exploit identified at time of analysis.
Splunk Enterprise deployments running Splunk Web in versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16 can be taken offline by a single unauthenticated request to the Splunk Web JavaScript logger endpoint, which parses request headers without any limit and can be driven into an unresponsive state. Recovery requires a full restart of Splunk Enterprise, making this an easy-to-repeat availability attack against any instance whose Splunk Web port is reachable by the attacker. The assessed vector (AV:N/AC:L/PR:N/UI:N, availability-only) is consistent with a low-complexity denial of service; no public exploit code or confirmed active exploitation was identified at time of analysis, and the risk is bounded to service availability with no implied data loss or compromise.
Remote denial of service in Cisco Snort 3-based inspection engines, including Cisco Secure Firewall Threat Defense, Cisco UTD Snort IPS Engine Software, Cisco Cyber Vision, and open-source Snort 3, allows unauthenticated remote attackers to crash or disrupt the inspection process by sending crafted traffic that triggers incorrect calculation errors (CWE-682). CVSS 3.1 scores this 7.5 High with vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so impact is availability-only with no confidentiality or integrity effect; exploitation requires the attacker's traffic to traverse an actively inspecting sensor. No KEV entry or public exploit data was supplied, and no public exploit identified at time of analysis.
Denial of service in toml-node versions prior to 5.0.1 allows remote attackers to synchronously block the Node.js event loop by supplying a TOML document containing an extremely long hexadecimal, octal, binary, or decimal integer literal. Because toml.parse() calls BigInt() on the digit sequence before the 64-bit range check runs in reduceInteger(), conversion cost grows super-linearly with digit count, so a single crafted document can stall all concurrent work in the process (CVSS 3.1: 7.5, AV:N/AC:L/PR:N/UI:N, availability-only). The flaw is exploitable only where an application parses attacker-influenced TOML; there is no confidentiality or integrity impact, no public exploit code identified at time of analysis, and the issue is fixed in 5.0.1.
Memory exhaustion in Django REST framework 3.6.4 through 3.18.1 lets a remote unauthenticated client make a single small JSON request balloon into a much larger in-memory body, degrading or crashing the worker that handles it. Because the affected JSONParser ships in the default parser set, any reachable DRF endpoint that accepts a JSON body is a candidate target - the attacker simply names a byte-transform codec such as bz2_codec in the request's Content-Type charset and sends a correspondingly compressed payload. Impact is limited to availability (CVSS 3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) rather than confidentiality or integrity; no public exploit code was identified at time of analysis and there is no CISA KEV entry, so this is a genuine but bounded denial-of-service risk pending upgrade to 3.18.2.
Privilege escalation in Progressive Robot hMailServer 6.3.4 through 6.3.6 allows an authenticated holder of the manage_roles permission - a full-scope API key issued for named domains or a domain-scoped serveradmin account - to strip a narrowing role assignment from a server-administrator-level account and thereby restore that account to full server-admin authority. Because the credential can also reset that account's password while the narrower role is still in place, the attacker can then sign in as the server administrator and take over mail-server administration. Exploitation is conditionally gated and multi-step (CVSS AC:H) and no public exploit was identified at time of analysis, so this is a genuine but not trivially reachable escalation path.
Improperly ordered path validation in GitPython before 3.2.1 enables unauthenticated remote attackers who can influence a submodule path to make create_submodule() clone an attacker-controlled repository into a Git metadata location such as .git/hooks, planting a post-checkout hook that executes arbitrary code when a later checkout occurs. The CVSS 3.1 score of 7.5 (HIGH) is materially tempered by AC:H-the hooks directory must be empty enough for Git to clone into, typically requiring default sample hooks to be absent-and UI:R, since a subsequent Git operation must trigger the hook. No public exploit identified at time of analysis; affected code spans 3.1.x through 3.2.0-affected revisions and is fixed in 3.2.1.
Denial of service in NLnet Labs Unbound versions 1.22.0 through 1.26.1, where a remote DNS-over-QUIC client can crash the resolver by triggering a QUIC path migration at the moment a mesh reply still holds a pointer to the associated DoQ stream. The resulting use-after-free dereferences the freed stream when the pending reply completes, terminating the process and interrupting DNS resolution for all clients of that instance. Exploitation is race-dependent and only possible when DoQ is enabled and Unbound runs multi-threaded; no public exploit code was identified and the issue is not confirmed actively exploited (CISA KEV), so this is a genuine but bounded availability risk rather than a wormable or data-exposing flaw.
Memory exhaustion in the mcpack2pb parser of Apache bRPC before 1.18.0 allows remote, unauthenticated attackers to force large preallocations by declaring an oversized item count in a crafted mcpack array header, with the request body parsed before any authentication check. Impact is availability-only: a count such as 0x7fffffff can drive roughly 16GB of virtual-memory preallocation and abort the process (SIGABRT), most reliably on memory-constrained hosts. No public exploit has been identified at time of analysis and EPSS is low at 0.24% (15th percentile), but the exposure is confined to the non-default Baidu ubrpc deployment pattern that wires NsheadService to UbrpcMcpack2Adaptor with mcpack2pb-generated parsing code.
Information disclosure in Splunk SOAR On-premises (all versions below 8.7.0) allows any authenticated user holding the low-privileged Observer role to recover other users' password hashes and authorization tokens by submitting crafted REST API query filters against user records. The flaw is an ordering problem: filter clauses are evaluated against user objects before Splunk SOAR strips sensitive fields, so an Observer can use boolean or comparison-style filters as an oracle to infer secret values they were never meant to see. Exploitation requires a valid account on an affected on-premises deployment and proceeds indirectly through query behavior rather than a single direct read; no public exploit code has been identified at time of analysis, and the vendor scores this 7.5 while our assessment scopes the realized impact to confidentiality (loss of credentials and API tokens) rather than to integrity or availability.
Crafted IPv4 packets addressed to the router itself can drive the line card network processor on Cisco IOS XR into repeated resets, causing traffic loss and - under sustained attack - a persistent shutdown state that requires manual line card reload to recover. The flaw affects carrier-grade hardware specifically: Cisco ASR 9000 and 9900 Series Aggregation Services Routers plus the ASR 9902 and 9903 Compact High-Performance Routers. No authentication or user interaction is needed (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5), and no public exploit code or confirmed active exploitation was identified at time of analysis; exposure is bounded by the fact that transit IPv4 traffic and all IPv6 traffic cannot trigger the fault.
Denial of service in Cisco Expressway Series allows remote unauthenticated attackers to disrupt availability by triggering uncaught exceptions in network-reachable service code, with CVSS 3.1 score 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). The issue is an internally discovered CWE-248 weakness addressed in Cisco hardening releases; no public exploit or CISA KEV entry is identified at time of analysis. Affected deployments are Cisco Telepresence Video Communication Server (VCS)/Expressway instances that have not applied the fixed releases listed in Cisco advisory cisco-sa-exwy-hardening-FhcqBVcs.
Denial of service in Cisco Expressway Series allows unauthenticated remote attackers to crash the service by triggering a null pointer dereference (CWE-476). The issue is network-reachable, low complexity, and requires no user interaction, with impact limited to availability; exact affected and fixed releases must be confirmed in Cisco's advisory. No public exploit code was identified at time of analysis, and exposure is greatest for internet-facing or externally reachable Expressway deployments.
Network-reachable assertion failures in Cisco Expressway Series (TelePresence VCS Expressway) can terminate video and collaboration signaling services, allowing remote attackers to cause a denial-of-service condition without authentication or user interaction (CVSS 7.5). The vendor advisory describes multiple internally discovered CWE-617 reachable-assertion issues fixed in hardening releases; the exact affected and fixed versions are not specified in the provided data. No public exploit was identified at time of analysis, and there is no CISA KEV confirmation of active exploitation.
Cisco voice and collaboration products - Unified Communications Manager, Unified CM IM & Presence, Emergency Responder and Unity Connection (with Prime Collaboration Deployment and Unified CM SME also named in the advisory) - contain a set of internally discovered flaws in the CWE-703 improper-handling-of-exceptional-conditions class that can be triggered over the network by an unauthenticated remote attacker with no user interaction, disrupting service availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5 HIGH) rates this as a denial-of-service condition only, with no confidentiality or integrity impact. The issues were found during Cisco's own hardening review rather than through external reporting, and no public exploit has been identified at time of analysis; the realistic exposure depends on whether the affected collaboration nodes are reachable from untrusted networks, since these services normally sit on internal management planes.
Denial of service in the Cisco Snort 3 detection engine allows remote, unauthenticated attackers to exhaust device resources and disrupt inspection services on any deployment actively processing attacker-influenced traffic - including Cisco Secure Firewall Threat Defense (FTD), the Cisco UTD Snort IPS engine, Cisco Cyber Vision, and upstream Open Source Snort 3. The flaw is rooted in uncontrolled resource consumption (CWE-400) and carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), meaning only availability is impacted - there is no confidentiality or integrity loss and no code execution. No public exploit code or in-the-wild activity has been identified at time of analysis, and no CISA KEV listing exists; exploitation is gated by the requirement that the target actually sits inline as an IDS/IPS or firewall in a traffic-inspection path.
Path traversal in the Bold Grid weForms plugin for WordPress, affecting versions through 1.6.28, lets an attacker supply a crafted file-path parameter that escapes the intended directory and deletes arbitrary files on the underlying host, giving a primary availability impact (CVSS 7.5, C:N/I:N/A:H). Per the supplied CVSS vector the attack is network-reachable with no privileges or user interaction (AV:N/AC:L/PR:N/UI:N), though that unauthenticated claim is not independently confirmed and the vulnerable endpoint and parameter are not disclosed in the available data; in practice lower-privileged access may be needed. No public exploit code and no CISA KEV entry were identified at time of analysis, and no fixed version is listed in the available references. Signals are moderately consistent but incomplete, so the practical exploitability and any auth prerequisite should be validated against the vendor's Patchstack advisory before prioritizing response.
Failed token revocation in Django REST Framework 3.12.0 through 3.18.1 leaves API credentials live after they are supposedly revoked: calling delete() on a TokenProxy instance issues a DELETE that matches no row, returns a zero count, and raises no error, so applications, admin integrations, or operational scripts that trust the return value believe the credential is gone while it continues to authenticate requests. The defect is a credential-hygiene and failed-revocation problem (CWE-390) rather than a directly exploitable remote flaw - the CVSS 3.1 base score is 7.4 (High) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, and because DRF tokens never expire automatically, any token that escapes revocation stays valid indefinitely until the database row is cleaned up manually. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis; the practical prerequisite is that an attacker already holds a previously issued token that the victim attempted to revoke through the affected code path.
Path-restricted checkout in Dulwich 0.24.0 through 1.2.7 follows symlinks when writing restored files, so a crafted repository can redirect a selective checkout into arbitrary filesystem locations - including .git/hooks/post-checkout - to plant an executable hook and achieve code execution. Exploitation is conditional: the victim must obtain an attacker-controlled repository whose worktree entry is a symlink (mode 120000) pointing at a sensitive path, then explicitly call porcelain.checkout(paths=[...]) against a tag or ref where that same path is a regular executable blob; a plain clone or default full checkout does not trigger it. No public exploit code has been identified at time of analysis, and the issue is fixed in Dulwich 1.2.8.
Arbitrary file write leading to potential code execution affects Dulwich 0.22.5 through 1.2.7 when a victim pops a stash in an attacker-crafted repository, because intermediate directory symlinks are followed and can redirect writes into .git/hooks/post-checkout. Exploitation requires local operation of the affected library plus a multi-step stash workflow and a subsequent checkout, so this is a conditional code-execution risk rather than a drive-by remote compromise; no public exploit code was identified at time of analysis. Dulwich 1.2.8 contains the vendor fix.
Symlink-based path traversal in Dulwich 0.23.1 through 1.2.7 allows an attacker who controls a repository's commit history to write files outside the working directory when a victim runs filter_branch with an index_filter, with code execution possible if the write lands in .git/hooks. Exploitation is conditional: it requires local access and the victim to invoke the history-rewriting operation against the crafted repository, and no public exploit code was identified at time of analysis. Dulwich 1.2.8 fixes the issue by addressing cross-commit symlink persistence.
Truncating a partitioned topic through the Apache Pulsar broker admin REST API succeeds without the caller holding tenant admin or superuser rights, letting an authenticated user wipe consumer backlog and destroy retained data on topics they merely have lookup permission for. The broker proxies each per-partition truncate request through its own internal admin client, so the tenant-admin authorization check is evaluated against the broker's configured identity rather than the caller's, and passes whenever that internal role is a superuser or tenant admin (the usual setup when authorization is enabled). Affected releases are 2.8.0 through 4.0.13 and 4.1.0 through 4.2.4, with fixes in 4.0.14 and 4.2.5; successful exploitation requires a valid authenticated identity, lookup permission on the target, a partitioned topic addressed by its partitioned name, and a suitably privileged broker internal client, and yields high integrity and availability impact with no confidentiality impact. No CISA KEV entry or public exploit code was identified at the time of analysis, and no EPSS score was supplied.
Remote code execution in Splunk Enterprise is possible for authenticated users whose roles include the edit_manager_xml capability; by opening a crafted Manager XML configuration in Splunk Web, they can execute arbitrary operating-system commands with the privileges of the account running Splunk Enterprise. The flaw affects versions below 10.4.3, 10.2.8, 10.0.11, and 9.4.16. No public exploit was identified at time of analysis, and the high-privilege prerequisite confines meaningful exposure to environments where edit_manager_xml is assigned broadly rather than tightly restricted to trusted administrators.