2026-11-03
Client-side denial of service in FreeRDP xfreerdp before 3.32.2 lets a malicious RDP server crash the connecting Linux X11 client by sending an RDPGFX ResetGraphics PDU with width zero followed by any ordinary bitmap update. The zero dimension passes the RDPGFX parser's bounds check, the resulting failed resize frees and nulls the GDI primary surface without ending the session, and the next bitmap paint dereferences the null pointer in gdi_Bitmap_Paint. Impact is confined to availability (CVSS 4.0 7.1; assessed 3.1 AV:N/AC:L/PR:N/UI:R/A:H with no C or I impact), the user must connect to the attacker-controlled server for exploitation, a public PoC reference exists in the GitHub advisory but is a callback-level harness not verified as working exploit code, and no KEV-listed active exploitation was reported.
CPU exhaustion in FreeRDP 3.32.1 and earlier allows a malicious or compromised RD Gateway to pin one client thread at 100% of a core by completing the RDG tunnel-open exchange and then sending an eight-byte keepalive control header that declares a 65,535-byte body which is never delivered. Only clients that explicitly connect through a gateway (the /gateway option with HTTP or WebSocket transport) are affected; direct RDP connections are not, and the victim must initiate the session, so the practical attack surface is users routed through an untrusted or machine-in-the-middled gateway. Impact is availability-only - the upstream advisory and reproduction confirm CPU spin and a runnable thread, not a crash, memory corruption, data access, or code execution - and the issue is fixed in FreeRDP 3.32.2. The upstream advisory (GHSA-x4x6-2hrm-hvq9) ships a complete proof-of-concept gateway harness that reproduces the spin, but the flaw is not listed in CISA KEV.
Denial of service in FreeRDP 3.17.0 through 3.32.1 can abort the client process when a malicious or relayed RDP server sends a crafted RemoteFX tile and the client is built with verbose WinPR assertions enabled. The abort occurs in the RemoteFX differential decoder and requires the victim to initiate the RDP connection and negotiate the classic RemoteFX surface-bits path; there is no confidentiality, integrity, or memory-corruption impact. A public proof-of-concept is included in the vendor advisory, and the issue is not listed in CISA KEV.
A malicious RDP server can abort a FreeRDP client that has RemoteFX surface decoding enabled by sending a crafted RemoteFX tileset whose RLGR bitstream encodes the value 32767, tripping a checked narrowing conversion in rfx_rlgr_decode and terminating the client process. Only denial of service to that single client process is demonstrated: the advisory explicitly reports no memory corruption, confidentiality or integrity impact, and no effect on other processes. Affected builds are FreeRDP 3.11.0 through 3.32.1 (fixed range ends before 3.32.2, per the published package metadata); the abort is additionally build-dependent because it only fires when the client is compiled with WITH_VERBOSE_WINPR_ASSERT enabled, which is the default in the inspected 3.32.1 CMake configuration but is disabled by some presets and downstream distributions. A complete public proof-of-concept relay script with a documented successful run is included in the upstream advisory; no confirmed active exploitation (CISA KEV) has been reported.
FreeRDP 3.x clients that decode classic RemoteFX graphics and were compiled with WITH_VERBOSE_WINPR_ASSERT=ON can be aborted by a malicious RDP server that sends a crafted RemoteFX region rectangle, giving the server a client-side denial of service (CWE-617 reachable assertion). The malformed rectangle uses x = 65535 while the RDP SurfaceBits destination starts at left = 1, so their sum no longer fits the 16-bit coordinate the client asserts on in rfx_process_message; builds made with verbose WinPR assertions disabled did not crash on the same packet in the vendor's testing, so real-world exposure is gated by build configuration. Exploitation requires a user to connect to an attacker-controlled or redirected RDP server and negotiate RemoteFX (UI:R, PR:N); impact is limited to loss of availability of the connecting client process, with no data, memory-corruption, server, or other-client impact. The issue is not recorded as actively exploited in CISA KEV, while the upstream advisory does publish a detailed loopback proof-of-concept relay script.
Client-side memory exhaustion in FreeRDP 3.0.0 through 3.32.1 lets a malicious or compromised RDP server force large allocations by declaring an enormous DRDYNVC DATA_FIRST Length, exhausting client memory and causing denial of service. The victim must connect to the server and have DRDYNVC negotiated with at least one dynamic virtual channel in DVC_CHANNEL_RUNNING state; the flaw does not provide code execution or data disclosure. A bounded public proof-of-concept reproducer is included in the advisory, but it is not verified as working exploit code, and no CISA KEV listing is provided.
Heap out-of-bounds read in µD3TN's BPv6/BPv7 fragmenter lets a local attacker with low privileges read process memory and reliably crash the bundle daemon (denial of service). A CVSS 3.1 vector of AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H (7.1, High) applies: the attacker must already hold a foothold on the host and be able to get input into the fragmentation code path, but no user interaction is needed, confidentiality and availability impacts are high, and integrity is unaffected. The CPE for d3tn_gmbh:µD3TN carries wildcard version components, so the vulnerable version range is not narrowed in the available data; no public exploit code and no CISA KEV entry were identified at time of analysis, and the only reference is the upstream GitLab work item 290.
Cross-user data disclosure in Instatic before 0.0.21 lets any authenticated user holding only the low-privileged ai.chat and content.edit.own capabilities read other users' private drafts and enumerate rows in the posts system table through the AI/MCP interface. The content_get_document, content_list_documents and content_search_documents tools call the underlying data-row helpers directly and never apply the object-level ownership checks that the normal HTTP data-row route enforces (that route correctly returns 404 for the same request). No content.edit.any, data.system.tables.read or ai.tools.write privilege is needed, and no LLM provider has to be configured because the /_instatic/mcp JSON-RPC endpoint can be called directly with an MCP bearer token; a public PoC reference (reproduction steps and screenshots against 0.0.20) exists in the upstream advisory, though it is not verified as working exploit code, and there is no indication of active exploitation.
Any registered user on HustOJ (versions 24.09.10 through 26.08.19) can delete, lock, or sticky any forum thread - including administrator announcements - because the thread-handling branch of threadadmin.php verifies only that a session exists, never thread authorship or administrative role. Successful abuse yields high integrity impact and partial availability impact on forum content (CVSS 7.1, I:H/A:L, C:N), requires no user interaction, and needs nothing more than a self-registered account on instances that allow open registration. There is no KEV listing and no confirmed working exploit code at time of analysis, though a public reference repository named for this CVE exists and is not verified as functional exploit code; an upstream fix is available in pull request #1192.
TYPO3 sites using the 'mail' extension's newsletter click-tracking can expose recipients' personal data to unauthenticated remote attackers. Requests to the click-tracking middleware that omit the recipient authentication code bypass the validation check, allowing data inserted into tracked newsletter links to be retrieved without credentials or user interaction. The vendor rates the issue medium severity (CVSS 4.0 base 6.9); exploitation is confined to installations that send tracked newsletters containing recipient data, and no public exploit identified at time of analysis.
Heap memory corruption in the check_icmp plugin shipped with Monitoring Plugins 3.0.0-rc1 through 3.0.0 gives a local low-privileged user an out-of-bounds write inside a process that still holds root privileges when check_icmp is installed setuid-root. Passing more than 65,535 hosts, either as repeated -H/--Host arguments or as Host= entries in an --extra-opts ini file, wraps an unsigned short host counter so process_arguments() allocates an undersized hosts array and writes later entries past its end, all before main() performs setuid(getuid()). This is a moderate, locally-scoped privilege-escalation risk rather than an urgent remote threat: there is no remote vector, reliable privilege escalation from the corruption has not been demonstrated, and no public exploit code was identified in the available sources; the fix is enforcing an explicit host-count bound.
Heap-based buffer overflow in the slurmstepd socket handling code of NVIDIA Slurm lets an authenticated local user corrupt heap memory, with the assessed CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0) indicating high confidentiality, integrity, and availability impact. The affected product is captured by the wildcard CPE for nvidia:slurm, and no version-specific fixed release is present in the supplied data. No public exploit was identified at time of analysis, and the vuln.today decision label is this_week.
Denial of service in the Digital I/O function of Welotec TK100, TK500-v2 and TK500-v3 industrial routers lets a remote attacker who already holds high-privilege credentials crash or disrupt availability through insufficient bounds checking. The flaw is a buffer overflow class issue (CWE-120) with a CVSS 4.0 base score of 6.9; confidentiality and integrity are unaffected. No public exploit code was identified at time of analysis, and exploitation is constrained by the high-privilege authentication requirement.
Uninitialized-memory handling in the pybddisasm Python bindings can cause nd_to_text to turn an uninitialized output buffer into a Python return value when the underlying text conversion fails, potentially disclosing residual process memory or crashing the interpreter. The issue is locally scoped (AV:L) and requires low privileges (PR:L); exploitation depends on an application embedding the unmaintained package, passing input that makes conversion fail, and then returning or otherwise using the failed output. No public exploit identified at time of analysis, and the package is no longer maintained, so no vendor patch is expected and migration away from pybddisasm is the effective remediation.
A use-after-free in the pybddisasm Python bindings lets a local, low-privileged consumer of the library read freed heap memory or crash the Python interpreter when it keeps a reference to an element of an INSTRUX array member (such as an entry in the operands/ND_OPERAND list) after the owning INSTRUX object has been destroyed, because the child element does not keep the parent allocation alive. All versions of Bitdefender's pybddisasm package are affected (CPE cpe:2.3:a:bitdefender:pybddisasm:*), and the package is no longer maintained, so no vendor-released patch was identified at time of analysis. The trigger depends on the host application's own object-lifetime handling rather than on network input: no public exploit was identified at time of analysis, and the outcome is bounded to a likely process crash (availability) with only a limited memory-disclosure path (C:L), making this a medium-severity, low-urgency issue rather than a top priority.
Use-after-free in the unmaintained pybddisasm Python bindings lets a local, low-privileged process crash the Python interpreter or potentially read freed process memory when an application retains a structure-valued INSTRUX member reference after the parent object is freed. Exploitation requires a specific application coding pattern - obtaining a member object, letting the parent INSTRUX allocation be released, then accessing the stale member - and there is no remote or unauthenticated path. No public exploit has been identified at time of analysis, the package is no longer maintained, and the practical impact is limited by the narrow trigger and the library's small footprint.
ZipUtil.unpack in zt-zip 1.18.0 and earlier can rewrite the permissions of the extraction output directory itself when an untrusted ZIP contains a self-referencing entry such as '/' or './' that carries attacker-chosen stored Unix mode bits. Applications that unpack attacker-supplied archives are affected; a restrictive output directory (for example owner-only) can be made readable, writable and executable by every local user, weakening the isolation of everything written under it. A public proof-of-concept snippet is included in the vendor's GitHub security advisory; it is not verified as working exploit code against third-party applications, and there is no CISA KEV confirmation, so active exploitation is not established. The vendor-released patch is zt-zip 1.18.1, and the project's priority label places this in the 'this month' remediation window rather than an emergency tier.
Unauthenticated application-name enumeration in Coolify (versions before 4.1.1) lets remote attackers list application names belonging to every team on an instance through the manual GitHub, GitLab, Bitbucket and Gitea webhook endpoints. Because the repository match runs before any webhook secret or signature check, submitting a full_name of '%' (or an empty value) together with a common branch such as 'main' turns the unescaped SQL LIKE wildcard into a match-all and returns the corresponding application names in the response payloads. Impact is limited to name disclosure - no source code, secrets or configuration are returned - and it requires that applications with a matching branch actually exist; the vendor CVSS 4.0 base score is 6.9, our independent assessment is 5.3 (CVSS 3.1), the fix is released in 4.1.1, and no public exploit or active exploitation has been reported.
Server-side request forgery and local file disclosure in Django's GeoDjango module affect 5.2 before 5.2.19, 6.0 before 6.0.10, and 6.1 before 6.1.3, where SpatialReference, the transform() methods on GEOSGeometry/OGRGeometry/GDALRaster, and the OGRGeometry.srs and GDALRaster.srs/srid setters forward attacker-influenced strings to GDAL without restricting its file and network access, letting unauthenticated remote attackers on an affected code path trigger outbound requests or read local files. Exposure is conditional: only applications that pass untrusted spatial-reference strings into these GIS APIs are reachable, and even after patching the file/network blocking is only enforced on GDAL 3.9 or newer. No public exploit code or active exploitation was identified at time of analysis; Django has released fixes in 6.1.3, 6.0.10, and 5.2.19.
Medium-severity server-side request forgery in Django's GeoDjango component allows unauthenticated remote attackers to make a vulnerable server send requests to attacker-selected destinations when crafted GeoJSON containing an external coordinate reference system (CRS) is passed to django.contrib.gis.gdal.OGRGeometry. Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 are affected, while unsupported older series such as 5.1.x, 5.0.x, and 4.2.x were not evaluated and may also be affected. Vendor patches are available, and no public exploit was identified at time of analysis; practical exposure is limited to deployments that use GeoDjango with the GDAL backend and accept untrusted GeoJSON geometry input.
Log injection in Django's GeoDjango form layer lets remote attackers forge or corrupt application log entries by submitting a crafted geometry value to a form built on django.contrib.gis.forms.GeometryField, because BaseGeometryWidget.deserialize() wrote the rejected input into the django.contrib.gis error log without escaping control characters. Affected releases are Django 6.1 before 6.1.3, 6.0 before 6.0.10 and 5.2 before 5.2.19; older unsupported series (5.1.x, 5.0.x, 4.2.x) were not evaluated by the vendor and may also be affected. The CVSS 4.0 base score is 6.9, but the Django security team classifies the issue as low severity and the practical impact is confined to log integrity - newline or ANSI escape sequences can fake log lines or manipulate terminal output when such logs are viewed or ingested elsewhere. No public exploit code was identified at time of analysis.
Memory exhaustion in Django's MultiPartParser affects Django 6.1 before 6.1.3, 6.0.4 before 6.0.10, and 5.2.13 before 5.2.19 when an endpoint accepts multipart file uploads carrying Content-Transfer-Encoding: base64. Remote attackers can send such an upload without authentication or user interaction, causing the base64 content to be buffered entirely in memory regardless of FILE_UPLOAD_MAX_MEMORY_SIZE before upload handlers receive it. Impact is availability-only and rated low by the vendor; no public exploit is identified at time of analysis.
HDF5 through 2.2.0 reads past the end of the heap buffer holding an external link's user data when that link is traversed, because the default traversal callback H5L__extern_traverse() located the target file name and object path with strlen() without ever validating the payload against its recorded size. The flaw is reachable in default operation and requires a crafted HDF5 file whose external link data is not NULL-terminated or is too short to hold both strings; it triggers when a user or application opens an object through that link (CVSS 4.0 6.9, AV:L/PR:N/UI:P, availability high, confidentiality low). No public exploit code was identified at time of analysis and there is no KEV entry; the practical outcome is a crash/denial of service, with the additional possibility that adjacent heap bytes get folded into the file name or object path the library then attempts to open, and the upstream fix is the pull request referenced below (no released patched version independently confirmed).
Argument injection through proxy settings, plus an unchecked checksum-update path in the privileged service, in Securepoint SSL VPN Client v2 on Windows let a non-privileged local user steer OpenVPN operations that execute with NT AUTHORITY\SYSTEM privileges, producing high integrity and availability impact (VC:N/VI:H/VA:H). The proxy-settings vector is the more accessible one: it requires only the ability to set the client's proxy options and needs neither communication with the privileged service nor modification of the protected OpenVPN configuration. Exploitation requires a pre-existing local session on the affected Windows host (AV:L, PR:L, UI:N), so this is a post-foothold local privilege escalation rather than a remote entry point; no public exploit code or confirmed active exploitation is identified in the available data, and the vendor-reported advisory is the reference of record.
Crashing the Linux kernel is possible through a NULL pointer dereference in AMD's amdgpu GPU driver, giving local users a denial-of-service primitive on affected systems. The CVSS 4.0 vector shows local access (AV:L), no privileges (PR:N), no user interaction, and high availability impact only; confidentiality and integrity are unaffected. No public exploit or CISA KEV designation was identified in the supplied intelligence, and the priority is this_month rather than emergency.
Integer overflow in the DDS RGB888 loader of the AMD Compressonator SDK can be reached when a user opens a crafted DDS file, producing an undersized heap allocation and an out-of-bounds read that may crash the process or disclose limited heap memory. The issue is local and requires user interaction; the supplied intelligence records no CISA KEV entry and no public exploit identified at time of analysis, with AMD advisory AMD-SB-6032 as the vendor reference.
Unauthenticated information disclosure in CTFd's /api/v1/teams list endpoint exposes non-public team custom registration fields - emails, phone numbers, student IDs - to anyone who paginates GET requests, but only on instances configured for team mode with public visibility enabled and teams that have populated hidden custom fields. Impact is confidentiality-only and limited (CVSS 4.0 6.9; independently assessed as CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, Medium), with no integrity or availability effect. There is no CISA KEV listing and no confirmed public exploit code at time of analysis, though harvesting is trivially automatable through pagination once the preconditions hold. A vendor patch exists in CTFd 3.8.7.
Remote attackers can forge Strava webhook events against Dreeve before 5.8.0 and cause permanent deletion of imported Strava activities and their streams. The StravaWebhookRequestHandler::handleEvent path does not verify the signature, verify-token, or owner_id, so a crafted DELETE event carrying a known public Strava activity id is accepted when the instance has imported that activity and its webhook endpoint is reachable. The assessed impact is limited to integrity and availability of imported activity data, with no confidentiality exposure or code execution, and no public exploit was identified at the time of analysis; this is a genuine but moderate-priority issue rather than an emergency.
Path traversal in Koodo Reader 2.4.6 and earlier lets an authenticated user of the optional self-hosted HTTP server read arbitrary files outside the upload directory. The attacker uploads a crafted books.db whose 'cover' value contains ../ sequences and then requests /opds/cover/{key}, causing the server to serve a file readable by the Koodo Reader process; the same unsafe path construction affected the OPDS download handler. Exploitation requires the non-default OPDS/self-hosted mode to be deployed and reachable plus privileges sufficient to upload a database (PR:H), so impact is read-only disclosure of files the server process can already access. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor fix is contained in commit cbc79a1.
svg-sanitizer 1.1.0 can fail individual PHP 8 requests when an application passes attacker-controlled SVG input that ends inside an unclosed tag, with a lone '<' being the smallest trigger; the resulting uncaught ValueError escapes catch (Exception) handlers and aborts the request. The impact is availability-only and bounded to the affected request, and the vendor fixes it in 1.1.1. A public PoC reference exists; it is not verified as working exploit code, and no confirmed active exploitation is reported in the supplied data.
HTTP response splitting in Wasmtime's wasi-http p3 implementation lets an executing WebAssembly guest set an unvalidated content-length header when it splices an existing body into a new response, creating inconsistent HTTP framing that can enable response splitting or injection against downstream consumers. Wasmtime releases 46.0.0 through 48.0.6 and 49.0.0 through 49.0.3 are affected; vendor patches are available in 48.0.7 and 49.0.4. Exploitation requires a host that embeds Wasmtime and runs untrusted guests through the experimental wasi-http p3 API, and the assessed impact is limited to HTTP message integrity with no direct confidentiality or availability loss; no public exploit identified at time of analysis.
Quadratic CPU consumption in Mistune's inline link parser allows unauthenticated remote attackers to degrade availability by submitting crafted Markdown containing thousands of balanced nested bracket pairs that never resolve into a valid link. Every version prior to 3.3.3 is affected, and exploitation only requires that a downstream application or background job pass attacker-controlled Markdown into the default parser (mistune.create_markdown() or mistune.html()); no plugin, non-default renderer, or user interaction is involved. The impact is availability-only (no confidentiality or integrity loss), but a small input of tens of kilobytes can pin a request handler or worker for seconds, and a public proof-of-concept reproducer included in the vendor advisory was verified against the 3.3.2 release tag. The issue is not listed as actively exploited in CISA KEV, and no EPSS score was supplied with the source data.
Server-side request forgery in AzuraCast through 0.23.8 lets any station user holding the station-scoped WebHooks permission make the AzuraCast server issue outbound HTTP requests to attacker-chosen internal addresses. The flaw is an incomplete fix for GHSA-3jp3-3wqw-jvw4: the Mastodon (instance_url), Telegram (api), GroupMe (api) and RadioReg (webhookurl) connectors were never routed through the UserUrlFilter guard, so a low-privilege user can point them at loopback, private-network or cloud-metadata endpoints and fire the test webhook endpoint (PUT /station/{id}/webhook/{id}/test) for immediate dispatch, with the response captured in the HTTP log. Exploitation is gated by the WebHooks permission rather than being anonymous, and the highest-impact outcomes (metadata credential theft, Docker-internal pivoting) depend on such endpoints being reachable from the host; no public exploit code was identified at time of analysis and the issue is prioritised as a this-month item rather than an emergency.
Alo Suite's password recovery endpoint '/Account/resetPwd' lacks rate and frequency limits, so remote attackers can repeatedly trigger unlimited reset emails to a single account, flooding the user's inbox and consuming application and mail infrastructure resources (CWE-770). The flaw affects Alo Suite installations exposing the password-recovery feature (CPE cpe:2.3:a:am_system:alo_suite), requires no authentication or user interaction (AV:N/AC:L/PR:N/UI:N), and is assessed as a moderate-severity availability issue with limited impact (CVSS:3.1 A:L; no confidentiality or integrity effect). The trigger is straightforward endpoint abuse per the available sources; no public exploit code or active exploitation is confirmed, though the vendor advisory from INCIBE is available.
Unauthenticated information disclosure in AM Systems Alo Suite allows remote attackers to read records belonging to other companies or users by substituting the object identifier in requests to the '/Companies/Edit/{id}' endpoint. The underlying flaw (CWE-639, IDOR) is a missing authorization check on the supplied identifier, so confidentiality impact is limited but the exposure is tenant-crossing: any reachable deployment of the affected product can be queried for data the requester should not see, and its practical value depends on identifiers being enumerable or predictable. Reported severity is moderate (6.9 on CVSS v4.0; assessed 5.3-equivalent vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), the issue is not in CISA KEV and no public exploit identified at time of analysis, and the vuln.today decision label places remediation in the 'this month' window rather than an emergency response.
AxxonSoft AxxonNet ARP Agent before 3.25.0 writes the plaintext password of the LDAP directory-service account into WARNING-level log entries on Windows and Linux hosts where LDAP user synchronization is configured. A local attacker with low privileges and read access to ARP Agent logs or generated support packages can recover that password, resulting in high confidentiality impact but no integrity or availability impact. No public exploit was identified at time of analysis, and the issue is not listed in CISA KEV; the risk is moderate and locally scoped rather than an urgent remote-exploitation priority.
Plaintext storage of the LDAP directory service account password in Axxon One before 3.1.0 allows a local attacker with read access to the SecurityManager shared configuration or configuration backups to recover that credential from main.conf on Windows or Linux. The assessed impact is confidentiality-only (CVSS:3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N; CVSS 4.0 score 6.8), and the flaw is only meaningful where an LDAP service account password is actually stored. No public exploit identified at time of analysis; the vendor lists 3.1.0 as the fixed version and this is a moderate, vendor-reported disclosure issue rather than an emergency.
Malformed CoAP messages parsed by the Qt CoAP module's QCoapInternalReply::createFromFrame() can crash a CoAP-enabled application or leave it operating on incorrect data, an out-of-bounds read rated 6.7 in CVSS 4.0 (assessed as CVSS 3.1 AV:N/AC:L/PR:N/UI:N/C:N/I:L/A:H). Exploitation requires that the application link Qt CoAP and decode incoming CoAP frames through QCoapInternalReply::createFromFrame(); once such traffic reaches the parser, the CVSS vector PR:N/UI:N indicates no authentication or user interaction is needed. Impact is primarily availability (crash) with low integrity impact and no confidentiality loss claimed; a vendor fix is available, and no public exploit was identified at time of analysis.
An out-of-bounds write in the Zephyr Bluetooth host's GATT client allows a malicious, spoofed or compromised GATT server within radio range to hand a subscribed client more than the 512-octet maximum attribute length defined by the Core Specification, corrupting memory in subscribers that size their receive buffers to that documented limit. Affected releases are Zephyr 3.4.0 through 4.3.1 and 4.4.0 through 4.4.x (fixed in 4.3.2 and 4.5.0), specifically the in-tree LE Audio unicast client and BAP Broadcast Assistant as well as any out-of-tree subscriber that assumes the 512-octet ceiling. Practical exploitation is heavily conditional: the device must already be connected and subscribed to the attacker's handle, and the build must negotiate an ATT MTU above 515 octets, which the shipped defaults (27/69/70/200/265) never reach; the assessed vector (PR:L) reflects that established subscription relationship rather than classic credential authentication, and no public exploit has been identified at time of analysis.
Queue-pointer corruption in libslirp's if_output() lets a guest on a libslirp user-mode network crash the host-side networking process. When burst traffic forces a session to migrate from the fast queue to the batch queue, the code unlinks and reinserts an arbitrary packet via ifm->m_nextpkt instead of the session queue head, leaving the queue pointers inconsistent; the result is an availability-only denial of service (CVSS 6.5, AV:A/AC:L/PR:N/UI:N, C:N/I:N/A:H) with no confidentiality or integrity impact and no demonstrated code execution. Affected deployments are those actually running the slirp/slirp4netns backend - QEMU user networking and rootless Podman/OpenShift container networking among Red Hat Enterprise Linux 8, 9 and 10 and OpenShift Container Platform 4 and 5 - while bridge, tap or passt setups are out of scope. Exploitation requires the attacker to already control a guest attached to that virtual network; no public exploit code has been identified at time of analysis, and this is a medium-severity, availability-only issue rather than a top-priority emergency.
Stored cross-site scripting in the WPVibes AnyWhere Elementor WordPress plugin, affecting all versions through 1.3.0, lets a holder of a low-privileged authenticated WordPress account persist a script payload that later executes in the browser of any user viewing the affected page - potentially including site administrators. The CVSS 3.1 score is 6.5 with a scope change (S:C), reflecting that the injected script runs outside the plugin's own security boundary; the assessed vector is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, so exploitation needs valid credentials plus victim interaction rather than a fully unauthenticated attack. No public exploit code or CISA KEV entry was identified at time of analysis, and the specific plugin field or parameter that fails to neutralize input is not described in the available sources.
Stored cross-site scripting in the Barn2 Posts Table with Search & Sort WordPress plugin through 1.4.14 lets an authenticated low-privilege user inject persistent script that executes when a victim loads the affected table page. The medium-severity flaw (CVSS 6.5) requires a foothold account and victim interaction, which limits real-world exploitation; no public exploit was identified at time of analysis.
Sensitive information exposure in the WordPress plugin AnyWhere Elementor through version 1.3.0 lets low-privilege authenticated users retrieve embedded sensitive data that should not be sent to the client. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/C:H/I:N/A:N, 6.5) means a logged-in account at low privilege on an affected site can remotely read data on the confidentiality side with no interaction and no integrity or availability impact. No public exploit code or CISA KEV entry is part of the available data, and the trigger mechanism is not described in the available sources; risk is moderate and depends on how readily low-privilege accounts exist or can be obtained on a target site.
Memory exhaustion in Elastic APM Server's OpenTelemetry (OTLP/HTTP) intake lets an attacker who can submit OTLP data drive the server out of memory and terminate it, halting all APM and OpenTelemetry ingestion until the service restarts. The flaw is a resource-allocation-without-limits weakness (CWE-770, CAPEC-231 oversized serialized payloads) rated CVSS 6.5 with availability-only impact (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), so it is a moderate-severity denial of service rather than a confidentiality or integrity risk, and only deployments that expose the OTLP/HTTP endpoint are reachable by this path. No public exploit code identified at time of analysis and no CISA KEV listing; vuln.today priority is this_month, and vendor fixes are published as APM Server 8.19.24, 9.4.9 and 9.5.6 under ESA-2026-236.
Heap exhaustion in Elasticsearch's optional analysis-phonetic plugin allows an authenticated user who can write documents to, or run searches against, an index configured with an affected phonetic encoder to drive a node out of memory until it becomes unresponsive or terminates. The flaw is CWE-770 (allocation of resources without limits or throttling) and is reachable remotely with low complexity and no user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5), but only when the non-default plugin is installed and a target index actually uses a vulnerable encoder - prerequisites that substantially narrow the exposed population. Availability is the only impacted property; no public exploit code was identified at time of analysis, and the issue is not on the CISA KEV list, consistent with a this_month remediation priority rather than an emergency response.
A single crafted AMQP packet can crash Elastic Packetbeat by triggering a null pointer dereference in its AMQP protocol parser, producing an unrecovered Go runtime panic that terminates the process and halts network telemetry collection. The flaw is rated CVSS 6.5 (availability-only) and requires no AMQP authentication, but exploitation is constrained to attackers who can inject traffic onto a network segment the sensor actually monitors and only where AMQP protocol analysis is enabled - the CVSS vector is Adjacent (AV:A), so this is not reachable against an internet-exposed service. There is no CISA KEV listing and no public exploit identified at time of analysis; the vendor has published fixed releases (8.19.24, 9.4.9, 9.5.6) under ESA-2026-208, and vuln.today prioritizes it as a this-month item rather than an emergency.
Kibana can disclose the Elasticsearch credentials it uses as a service account to any authenticated user who holds privileges to onboard Observability data, because those credentials are inserted into data sent back to the client during the onboarding flow. The exposure is conditional: it occurs when the Elasticsearch connection credentials are embedded inside the Elasticsearch host URLs in the Kibana configuration, so deployments that keep credentials in separate username/password settings do not appear to expose them through this path. Fixed versions 8.19.24, 9.4.9 and 9.5.6 are published in Elastic security advisory ESA-2026-204; no public exploit has been identified at time of analysis, and the issue is rated moderate with a 'this month' remediation priority rather than an emergency.
Stored cross-site scripting in Cozmoslabs Paid Member Subscriptions through version 3.1.3 allows an authenticated user with low-level privileges to inject script that executes when another user or administrator views the affected page. The plugin does not properly neutralize input during web page generation (CWE-79), and exploitation requires victim interaction with the stored payload, which limits reliability. No public exploit was identified at time of analysis.
A denial-of-service flaw in the GStreamer JPEG 2000 decimator shipped in gst-plugins-bad allows crafted JPEG 2000 media to crash applications that decode it, via integer overflows or division by zero during tile processing. Per the assessed vector (AV:N/AC:L/PR:N/UI:R, C:N/I:N/A:H), the attack is remote but requires the user to open or play the malicious file, and impact is limited to availability - no code execution or data exposure. This is a moderate-severity issue rather than a high-priority emergency; no public exploit is identified in the supplied data, and Red Hat tracks the flaw across Red Hat Enterprise Linux 7, 8, 9 and 10. The only complete fix stated in the sources is updating to GStreamer 1.28.
SQL injection in runZero's search feature lets authenticated low-privileged users retrieve search results belonging to other organizations, breaking tenant-level data isolation. The flaw affects deployments prior to 5.1.261013.1 and has a medium CVSS score of 6.5 with confidentiality-only impact; runZero's hosted-environment logs showed testing but no adversary traffic. No public exploit code or proof-of-concept was identified at time of analysis, and exploitation requires a valid low-privileged account.