Information Disclosure
Monthly
Case-insensitivity handling inconsistency in Jenkins 2.575 and earlier allows attackers to impersonate existing users or inherit their permissions by registering accounts with Unicode characters that case-insensitively match existing usernames. Jenkins generates canonical user IDs via lowercasing but performs comparisons using Java's `String#equalsIgnoreCase`, which follows Unicode case-folding semantics - for example, the Turkish dotless 'ı' is treated as equal to 'i' during comparison but produces a different canonical ID when lowercased. Exploitation is constrained to deployments using external security realms that permit non-ASCII characters in usernames; no public exploit has been identified at time of analysis.
Arbitrary file write via crafted tar archive extraction in Jenkins 2.575 and earlier allows attackers controlling agent processes to escape extraction directory boundaries on the controller filesystem, directly enabling remote code execution. The root cause is unsafe handling of symbolic links with effectively empty names during .tar and .tar.gz extraction on the controller, permitting writes to sensitive paths such as JENKINS_HOME/init.groovy.d/ (Groovy init scripts) or JENKINS_HOME/plugins/ (plugin deployment). No public exploit or CISA KEV listing has been identified at time of analysis, but the agent-to-controller trust boundary is a well-established Jenkins attack surface with a history of critical exploitation.
Statamic CMS exposes authenticated users' raw two-factor authentication recovery codes through the Antlers templating engine due to a missing access restriction in the `AugmentedUser::get()` resolver. Unlike `password` and `password_hash` fields, which are explicitly excluded from augmentation, `two_factor_recovery_codes` is returned without restriction and is absent from all Antlers variable guard lists. An administrator or developer who has configured a blueprint field with dynamic Antlers rendering enabled can craft a template (`{{ current_user.two_factor_recovery_codes }}`) that, when rendered by a victim visiting the page, leaks that victim's 2FA recovery codes into the HTML response - enabling 2FA bypass. No public exploit has been identified at time of analysis, and exploitation requires a high-privilege prerequisite (blueprint configuration access).
ESPHome's built-in web server unconditionally leaks plaintext passwords stored in password-mode text entities to any unauthenticated attacker on the local network. The web_server component on port 80 - which carries no authentication by default - serializes text entities with a dual-field JSON structure where the 'state' field is correctly redacted to '********' but the 'value' field is always populated with the raw secret via set_json_icon_state_value()/set_json_value(), exposing WiFi credentials, API tokens, and similar secrets through a trivial GET request or the /events EventSource stream. No public exploit code or CISA KEV listing has been identified at time of analysis, but exploitation requires only standard HTTP tooling against any reachable device with the web_server component enabled.
IV reuse in libkcapi's one-shot symmetric cipher operations allows a remote attacker to weaken data confidentiality for applications processing inputs larger than 64 KiB under stateful modes (CTR or CBC). Affected deployments include Red Hat Enterprise Linux 8, 9, and 10, Red Hat Hardened Images, and OpenShift Container Platform 4. No public exploit or active exploitation has been identified; the AV:N vector reflects an indirect attack path where an adversary induces a vulnerable application to process specially crafted oversized inputs, enabling ciphertext analysis to expose plaintext relationships or recover data.
Host header injection in SonicWall SonicOS enables remote unauthenticated attackers to manipulate the HTTP Host header on the firewall management interface, causing redirect responses that send management users to attacker-controlled web domains. Affected version branches span the SonicOS 6.5, 7.0, 7.3, and 8.2 lines, covering a wide installed base of SonicWall firewalls. No public exploit code exists and this vulnerability has not been added to CISA KEV at time of analysis, but the unauthenticated network-accessible attack surface and management-user targeting make it a meaningful phishing risk in environments where the management interface is internet-exposed.
AES-GCM nonce exhaustion in Kong Event Gateway 1.0.0-1.1.1 and 1.2.0 allows an authorized consumer to recover partial message plaintext when the AWS IAM encryption feature is enabled and key rotation has not occurred. Because keys are only rotated on gateway reboot, a producer sustaining a high message rate can exhaust the NIST SP 800-38D-recommended random nonce limit (~2^32 encryptions), making nonce collisions statistically likely and enabling ciphertext XOR attacks. No public exploit exists and the vulnerability is not in CISA KEV; the CVSS 4.0 score of 2.3 reflects the narrow, condition-heavy exploitation path.
Prototype pollution in Eclipse Theia's preference resolution system exposes developers to application-logic manipulation when opening crafted workspaces. The `PreferenceUtils.merge` function in `@theia/core`, invoked for every preference scope resolution, fails to reject reserved JavaScript prototype keys (`__proto__`, `constructor`, `prototype`), allowing a malicious `.theia/settings.json` or `.vscode/settings.json` to corrupt `Object.prototype` across the entire Theia Node.js process. Affected versions span 0.7.0 through 1.73.1 inclusive; no public exploit has been identified at time of analysis, and the CVSS 4.0 score of 5.7 appropriately reflects the social-engineering dependency and required user interaction.
SQL injection in the ZTE Smart Life mobile app enables a local attacker with physical device access to execute UNION SELECT statements against the app's feedback.db SQLite database, extracting sensitive personal data including user account details, phone numbers, feedback content, and local debug log paths. Exploitation is severely constrained by the CVSS:3.1/AV:P/AC:H/PR:L/UI:R vector, requiring physical access to the device, a low-privilege authenticated session within the app, user interaction, and non-trivial attack complexity. No public exploit code or CISA KEV listing has been identified at time of analysis, and the vendor (ZTE PSIRT) has published a bulletin acknowledging the issue.
In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: free fib_alias with kfree_rcu() on insert error path fib_table_insert() publishes new_fa into the leaf's fa_list with fib_insert_alias() before calling the fib entry notifiers. When a notifier fails, the error path removes new_fa with fib_remove_alias() (hlist_del_rcu) and frees it right away with kmem_cache_free(). fib_table_lookup() walks that list under rcu_read_lock() only, so a concurrent lookup that already reached new_fa keeps reading it after the free: BUG: KASAN: slab-use-after-free in fib_table_lookup (net/ipv4/fib_trie.c:1601) Read of size 1 at addr ffff88810676d4eb by task exploit/297 Call Trace: fib_table_lookup (net/ipv4/fib_trie.c:1601) ip_route_output_key_hash_rcu (net/ipv4/route.c:2814) ip_route_output_key_hash (net/ipv4/route.c:2705) __ip4_datagram_connect (net/ipv4/datagram.c:49) udp_connect (net/ipv4/udp.c:2144) __sys_connect (net/socket.c:2167) __x64_sys_connect (net/socket.c:2173) do_syscall_64 entry_SYSCALL_64_after_hwframe which belongs to the cache ip_fib_alias of size 56 Triggering the error path needs CAP_NET_ADMIN and a registered fib notifier that can reject a route; a netdevsim device whose IPv4 FIB resource is exhausted is enough. Free new_fa with alias_free_mem_rcu(), as fib_table_delete() already does for a fib_alias removed from the trie.
In the Linux kernel, the following vulnerability has been resolved: wifi: p54: validate RX frame length in p54_rx_eeprom_readback() p54_rx_eeprom_readback() copies the requested EEPROM slice out of a device-supplied readback frame without checking that the skb actually holds that many bytes. Commit da1b9a55ff11 ("wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()") closed the destination overflow by copying a fixed priv->eeprom_slice_size (and rejecting a mismatched advertised len), but the source side is still unbounded: nothing verifies the frame is long enough to supply that many bytes. A malicious USB device can send a short frame whose advertised len matches priv->eeprom_slice_size while the payload is truncated. The equality check passes and memcpy() reads past the end of the skb, leaking adjacent heap: BUG: KASAN: slab-out-of-bounds in p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) Read of size 1016 at addr ffff88800f077114 by task swapper/0/0 Call Trace: <IRQ> ... __asan_memcpy (mm/kasan/shadow.c:105) p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) p54u_rx_cb (drivers/net/wireless/intersil/p54/p54usb.c:163) __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657) dummy_timer (drivers/usb/gadget/udc/dummy_hcd.c:2005) ... </IRQ> The buggy address belongs to the object at ffff88800f0770c0 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 84 bytes inside of allocated 704-byte region [ffff88800f0770c0, ffff88800f077380) Check that the slice fits in the skb before copying.
In the Linux kernel, the following vulnerability has been resolved: mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n On CONFIG_INET=n builds, mpls_valid_fib_dump_req() walks the parsed attribute table itself instead of calling ip_valid_fib_dump_req(). The RTA_OIF arm passes tb[RTA_OIF] to nla_get_u32() without checking it is present, so an RTM_GETROUTE dump for AF_MPLS with strict checking and no RTA_OIF hits a NULL dereference. RTM_GETROUTE is RTNL_KIND_GET, which rtnetlink_rcv_msg() permits without CAP_NET_ADMIN, so an unprivileged user can trigger it. Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:mpls_valid_fib_dump_req (net/mpls/af_mpls.c:2189) Call Trace: mpls_dump_routes (net/mpls/af_mpls.c:2236) netlink_dump (net/netlink/af_netlink.c:2331) __netlink_dump_start (net/netlink/af_netlink.c:2446) rtnetlink_rcv_msg (net/core/rtnetlink.c:7033) netlink_rcv_skb (net/netlink/af_netlink.c:2556) netlink_unicast (net/netlink/af_netlink.c:1345) netlink_sendmsg (net/netlink/af_netlink.c:1900) __sock_sendmsg (net/socket.c:790) ____sys_sendmsg (net/socket.c:2684) ___sys_sendmsg (net/socket.c:2738) __sys_sendmsg (net/socket.c:2770) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Skip unset attributes, as ip_valid_fib_dump_req() does.
Cluster ID enumeration in SUSE Rancher exposes a reliable oracle via the unauthenticated `/v3/import/{token}_{clusterId}.yaml` endpoint, which performs cluster object retrieval before token validation. Remote unauthenticated attackers can distinguish valid cluster IDs (HTTP 502, triggered by a nil pointer dereference in `pkg/systemtemplate/private_registry.go` when private registry secrets exist) from non-existent ones (HTTP 200), leaking the presence and private-registry configuration status of clusters. This is not listed in CISA KEV and no public exploit code has been identified, but the zero-prerequisite network accessibility makes enumeration trivially scriptable.
Unrestricted brute-force against changedetection.io's /login endpoint allows a remote unauthenticated attacker to systematically guess the single shared application password with no throttling, lockout, or attempt counter to impede automated attacks. Because the entire application is protected by one shared credential with no per-user account model, a successful guess grants full administrative control - including the ability to view and regenerate the API token and access all monitored URL configurations. No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack is trivially automatable given the network-accessible endpoint, low complexity (CVSS AC:L), and complete absence of brute-force controls confirmed by requirements.txt inspection.
Unauthorized information disclosure in the MLSImport: IDX Plugin & MLS Plugin for Real Estate Listings WordPress plugin (all versions before 7.0.4) exposes import log files and import-related post metadata to any authenticated user, including low-privilege subscribers. The flaw stems from a missing authorization and CSRF check on an AJAX action, meaning any logged-in WordPress user on an affected site can invoke the endpoint and read sensitive operational data. A publicly available proof-of-concept exists (reported by WPScan), though EPSS places exploitation probability at 0.10% and SSVC confirms no known active exploitation at time of analysis.
Unauthenticated information disclosure in DHL Shipping Germany for WooCommerce (versions before 4.0.1) exposes stored shipping labels - each containing customer name and postal address - to any visitor who can request predictable filenames from the label storage directory. The plugin relies exclusively on an Apache .htaccess file for directory access control, which nginx and other non-Apache web servers silently ignore, leaving the directory fully browsable over the network. A publicly available exploit exists (via WPScan), though EPSS of 0.14% at the 4th percentile indicates low observed exploitation activity, and the vulnerability is not listed in the CISA KEV catalog.
Information disclosure in the GeoDirectory WordPress plugin (before 2.8.168) exposes the email addresses of all registered users - including site administrators - to any authenticated Contributor-level or higher user. The root cause is an unrestricted user-search handler that performs no authorization check against WordPress's capability system, meaning any low-privilege authenticated user can invoke it freely. Publicly available exploit code exists per WPScan, though EPSS at 0.14% (4th percentile) and absence from CISA KEV suggest opportunistic exploitation remains limited at time of analysis.
Cost Calculator Builder for WordPress exposes live payment gateway credentials to any authenticated site user through a missing authorization check on its calculator export AJAX endpoint. All plugin versions through 3.6.17 are affected; attackers holding a Subscriber-level WordPress account - the lowest authenticated role - can invoke the `cost-calculator-custom-export-run` AJAX action to receive a full configuration export containing Stripe secret keys, PayPal client secrets, Razorpay secret keys, webhook secret keys, and reCAPTCHA secret keys. No public proof-of-concept exploit or CISA KEV listing has been identified at time of analysis, but the attack requires only a valid site account and basic HTTP knowledge, and an upstream fix has been committed to the plugin's trunk repository.
Out-of-bounds read in OpenSIPS versions prior to 3.6.6 and 4.0.0-rc1 allows unauthenticated remote attackers to trigger memory over-reads in the multipart SIP body parser by sending a crafted message with Content-Type: multipart/mixed whose body contains "--" within two to three bytes of the buffer end. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms network-reachable, zero-prerequisite exploitation with low availability impact, though the reporter's "Information Disclosure" tag conflicts with the official C:N rating, suggesting potential memory leakage beyond what the score reflects. No public exploit or CISA KEV listing has been identified at time of analysis; vendor-released patches are confirmed in 3.6.6 and 4.0.0-rc1.
Epsilla-cloud VectorDB's filter query parser crashes under malformed input due to an improper exception/condition check (CWE-754) in the SplitTokens and ShuntingYard functions of engine/query/expr/expr.cpp. All releases from 0.3.0 through 0.3.18 (including commit df5a5f5afb85a2376a0f2f316c79dea9b2c6ac7a) are affected. A local, low-privileged user who can submit filter expressions to the database engine can trigger an abnormal termination of the parser, causing an availability impact. A public proof-of-concept exploit exists; the vendor did not respond to responsible disclosure.
Baserow's admin impersonation endpoint in versions 2.3.0 through 2.3.2 allows authenticated administrators to obtain authentication tokens for deactivated (inactive, non-staff) users via an improper authorization flaw in `BaserowImpersonateAuthTokenSerializer`. The Baserow maintainer explicitly notes that issued tokens for deactivated accounts are functionally inert because all downstream API endpoints reject them, calling the issue 'more like a bug instead of a vulnerability.' No public exploit code exists, no active exploitation has been observed, and a CVSS 4.0 score of 2.1 reflects the extreme privilege requirement and negligible real-world impact.
Session fixation in Ghost Admin (v2.2.0-v6.54.0) allows an attacker who can plant a known session identifier in a victim's browser - via a secondary vulnerability on the same domain - to hijack an authenticated Ghost Admin session after the victim logs in. The root cause is that Ghost Admin's login flow did not call session regeneration, leaving the pre-login session ID valid post-authentication. Exploitation is chained and non-trivial, but the upstream fix (v6.54.1) is confirmed and straightforward to apply. No public exploit code and no CISA KEV listing identified at time of analysis.
Blind password hash disclosure in Ghost Admin API versions prior to 6.54.1 allows any authenticated staff-level user to retrieve hashed passwords of other staff accounts by crafting filtered API queries against the posts or pages browse endpoints. The root cause is insufficient field-level access control in MongoDB filter queries, exposing internal authentication fields (CWE-200). No active exploitation is confirmed (not in CISA KEV), and downstream account takeover is partially mitigated by Ghost's Device Verification and email MFA features, though the hash disclosure itself is confirmed and unambiguously fixed in 6.54.1.
Ghost CMS subscription checkout accepts redemption of archived offers due to missing offer-status validation in the member router controller, affecting all self-hosted Ghost instances from v4.22.0 through v6.54.0. Unauthenticated users who possess or can discover an archived offer ID can submit a valid checkout request and obtain unauthorized subscription discounts or access at a revoked price point. No public exploit code has been identified and this CVE is absent from CISA KEV, but the direct financial impact on subscription-based Ghost sites makes it a meaningful business-logic risk for affected operators.
Tool source code disclosure in Open WebUI (≤ 0.10.2) allows any authenticated non-admin user who holds a read grant on a shared workspace tool to retrieve the full Python source of that tool via three unguarded API endpoints. The root cause is a Pydantic response-model inheritance defect where the `ToolUserResponse` subclass re-admitted the `content` field that the parent `ToolResponse` schema deliberately excluded, combined with a separate query-level defect in the list path. Because tool source commonly embeds hard-coded API keys, credentials, and internal service URLs, the practical confidentiality loss frequently exceeds the code itself; a detailed proof-of-concept is published in the GitHub security advisory, and the vendor-confirmed fix is available in 0.11.0 with no active exploitation (CISA KEV) recorded at time of analysis.
DNS rebinding bypasses Open WebUI's SSRF protection in all versions prior to 0.11.0, enabling authenticated attackers who control authoritative DNS for a submitted hostname to reach internal resources - including cloud instance metadata services (e.g., 169.254.169.254), loopback admin APIs, and internal network services. The root cause is a TOCTOU race: the hostname is resolved once for validation and again at connection time, letting a TTL=0 DNS record switch from a public IP during the check to an internal IP during the actual fetch. On most vulnerable paths the internal response is returned directly to the attacker; the OAuth path additionally forwards the OAuth access token as a Bearer header to the attacker-controlled internal target, enabling credential theft. No public exploit identified at time of analysis.
Insecure temporary file creation in Lenovo XClarity Essentials OneCLI 5.5.0 and earlier on Linux enables a local low-privileged attacker to overwrite or truncate arbitrary system files via a race condition (CWE-377), but only when a privileged user concurrently executes OneCLI with elevated rights. The attack timing requirement (AT:P in the vendor CVSS 4.0 vector) confirms this is a classic TOCTOU-style symlink race, limiting realistic exploitation to shared multi-user Linux environments where an administrator routinely runs the tool elevated. No public exploit code or CISA KEV listing exists; the vendor has released a patch via advisory LEN-ht116433.
NVIDIA Dynamo for Linux versions 0 through v1.2.0 leaks sensitive information through crafted error message generation, exploitable remotely without authentication. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) confirms low-complexity unauthenticated network access is sufficient to trigger disclosure. No public exploit code has been identified at time of analysis and no CISA KEV listing exists, indicating this is not currently confirmed as actively exploited at scale.
Out-of-bounds read in Systerel S2OPC versions 1.7.0 through 1.7.3 allows a local, low-privileged attacker to disrupt the OPC-UA client process by triggering a memory read violation in the DeleteMonitoredItemsRequest handler state machine function. The flaw is confined to the client-side wrapper component and results in an availability impact rather than code execution or data exfiltration. A public proof-of-concept exploit has been released on GitHub, and the vendor has not responded to coordinated disclosure, leaving no official patch confirmed at time of analysis.
Memory exhaustion in Django's `check_for_language()` function allows denial-of-service via the `set_language` view when it is explicitly enabled in URL configuration. Attackers can submit many distinct, very long language codes via POST requests, causing each code to be cached as an in-memory key and progressively consuming process memory. Django rates this severity 'low' because built-in guards - `DATA_UPLOAD_MAX_MEMORY_SIZE` and the cache's maximum entry count - bound the total exploitable memory; no public exploit identified at time of analysis.
Denial-of-service via recursive GEOMETRYCOLLECTION parsing crashes Django processes through a segmentation fault in the underlying GEOS library. Django's GEOSGeometry class, GeometryField form field, and spatial field lookups in versions 5.2, 6.0, 6.1 (RC), and main are all affected when processing WKT or WKB input containing deeply nested or excessively numerous GEOMETRYCOLLECTION objects. No public exploit code or active exploitation has been identified at time of analysis; the Django team rated this 'moderate' severity and issued fixed releases Django 5.2.17 and 6.0.8 on August 4, 2026.
Information disclosure in Qualcomm Snapdragon chipsets exposes private data transmitted during NG-eCall SIP signaling when IPSec negotiation fails or is improperly established. Attackers adjacent to the network can intercept unprotected signaling traffic, gaining access to sensitive session data - potentially including location coordinates and caller identity transmitted as part of the automated emergency call system. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Information disclosure in Qualcomm Snapdragon wireless subsystem allows an adjacent-network attacker to leak sensitive memory contents by transmitting malformed wireless channel switch frames with invalid length fields. The root cause is CWE-191 (integer underflow), where improperly formatted length values trigger an arithmetic wrap condition during 802.11 management frame parsing, resulting in out-of-bounds memory reads. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, though the low attack complexity and no-authentication requirement on an adjacent wireless segment represent a meaningful real-world risk for shared wireless environments.
Stack-based out-of-bounds read in stunnel's s_vlog logging function allows remote unauthenticated attackers to crash the service by sending protocol inputs that generate log messages exceeding 1024 bytes via vsnprintf. The primary impact is service disruption (availability), with a limited integrity impact in corner cases where trailing newline characters in the stack buffer can be overwritten with null bytes. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Information disclosure in Firefox for Android and Firefox Focus for Android exposes sensitive user data to network-based attackers who can lure a victim into interacting with a crafted web resource. The vulnerability, tracked under CWE-200 and assigned a CVSS score of 6.5 with high confidentiality impact, is limited to Android platform builds and does not affect desktop Firefox. Mozilla patched this in Firefox 153.0.3 per advisory mfsa2026-73; no public exploit or active exploitation has been identified at time of analysis.
Observable response discrepancy in HUMANIST Digital Human Resources 26.0 exposes the system to unauthenticated account footprinting, enabling attackers to enumerate valid user accounts by analyzing differentiated server responses. The vulnerability is classified under CWE-204 and was reported by TR-CERT (Turkish national CERT), affecting the HR platform's authentication or account-lookup endpoints. No active exploitation has been identified in CISA KEV and no public exploit code is known, but the network-accessible, zero-authentication attack surface makes this a viable reconnaissance vector preceding credential-based attacks.
Insufficient session expiration in HUMANIST Digital Human Resources version 26.0 allows an attacker who obtains a valid session token to replay it indefinitely, effectively hijacking an authenticated user's session and gaining unauthorized access to HR data. Reported by TR-CERT (TR-26-0737), the flaw affects all 26.0 builds prior to 26.1 and carries a high confidentiality impact due to the sensitive nature of human resources data processed by the platform. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog.
Resource exhaustion via oversized serialized Lottie animation payloads in Samsung Open Source rlottie allows denial-of-service against any application embedding the library. The library failed to bound precomposition nesting depth, total render-node count, Repeater element copy counts, and did not validate non-finite float values (NaN/Infinity) for polystar and polygon point counts during deserialization and rendering. When a user or application opens a crafted Lottie JSON file, the renderer enters unbounded recursion or allocates excessive memory, crashing or hanging the host application. No public exploit or active exploitation (KEV) has been identified at time of analysis.
Broken object-level authorization in the REST API Log WordPress plugin (all versions before 1.7.1) permits unauthenticated attackers who hold any valid log-download token - regardless of which entry it was issued for - to retrieve arbitrary log entries from any other user, exposing stored credentials, authentication tokens, and private REST API payloads. The root cause is twofold: tokens are not cryptographically bound to specific log entry IDs, and the plugin performs no WordPress capability check on the requester. A public exploit PoC is referenced via WPScan, though EPSS at 0.18% and SSVC exploitation status of 'none' indicate no confirmed widespread abuse at time of analysis.
Uninitialized heap memory disclosure in SSSD's NSS responder exposes cached directory data and heap layout to local authenticated users on RHEL 6 through 10 and OpenShift Container Platform 4. The sss_nss_protocol_fill_initgr() function pre-allocates a reply buffer sized for all group entries but fails to shrink it when groups are skipped, causing uninitialized heap bytes to be included in the response transmitted back to the requesting client. No public exploit code has been identified at time of analysis, and this is not listed in CISA KEV; however, leaked heap addresses may assist in chained attacks targeting ASLR bypass in sssd_nss.
Forced logout via unsigned backchannel requests affects Red Hat Build of Keycloak when an OIDC identity provider is configured to skip signature validation. Under this non-default configuration, the backchannel logout endpoint in keycloak-services improperly accepts logout requests lacking any cryptographic signature (CWE-347), violating the OIDC backchannel logout specification. An unauthenticated network attacker who possesses knowledge of a target user's session identifiers can submit a forged unsigned logout request, terminating that session without the user's consent. No public exploit or active exploitation (CISA KEV) has been identified; with CVSS 3.7 and EPSS data absent from the input, this is a low-priority availability-only issue gated by a specific non-default configuration.
Debug unlock token cross-device reuse in Caliptra Core ROM and Core Firmware (subsystem mode) allows an attacker who already holds access to an integrator's debug unlock signing service to unlock production debug on an unintended device by presenting a token originally issued for a different device sharing the same debug unlock key hash. The 384-bit challenge nonce prevents replay of previously captured tokens but does not bind a token to a specific target device identity, enabling lateral debug access within a shared-key-hash trust group. No public exploit has been identified and the CVSS 4.0 score of 1.8 reflects the narrow real-world impact, which is bounded by the requirement for high-privilege signing-service access and the hard constraint that exploitation cannot cross key-hash group boundaries.
Microsoft Edge (Chromium-based) is affected by a Time-of-Check Time-of-Use (TOCTOU) race condition that allows a remote, unauthenticated attacker to disclose sensitive information over the network, contingent on user interaction. The flaw exploits the timing gap between a security check and subsequent resource use within the Chromium-based browser engine, potentially exposing cross-origin data or internal browser state. No active exploitation has been confirmed by CISA KEV, and the temporal CVSS metrics (E:U) confirm no proven exploit code exists at time of analysis; a vendor patch is available via MSRC.
Wildcard DNS SAN matching in python-cryptography's X.509 chain verifier prior to 49.0.0 allows a leaf certificate bearing *.example.com to satisfy a constrained intermediate CA's permittedSubtrees restriction of foo.example.com, enabling scope escape to sibling domains such as bar.example.com. Applications relying on the PolicyBuilder/Store verification API are exposed to acceptance of invalid certificate chains that should be rejected per RFC 5280 §4.2.1.10. A public proof-of-concept is confirmed in the GHSA advisory; the vulnerability is not in the CISA KEV catalog, but the CVSS 4.0 E:P modifier reflects the POC's availability.
Cookie domain scope bypass in Guzzle PHP HTTP client (prior to 7.15.2 and 8.0.1) allows improper cookie sharing via non-canonical IP address representations in cookie Domain attributes. The flaw in SetCookie::matchesDomain() fails to recognize hexadecimal (e.g., 0x7f000001), mixed-base octal (e.g., 0177.0.0.0x1), and percent-escaped (e.g., 192.168.0.%31) host spellings as IP literals, so cookies set for such domains incorrectly gain subdomain scope while libcurl resolves the same strings as actual IP addresses. This divergence enables an adversary-controlled host (e.g., evil.0x7f000001) to receive session cookies intended for the target IP, facilitating credential disclosure and session fixation; no public exploit identified at time of analysis.
HTTP request smuggling in aiohttp's server-side parser allows unauthenticated remote attackers to inject and misdirect HTTP traffic by exploiting a protocol-switch race in the WebSocket upgrade path. Versions 3.14.1 and earlier prematurely mark the connection as upgraded before the full request body is consumed, causing trailing bytes - potentially an attacker-controlled HTTP request - to be interpreted as WebSocket or pipelined data by the server or any upstream proxy. No public exploit code exists and the vulnerability is not listed in CISA KEV, but CVSS 4.0 AC:H reflects the edge-case nature of the trigger condition.
Man-in-the-middle interception of SSH sessions and file transfers is possible through the EMR SSH helper commands in Amazon AWS CLI v1 before 1.45.28 and v2 before 2.35.3 due to missing entity authentication during the SSH key exchange. Network-positioned attackers - requiring no privileges or user interaction - can substitute their own key material during the handshake and silently relay or inspect the session. No active exploitation is confirmed by CISA KEV, and no public proof-of-concept has been identified at time of analysis; however, the impact on downstream EMR cluster confidentiality is rated high (SC:H in the CVSS 4.0 vector).
Server-side template injection (SSTI) in Dify's Jinja2 Handler (versions ≤1.14.2) allows remote, low-privileged authenticated attackers to inject malicious Jinja2 template expressions through the code execution subsystem, resulting in information disclosure and potential further impact. A public proof-of-concept exploit is available on GitHub, materially lowering the bar for exploitation. The vendor did not respond to responsible disclosure, meaning no patch has been released and no official mitigation guidance exists.
Provisioning data interception in TP-Link Omada's cloud-based device adoption workflow allows a low-privileged network attacker to receive configuration secrets intended for a legitimate device. The vulnerability is a classic race condition (CWE-362): an attacker who can interact with the adoption workflow before a legitimate device completes registration can position themselves to receive the provisioning payload. Affected products span the full Omada ecosystem - controllers, access points, switches, and gateways. No public exploit or CISA KEV listing exists at time of analysis, but the confidentiality impact is rated High by the vendor's own CVSS 4.0 assessment.
Insufficient entropy in session key generation within the TP-Link Omada adoption protocol exposes encrypted controller-to-device communications to decryption by adjacent network attackers. The adoption protocol - the handshake sequence by which Omada Controllers onboard and establish management sessions with gateways, switches, and access points - generates session encryption keys with insufficient randomness, making them potentially recoverable through cryptanalytic means after traffic interception. No confirmed active exploitation (not in CISA KEV) and no public exploit code has been identified at time of analysis; however, the CVSS 4.0 score of 6.9 and the high confidentiality impact on both the vulnerable and subsequent systems indicate meaningful confidentiality risk for organizations relying on Omada-managed network infrastructure.
Hard-coded cryptographic keys in the TP-Link Omada adoption protocol allow adjacent-network attackers to impersonate trusted controllers or managed devices, exposing sensitive authentication material exchanged during device adoption. The flaw affects the entire Omada product line - gateways, switches, access points, and controllers - because all share the same embedded keys, meaning any attacker who extracts the keys from firmware can spoof identity during any adoption event on the same network segment. No public exploit or CISA KEV listing exists at time of analysis, but a vendor patch is available and should be applied promptly given the high confidentiality impact on subsequent systems.
Uncontrolled search path exploitation in CheckMAL AppCheck Pro 3.1.43.10's kernel mini-filter driver (AppCheckD.sys) allows a local attacker with low privileges to redirect the driver's library loading path, potentially achieving kernel-level code execution on the target host. A public proof-of-concept exploit has been released despite the vendor declining to respond to coordinated disclosure, making this a no-patch, public-exploit scenario. While high attack complexity (AC:H) reduces opportunistic risk, the complete confidentiality, integrity, and availability impact at the kernel layer makes successful exploitation highly damaging.
Improper export of the DialerActivity component in textPlus Text Message and Call App (Android, versions up to 8.3.5) allows any co-installed application on the same device to invoke the com.gogii.textplus dialer component without authorization. Classified under CWE-926, this flaw permits a locally-present malicious app to trigger dialer functionality, leading to limited information disclosure and unauthorized interaction with call-related features. No public KEV listing confirms active exploitation, but a proof-of-concept is publicly available on GitHub, lowering the technical barrier for abuse.
GNU tar's --one-top-level extraction mode fails to confine hardlink targets to the designated top-level directory, allowing a crafted archive to plant hardlinks that escape the intended extraction boundary. When combined with a preexisting symbolic link already present under the working directory, an attacker who can induce a victim to extract a malicious archive may read or write files outside the intended extraction scope on systems running affected RHEL versions (6 through 10) and Red Hat Hardened Images. No public exploit has been identified at time of analysis, and exploitation requires both user interaction and a specific environmental pre-condition, keeping real-world risk moderate despite GNU tar's ubiquitous deployment.
HCL iControl v3.2.0 exposes sensitive data in transit by advertising support for deprecated TLS 1.0 and TLS 1.1 protocol versions, which lack modern cryptographic protections. The CVSS vector (AV:N/AC:H/PR:N/UI:N) indicates a network-reachable flaw requiring high attack complexity - consistent with a man-in-the-middle positioning requirement for exploitation. No public exploit code and no CISA KEV listing exist at time of analysis, placing this in the medium-priority tier despite its network exposure, though organizations with regulatory requirements around cryptographic standards (PCI-DSS, NIST SP 800-52) should treat remediation as mandatory.
Out-of-bounds read in SSSD's NSS responder allows a local user with standard privileges to crash the SSSD process by sending a crafted GETHOSTBYADDR request, causing system-wide denial of authentication and name resolution services. The vulnerable function `sss_nss_protocol_parse_addr()` fails to validate the `addrlen` field against the actual remaining packet body size, enabling heap over-read and process termination. No public exploit code or active exploitation has been identified at time of analysis, and this vulnerability is not listed in CISA KEV.
Sharp Corporation's Network Scanner Tool and Network Scanner Tool Lite expose unauthenticated, unlimited file upload endpoints by default, enabling two distinct attack outcomes against any PC running the software in its initial configuration. An unauthenticated network attacker can flood the host with uploaded files to exhaust disk or system resources, causing a denial-of-service condition; separately, a threat actor can stage malicious executables that a local PC user may be socially engineered into running, enabling downstream attacks against other systems. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, though the default-insecure nature and zero authentication requirement lower the barrier to exploitation significantly.
Unauthenticated network access to address book editing and Document Filing features is possible on Sharp and Toshiba Tec multifunction printers (MFPs) sold outside Japan, because these devices ship from the factory with user authentication disabled. The root cause is CWE-1188 (Insecure Default Initialization of Resource) - the authentication control exists but is not activated in the initial configuration, meaning any network-reachable attacker can access sensitive stored data and modify contact directories without credentials. No public exploit code and no CISA KEV listing exist at time of analysis, but the CVSS vector confirms network-level unauthenticated access with no interaction required.
Incomplete cleanup of cached print job data in Sharp and Toshiba Tec multifunction printers exposes previously printed documents to subsequent physical users of the same device. Affecting all versions per CPE data (cpe:2.3:a:sharp_corporation:sharp_mfps and cpe:2.3:a:toshiba_tec_corporation:toshiba_tec_mfps), the flaw (CWE-459) means internal caches are not wiped after a print job completes, allowing the next person who physically accesses the device to potentially retrieve another user's data. No public exploit code exists and the vulnerability has not been added to CISA KEV, consistent with the low CVSS score of 2.4 and a physical-access attack vector.
Unauthenticated network access to stored image data affects Sharp and Toshiba Tec multifunction printers via a forced browsing vulnerability (CWE-425). Remote attackers without any credentials can directly request URLs referencing scanned or copied image data held on the device, bypassing the authorization layer entirely. Reported by JPCERT, this is an information disclosure issue with no public exploit identified at time of analysis and no confirmed active exploitation.
Sandbox escape in vxcontrol PentAGI up to 2.1.0 exposes a privilege boundary weakness in the Tool Management Protocol Handler, rooted in the pentester prompt template file. Remote unauthenticated attackers who can craft sufficiently complex inputs may bypass sandbox constraints on the AI agent's tool execution context, achieving limited confidentiality, integrity, and availability impact against the vulnerable system. A public proof-of-concept exists on GitHub; no patch has been released and the vendor has not responded to disclosure - leaving all deployments on versions up to 2.1.0 without a vendor-sanctioned fix.
Cleartext storage of personally identifiable information in Meesho Online Shopping App (Android, versions through 20260607) exposes user_id, phone number, email address, and name in the com.meesho.supply component without encryption. Exploitation requires physical access to the device and a degree of local privilege, making this a low-severity, localized threat rather than a remote or mass-exploitation risk. A proof-of-concept is publicly available via GitHub and Google Drive, though no active exploitation has been confirmed by CISA KEV.
NLTK's downloader in version 3.9.4 installs attacker-controlled package bytes by writing and potentially extracting downloaded content before enforcing SHA-256 or MD5 checksum validation. Any user or CI pipeline invoking `nltk.download()` against a compromised mirror, rogue proxy, or network-level MITM is at risk of silently installing malicious corpora or model files. No public exploit identified at time of analysis; active exploitation not confirmed (no CISA KEV listing). The AC:H CVSS metric correctly reflects the non-trivial infrastructure access an attacker must achieve, but the downstream trust propagation - NLP applications consuming poisoned models - amplifies the realistic impact beyond the base score.
Username enumeration is possible in PaperCut NG/MF via an observable timing side-channel in the authentication component, exploitable by unauthenticated remote attackers. The system conditionally executes password hash comparison only when a submitted username corresponds to a valid account, producing a measurable latency difference that reveals account existence. No public exploit code or CISA KEV listing has been identified at time of analysis; however, with a CVSS 4.0 score of 6.9 and an AV:N/PR:N vector, the attack surface is entirely remote and requires no credentials, making it accessible to any attacker with network reach to the login endpoint.
PaperCut NG/MF's login component fails to enforce account lockout or rate-limiting controls in certain configurations, allowing unauthenticated remote attackers to conduct unrestricted brute-force or credential-stuffing attacks against user accounts. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required, though the 'in some configurations' qualifier in the CVE description indicates exploitation is conditional on the absence of hardening controls. PaperCut published a security bulletin on August 3, 2026; no public exploit code or CISA KEV listing has been identified at time of analysis.
Out-of-bounds read in mz-automation libiec61850 up to version 1.6.1 allows remote unauthenticated attackers to crash the IEC 61850 MMS server process and potentially leak heap or stack memory contents by sending a crafted MMS DataSet access request. The root cause is unconstrained string copy operations in the checkDataSetAccess function, now confirmed fixed in v1.6.2 via bounded copy with a 129-byte limit. A public exploit has been disclosed; however, this vulnerability is not listed in CISA KEV and the CVSS 4.0 score of 6.9 (Medium) reflects limited impact scope confined to availability of the vulnerable system.
Out-of-bounds read in MediaTek's GeniZone trusted execution environment (TEE) exposes memory on 17 affected chipset models to local information disclosure, but only after an attacker has already acquired System-level privilege. The vulnerability stems from a missing bounds check in the geniezone driver (CWE-125, Patch ID ALPS11036877), and is tracked by MediaTek as MSV-7132. No public exploit code exists and CISA has not listed this in KEV; with an EPSS of 0.14% (4th percentile) and SSVC exploitation status of 'none', this is a low-urgency finding despite the breadth of affected silicon.
Out-of-bounds read in the MediaTek Wi-Fi driver component on MT6988, MT6990, and MT6890 chipsets permits local information disclosure against devices where an attacker has already obtained System-level privilege. The missing bounds check in the Wi-Fi stack allows reading memory beyond the intended buffer boundary, exposing potentially sensitive kernel or driver memory contents. No public exploit exists and EPSS at 0.13% (3rd percentile) reflects the significant privilege prerequisite that constrains real-world exploitation; CISA KEV does not list this vulnerability.
Out-of-bounds read in MediaTek's ccci (Cross Core Communication Interface) driver on multiple chipsets enables local denial of service by a System-privileged attacker. Affected chipsets include MT6813, MT6988, MT6982VB, MT6986D, and MT6986 - targeting mid-range and flagship Android SoC lines. No public exploit code exists and CISA has not added this to KEV; real-world impact is constrained by the high privilege prerequisite, making this a post-compromise availability risk rather than an initial access vector.
Local information disclosure in the display subsystem of multiple MediaTek SoC chipsets results from a CWE-125 out-of-bounds read triggered by an integer overflow. Seventeen distinct chipsets are confirmed affected per the EUVD listing, spanning devices such as MT8910, MT8188, MT8768, and MT6991 - all prevalent in mid-range and budget Android hardware. Exploitation requires an attacker who has already attained System-level privilege on the device; no public exploit exists and EPSS sits at 0.14% (4th percentile), consistent with the SSVC exploitation rating of 'none'.
Local information disclosure in MediaTek's display subsystem exposes arbitrary kernel memory to a privileged local process due to a missing bounds check (CWE-125). Exploitation is limited to actors who have already obtained System-level privileges on a device running one of 17 affected MediaTek chipsets (MT6991, MT8676, MT8799, and others). No public exploit code and no active exploitation have been identified; EPSS sits at 0.14% (4th percentile), consistent with SSVC's 'none' exploitation status and 'no automatable' classification.
Information disclosure in the TFA (Trusted Firmware-A) component of MediaTek chipsets allows a local attacker who has already obtained System-level privilege to retrieve sensitive secure-world data without user interaction, due to a missing permission check (CWE-201). The flaw spans 39 distinct MediaTek chipsets across the MT6xxx and MT8xxx families, covering a broad range of Android smartphones, tablets, and embedded devices. No public exploit code or active exploitation has been identified; EPSS stands at 0.14% (4th percentile), consistent with the high privilege prerequisite limiting real-world impact.
Local information disclosure in the Telephony component across 42 MediaTek chipsets enables any unprivileged application on the device to extract sensitive telephony data without elevated permissions. The root cause is a missing Android permission check (CWE-926: Improper Export of Android Application Components), allowing improperly exported Telephony interfaces to be queried by any installed app. No active exploitation is confirmed - EPSS sits at 0.15% (5th percentile) and the vulnerability is absent from CISA KEV - but the breadth of affected chipsets spanning budget through flagship tiers gives this issue significant deployment reach. Patch ALPS11086431 is available per MediaTek's August 2026 security bulletin.
Remote unauthenticated crash in mz-automation libiec61850 1.6.0-1.6.1 allows a network attacker to terminate an IEC 61850 MMS server by supplying an oversized Report ID string to the Report Control Block write handler, triggering a free of non-heap memory (CWE-590). No authentication or user interaction is required per the CVSS 4.0 vector (PR:N/UI:N/AV:N), and a public proof-of-concept exploit exists at the referenced GitHub issue. Active exploitation has not been confirmed by CISA KEV, but the combination of a public PoC and trivial exploitation path elevates practical risk in operational technology environments where IEC 61850 server continuity is safety-critical.
PSA Crypto key slot exhaustion in Zephyr's Bluetooth Mesh subnet.c permanently leaks one key slot on every subnet key teardown when CONFIG_BT_MESH_PRIV_BEACONS is enabled (the default). Devices running Zephyr 3.6.0 through 4.4.x are affected: a provisioner or network administrator with the node's device key can trigger the leak via Config Server NetKey Delete, Key Refresh Procedure, or reprovisioning over the Bluetooth Mesh network. With the default pool of 16 PSA key slots, roughly a dozen such operations exhaust the pool, preventing subnet creation and potentially starving other on-device PSA consumers until a reboot. No public exploit or CISA KEV listing exists; real-world impact is constrained by the high-privilege and proximity requirements.
PHP object injection in the Event Booking Manager for WooCommerce WordPress plugin (all versions before 5.3.7) allows authenticated contributors to deserialize attacker-controlled PHP objects through event content fields. Exploitation to achieve remote code execution, arbitrary file deletion, or sensitive data retrieval depends entirely on the presence of a usable POP (Property-Oriented Programming) chain from a co-installed plugin or theme - none exists within this plugin itself. A publicly available exploit exists per WPScan (EUVD-2026-51948), and this CVE represents an incomplete remediation of prior object-injection advisories affecting the same plugin.
Local HDF5 file content disclosure in keras-team/keras versions 3.14.0 and earlier allows an attacker who can deliver a malicious model file to exfiltrate arbitrary local filesystem data from a victim's machine. Both the `KerasFileEditor` class and `keras.saving.load_weights` function fail to invoke the `safe_get_h5_group` and `safe_get_h5_dataset` helpers before traversing HDF5 group children, causing automatic dereferencing of embedded ExternalLinks and SoftLinks that point to attacker-controlled paths on the victim's filesystem. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the attack mechanism is straightforward and the commit diff makes the vulnerability trivially reproducible.
Read-side prototype pollution gadgets in axios allow a secondary attacker primitive to corrupt HTTP request semantics when Object.prototype has already been polluted by a separate, pre-existing vulnerability in the same application. Affected are the bodyless method aliases - axios.get(), axios.delete(), axios.head(), and axios.options() - across all 1.x releases below 1.18.0 and all 0.x releases below 0.33.0. An attacker who controls Object.prototype pollution can inject a fabricated request body into what the application intends as a bodyless request, or, via lower-level adapter paths, route requests through an attacker-controlled proxy or invoke custom URL serialization logic. No public exploit identified at time of analysis and no CISA KEV listing, but the CVSS 4.0 AT:P metric explicitly models the required precondition attack.
Stale session persistence in better-auth allows deleted users to maintain authenticated access for up to seven days after account removal. Affected are deployments of better-auth versions 0.3.4 through 1.6.10 running with secondaryStorage (Redis, KV, or similar external cache) and the default storeSessionInDatabase=false setting, where user deletion flows through the admin, anonymous, or SCIM plugins. Because deleteSessions is never called before deleteUser in these code paths, the session payload remains live in the cache until TTL expiry, meaning a terminated employee or compromised account that has been administratively deleted can continue making authenticated requests. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Out-of-bounds heap read in FreeRDP's UVC H.264 extension-unit parser affects all versions prior to 3.29.0, allowing an attacker with physical USB access to trigger denial of service during camera stream setup. The parser fails to validate descriptor length before accessing the GUID field, enabling a read beyond allocated heap bounds when a malicious USB video camera is connected. No public exploit has been identified, KEV listing is absent, and the CVSS 4.0 score of 2.4 accurately reflects the constrained physical-access attack surface.
Divide-by-zero in FreeRDP's rdpecam camera redirection channel allows a malicious or compromised RDP server to crash the connecting client process by sending a StartStreamsRequest PDU with FrameRateDenominator set to zero. All FreeRDP releases up to and including 3.28.0 are affected when camera redirection is enabled; exploitation delivers a reliable client-side denial-of-service (SIGFPE termination) with no code execution potential. No public exploit or CISA KEV listing exists at time of analysis; this is a medium-severity availability issue patched in FreeRDP 3.29.0.
Out-of-bounds read in FreeRDP 3.28.0 and earlier allows a malicious or compromised RDP server to leak client-side memory contents or crash the FreeRDP process by sending a crafted truncated planar-encoded bitmap or surface update. The flaw lives in the RDP6 planar RLE decoder (libfreerdp/codec/planar.c), where attacker-declared raw byte counts of 0-15 bytes following a bounds-checked control byte are consumed without verifying remaining buffer space. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; FreeRDP 3.29.0 contains the confirmed vendor patch.
Proxy-Authorization header leakage in guzzlehttp/guzzle before 7.14.2 allows origin servers to receive proxy credentials due to a cURL handler misclassification bug. When requests are routed via SOCKS proxies, match no_proxy bypass rules, connect directly with proxying disabled, or cross proxy boundaries during redirects, Guzzle fails to migrate the Proxy-Authorization header from cURL's origin header list to the proxy-only channel - the credential arrives at the origin server instead of being confined to the proxy hop. An attacker who controls or monitors a destination origin server can harvest these credentials from access logs, then abuse the proxy to impersonate the proxy principal or reach destinations gated behind that proxy. No public exploit code has been identified at time of analysis.
Session revocation via forged cookies in better-auth's multi-session plugin (npm, versions 1.3.34 through <1.4.0) allows any authenticated attacker to arbitrarily delete session tokens belonging to other users by supplying a crafted `_multi-*` cookie to the /sign-out after-hook, which forwards cookie values to `internalAdapter.deleteSessions()` without verifying the cryptographic signature. The flaw is not listed in the CISA KEV catalog and no public exploit code has been identified, but the low attack complexity makes unauthorized targeted session termination straightforward once an attacker holds any valid application session. Version 1.4.0 resolves the issue via patch commit cfc453a2a6eb02951f9a0a7c944064936e73eee8.
Out-of-bounds read in Zephyr RTOS DHCPv4 client (versions 1.7.0 through 4.4.x) allows an adjacent-network attacker to crash the DHCP client or leak adjacent pointer contents by sending a crafted DHCP reply with a message-type value greater than 8. The defect is a classic sizeof-vs-ARRAY_SIZE confusion: the bounds guard compares a raw msg_type byte against the byte-size of a pointer array (32 or 64, depending on architecture) rather than its element count of 8, so values 9-31/63 bypass the check and cause a wild-pointer dereference inside a debug log call. Exploitation is gated on a non-default build configuration (CONFIG_NET_DHCPV4_LOG_LEVEL_DBG), substantially reducing the real-world attack surface. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Bluetooth GATT notification and indication paths in Zephyr RTOS 2.6.0 through 4.4.x skip the application-configured encryption, authentication, and LESC security requirements for characteristic values when the application follows the documented idiom of passing the Characteristic Declaration attribute to the notify/indicate APIs. A remote Bluetooth peer within radio range can connect without pairing and trigger the server to emit protected characteristic values over an unsecured link by writing the Client Characteristic Configuration descriptor, achieving an access-control bypass and information disclosure. No public exploit is identified at time of analysis; exploitation requires adjacent network access and specific application configuration.
Unauthenticated sensitive information disclosure in the WooCommerce PayPal Payments WordPress plugin (all versions through 3.3.2) allows remote attackers to harvest full customer billing PII from recently placed orders. The vulnerability is a two-stage IDOR chain: the `enqueue_paypal_insights_script_on_order_received()` function exposes order keys without validating the caller's identity, and those keys can then be replayed against the WooCommerce Store API - which grants a 10-minute post-order grace period - to retrieve names, email addresses, phone numbers, and street addresses. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the network-reachable, zero-authentication attack path and PII sensitivity elevate practical risk above the CVSS 5.3 numeric score.
Sensitive information exposure in the Advanced Views WordPress plugin (wplakeorg, all versions ≤ 3.9.1) allows any authenticated subscriber-level user to harvest admin-authored editor content - including template markup, CSS, JavaScript, and PHP controller variables - via improperly authorized REST API routes. Wordfence identified the flaw across three CPT interactive field classes (base, Layout, and Post Selection). No public exploit code or CISA KEV listing exists at time of analysis, but the low authentication bar of subscriber-level access makes this trivially exploitable on any WordPress site with open user registration.
Sensitive WooCommerce order data exposure in the PixelYourSite WordPress plugin (all versions through 11.2.1) allows unauthenticated remote attackers to retrieve full purchase metadata - product names, quantities, per-item prices, order totals, currency, and transaction IDs - for any order by supplying an arbitrary or invalid order key alongside a known order ID. The plugin's getWooPurchaseEventParams function resolves orders solely from the URL path order ID without validating the accompanying key, then emits the complete woo_purchase tracking payload directly into rendered page HTML via the pysOptions JavaScript object across all three supported integrations (Facebook Pixel, Google Analytics, and Google Tag Manager). No public exploit has been identified at time of analysis, but because WooCommerce order IDs are sequential integers by default, mass enumeration of the entire order history requires only a trivial HTTP loop.
Local file inclusion in the GetPaid WordPress plugin (versions ≤ 2.8.56) enables authenticated administrators to include and execute arbitrary PHP files on the server by supplying a crafted element type value to the getpaid_payment_form_element function. The root cause (CWE-98) is twofold: the element type string was used unsanitized to construct a PHP template file path, and the bare extract($element) call without EXTR_SKIP allowed attacker-controlled array keys to overwrite internal variables including the path already resolved. No public exploit code or active exploitation (CISA KEV listing) has been identified at time of analysis; real-world risk is substantially constrained by the administrator-level access and PHP file upload prerequisites.
Case-insensitivity handling inconsistency in Jenkins 2.575 and earlier allows attackers to impersonate existing users or inherit their permissions by registering accounts with Unicode characters that case-insensitively match existing usernames. Jenkins generates canonical user IDs via lowercasing but performs comparisons using Java's `String#equalsIgnoreCase`, which follows Unicode case-folding semantics - for example, the Turkish dotless 'ı' is treated as equal to 'i' during comparison but produces a different canonical ID when lowercased. Exploitation is constrained to deployments using external security realms that permit non-ASCII characters in usernames; no public exploit has been identified at time of analysis.
Arbitrary file write via crafted tar archive extraction in Jenkins 2.575 and earlier allows attackers controlling agent processes to escape extraction directory boundaries on the controller filesystem, directly enabling remote code execution. The root cause is unsafe handling of symbolic links with effectively empty names during .tar and .tar.gz extraction on the controller, permitting writes to sensitive paths such as JENKINS_HOME/init.groovy.d/ (Groovy init scripts) or JENKINS_HOME/plugins/ (plugin deployment). No public exploit or CISA KEV listing has been identified at time of analysis, but the agent-to-controller trust boundary is a well-established Jenkins attack surface with a history of critical exploitation.
Statamic CMS exposes authenticated users' raw two-factor authentication recovery codes through the Antlers templating engine due to a missing access restriction in the `AugmentedUser::get()` resolver. Unlike `password` and `password_hash` fields, which are explicitly excluded from augmentation, `two_factor_recovery_codes` is returned without restriction and is absent from all Antlers variable guard lists. An administrator or developer who has configured a blueprint field with dynamic Antlers rendering enabled can craft a template (`{{ current_user.two_factor_recovery_codes }}`) that, when rendered by a victim visiting the page, leaks that victim's 2FA recovery codes into the HTML response - enabling 2FA bypass. No public exploit has been identified at time of analysis, and exploitation requires a high-privilege prerequisite (blueprint configuration access).
ESPHome's built-in web server unconditionally leaks plaintext passwords stored in password-mode text entities to any unauthenticated attacker on the local network. The web_server component on port 80 - which carries no authentication by default - serializes text entities with a dual-field JSON structure where the 'state' field is correctly redacted to '********' but the 'value' field is always populated with the raw secret via set_json_icon_state_value()/set_json_value(), exposing WiFi credentials, API tokens, and similar secrets through a trivial GET request or the /events EventSource stream. No public exploit code or CISA KEV listing has been identified at time of analysis, but exploitation requires only standard HTTP tooling against any reachable device with the web_server component enabled.
IV reuse in libkcapi's one-shot symmetric cipher operations allows a remote attacker to weaken data confidentiality for applications processing inputs larger than 64 KiB under stateful modes (CTR or CBC). Affected deployments include Red Hat Enterprise Linux 8, 9, and 10, Red Hat Hardened Images, and OpenShift Container Platform 4. No public exploit or active exploitation has been identified; the AV:N vector reflects an indirect attack path where an adversary induces a vulnerable application to process specially crafted oversized inputs, enabling ciphertext analysis to expose plaintext relationships or recover data.
Host header injection in SonicWall SonicOS enables remote unauthenticated attackers to manipulate the HTTP Host header on the firewall management interface, causing redirect responses that send management users to attacker-controlled web domains. Affected version branches span the SonicOS 6.5, 7.0, 7.3, and 8.2 lines, covering a wide installed base of SonicWall firewalls. No public exploit code exists and this vulnerability has not been added to CISA KEV at time of analysis, but the unauthenticated network-accessible attack surface and management-user targeting make it a meaningful phishing risk in environments where the management interface is internet-exposed.
AES-GCM nonce exhaustion in Kong Event Gateway 1.0.0-1.1.1 and 1.2.0 allows an authorized consumer to recover partial message plaintext when the AWS IAM encryption feature is enabled and key rotation has not occurred. Because keys are only rotated on gateway reboot, a producer sustaining a high message rate can exhaust the NIST SP 800-38D-recommended random nonce limit (~2^32 encryptions), making nonce collisions statistically likely and enabling ciphertext XOR attacks. No public exploit exists and the vulnerability is not in CISA KEV; the CVSS 4.0 score of 2.3 reflects the narrow, condition-heavy exploitation path.
Prototype pollution in Eclipse Theia's preference resolution system exposes developers to application-logic manipulation when opening crafted workspaces. The `PreferenceUtils.merge` function in `@theia/core`, invoked for every preference scope resolution, fails to reject reserved JavaScript prototype keys (`__proto__`, `constructor`, `prototype`), allowing a malicious `.theia/settings.json` or `.vscode/settings.json` to corrupt `Object.prototype` across the entire Theia Node.js process. Affected versions span 0.7.0 through 1.73.1 inclusive; no public exploit has been identified at time of analysis, and the CVSS 4.0 score of 5.7 appropriately reflects the social-engineering dependency and required user interaction.
SQL injection in the ZTE Smart Life mobile app enables a local attacker with physical device access to execute UNION SELECT statements against the app's feedback.db SQLite database, extracting sensitive personal data including user account details, phone numbers, feedback content, and local debug log paths. Exploitation is severely constrained by the CVSS:3.1/AV:P/AC:H/PR:L/UI:R vector, requiring physical access to the device, a low-privilege authenticated session within the app, user interaction, and non-trivial attack complexity. No public exploit code or CISA KEV listing has been identified at time of analysis, and the vendor (ZTE PSIRT) has published a bulletin acknowledging the issue.
In the Linux kernel, the following vulnerability has been resolved: ipv4: fib: free fib_alias with kfree_rcu() on insert error path fib_table_insert() publishes new_fa into the leaf's fa_list with fib_insert_alias() before calling the fib entry notifiers. When a notifier fails, the error path removes new_fa with fib_remove_alias() (hlist_del_rcu) and frees it right away with kmem_cache_free(). fib_table_lookup() walks that list under rcu_read_lock() only, so a concurrent lookup that already reached new_fa keeps reading it after the free: BUG: KASAN: slab-use-after-free in fib_table_lookup (net/ipv4/fib_trie.c:1601) Read of size 1 at addr ffff88810676d4eb by task exploit/297 Call Trace: fib_table_lookup (net/ipv4/fib_trie.c:1601) ip_route_output_key_hash_rcu (net/ipv4/route.c:2814) ip_route_output_key_hash (net/ipv4/route.c:2705) __ip4_datagram_connect (net/ipv4/datagram.c:49) udp_connect (net/ipv4/udp.c:2144) __sys_connect (net/socket.c:2167) __x64_sys_connect (net/socket.c:2173) do_syscall_64 entry_SYSCALL_64_after_hwframe which belongs to the cache ip_fib_alias of size 56 Triggering the error path needs CAP_NET_ADMIN and a registered fib notifier that can reject a route; a netdevsim device whose IPv4 FIB resource is exhausted is enough. Free new_fa with alias_free_mem_rcu(), as fib_table_delete() already does for a fib_alias removed from the trie.
In the Linux kernel, the following vulnerability has been resolved: wifi: p54: validate RX frame length in p54_rx_eeprom_readback() p54_rx_eeprom_readback() copies the requested EEPROM slice out of a device-supplied readback frame without checking that the skb actually holds that many bytes. Commit da1b9a55ff11 ("wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()") closed the destination overflow by copying a fixed priv->eeprom_slice_size (and rejecting a mismatched advertised len), but the source side is still unbounded: nothing verifies the frame is long enough to supply that many bytes. A malicious USB device can send a short frame whose advertised len matches priv->eeprom_slice_size while the payload is truncated. The equality check passes and memcpy() reads past the end of the skb, leaking adjacent heap: BUG: KASAN: slab-out-of-bounds in p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) Read of size 1016 at addr ffff88800f077114 by task swapper/0/0 Call Trace: <IRQ> ... __asan_memcpy (mm/kasan/shadow.c:105) p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) p54u_rx_cb (drivers/net/wireless/intersil/p54/p54usb.c:163) __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657) dummy_timer (drivers/usb/gadget/udc/dummy_hcd.c:2005) ... </IRQ> The buggy address belongs to the object at ffff88800f0770c0 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 84 bytes inside of allocated 704-byte region [ffff88800f0770c0, ffff88800f077380) Check that the slice fits in the skb before copying.
In the Linux kernel, the following vulnerability has been resolved: mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n On CONFIG_INET=n builds, mpls_valid_fib_dump_req() walks the parsed attribute table itself instead of calling ip_valid_fib_dump_req(). The RTA_OIF arm passes tb[RTA_OIF] to nla_get_u32() without checking it is present, so an RTM_GETROUTE dump for AF_MPLS with strict checking and no RTA_OIF hits a NULL dereference. RTM_GETROUTE is RTNL_KIND_GET, which rtnetlink_rcv_msg() permits without CAP_NET_ADMIN, so an unprivileged user can trigger it. Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:mpls_valid_fib_dump_req (net/mpls/af_mpls.c:2189) Call Trace: mpls_dump_routes (net/mpls/af_mpls.c:2236) netlink_dump (net/netlink/af_netlink.c:2331) __netlink_dump_start (net/netlink/af_netlink.c:2446) rtnetlink_rcv_msg (net/core/rtnetlink.c:7033) netlink_rcv_skb (net/netlink/af_netlink.c:2556) netlink_unicast (net/netlink/af_netlink.c:1345) netlink_sendmsg (net/netlink/af_netlink.c:1900) __sock_sendmsg (net/socket.c:790) ____sys_sendmsg (net/socket.c:2684) ___sys_sendmsg (net/socket.c:2738) __sys_sendmsg (net/socket.c:2770) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) Skip unset attributes, as ip_valid_fib_dump_req() does.
Cluster ID enumeration in SUSE Rancher exposes a reliable oracle via the unauthenticated `/v3/import/{token}_{clusterId}.yaml` endpoint, which performs cluster object retrieval before token validation. Remote unauthenticated attackers can distinguish valid cluster IDs (HTTP 502, triggered by a nil pointer dereference in `pkg/systemtemplate/private_registry.go` when private registry secrets exist) from non-existent ones (HTTP 200), leaking the presence and private-registry configuration status of clusters. This is not listed in CISA KEV and no public exploit code has been identified, but the zero-prerequisite network accessibility makes enumeration trivially scriptable.
Unrestricted brute-force against changedetection.io's /login endpoint allows a remote unauthenticated attacker to systematically guess the single shared application password with no throttling, lockout, or attempt counter to impede automated attacks. Because the entire application is protected by one shared credential with no per-user account model, a successful guess grants full administrative control - including the ability to view and regenerate the API token and access all monitored URL configurations. No public exploit code or CISA KEV listing has been identified at time of analysis, but the attack is trivially automatable given the network-accessible endpoint, low complexity (CVSS AC:L), and complete absence of brute-force controls confirmed by requirements.txt inspection.
Unauthorized information disclosure in the MLSImport: IDX Plugin & MLS Plugin for Real Estate Listings WordPress plugin (all versions before 7.0.4) exposes import log files and import-related post metadata to any authenticated user, including low-privilege subscribers. The flaw stems from a missing authorization and CSRF check on an AJAX action, meaning any logged-in WordPress user on an affected site can invoke the endpoint and read sensitive operational data. A publicly available proof-of-concept exists (reported by WPScan), though EPSS places exploitation probability at 0.10% and SSVC confirms no known active exploitation at time of analysis.
Unauthenticated information disclosure in DHL Shipping Germany for WooCommerce (versions before 4.0.1) exposes stored shipping labels - each containing customer name and postal address - to any visitor who can request predictable filenames from the label storage directory. The plugin relies exclusively on an Apache .htaccess file for directory access control, which nginx and other non-Apache web servers silently ignore, leaving the directory fully browsable over the network. A publicly available exploit exists (via WPScan), though EPSS of 0.14% at the 4th percentile indicates low observed exploitation activity, and the vulnerability is not listed in the CISA KEV catalog.
Information disclosure in the GeoDirectory WordPress plugin (before 2.8.168) exposes the email addresses of all registered users - including site administrators - to any authenticated Contributor-level or higher user. The root cause is an unrestricted user-search handler that performs no authorization check against WordPress's capability system, meaning any low-privilege authenticated user can invoke it freely. Publicly available exploit code exists per WPScan, though EPSS at 0.14% (4th percentile) and absence from CISA KEV suggest opportunistic exploitation remains limited at time of analysis.
Cost Calculator Builder for WordPress exposes live payment gateway credentials to any authenticated site user through a missing authorization check on its calculator export AJAX endpoint. All plugin versions through 3.6.17 are affected; attackers holding a Subscriber-level WordPress account - the lowest authenticated role - can invoke the `cost-calculator-custom-export-run` AJAX action to receive a full configuration export containing Stripe secret keys, PayPal client secrets, Razorpay secret keys, webhook secret keys, and reCAPTCHA secret keys. No public proof-of-concept exploit or CISA KEV listing has been identified at time of analysis, but the attack requires only a valid site account and basic HTTP knowledge, and an upstream fix has been committed to the plugin's trunk repository.
Out-of-bounds read in OpenSIPS versions prior to 3.6.6 and 4.0.0-rc1 allows unauthenticated remote attackers to trigger memory over-reads in the multipart SIP body parser by sending a crafted message with Content-Type: multipart/mixed whose body contains "--" within two to three bytes of the buffer end. The CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms network-reachable, zero-prerequisite exploitation with low availability impact, though the reporter's "Information Disclosure" tag conflicts with the official C:N rating, suggesting potential memory leakage beyond what the score reflects. No public exploit or CISA KEV listing has been identified at time of analysis; vendor-released patches are confirmed in 3.6.6 and 4.0.0-rc1.
Epsilla-cloud VectorDB's filter query parser crashes under malformed input due to an improper exception/condition check (CWE-754) in the SplitTokens and ShuntingYard functions of engine/query/expr/expr.cpp. All releases from 0.3.0 through 0.3.18 (including commit df5a5f5afb85a2376a0f2f316c79dea9b2c6ac7a) are affected. A local, low-privileged user who can submit filter expressions to the database engine can trigger an abnormal termination of the parser, causing an availability impact. A public proof-of-concept exploit exists; the vendor did not respond to responsible disclosure.
Baserow's admin impersonation endpoint in versions 2.3.0 through 2.3.2 allows authenticated administrators to obtain authentication tokens for deactivated (inactive, non-staff) users via an improper authorization flaw in `BaserowImpersonateAuthTokenSerializer`. The Baserow maintainer explicitly notes that issued tokens for deactivated accounts are functionally inert because all downstream API endpoints reject them, calling the issue 'more like a bug instead of a vulnerability.' No public exploit code exists, no active exploitation has been observed, and a CVSS 4.0 score of 2.1 reflects the extreme privilege requirement and negligible real-world impact.
Session fixation in Ghost Admin (v2.2.0-v6.54.0) allows an attacker who can plant a known session identifier in a victim's browser - via a secondary vulnerability on the same domain - to hijack an authenticated Ghost Admin session after the victim logs in. The root cause is that Ghost Admin's login flow did not call session regeneration, leaving the pre-login session ID valid post-authentication. Exploitation is chained and non-trivial, but the upstream fix (v6.54.1) is confirmed and straightforward to apply. No public exploit code and no CISA KEV listing identified at time of analysis.
Blind password hash disclosure in Ghost Admin API versions prior to 6.54.1 allows any authenticated staff-level user to retrieve hashed passwords of other staff accounts by crafting filtered API queries against the posts or pages browse endpoints. The root cause is insufficient field-level access control in MongoDB filter queries, exposing internal authentication fields (CWE-200). No active exploitation is confirmed (not in CISA KEV), and downstream account takeover is partially mitigated by Ghost's Device Verification and email MFA features, though the hash disclosure itself is confirmed and unambiguously fixed in 6.54.1.
Ghost CMS subscription checkout accepts redemption of archived offers due to missing offer-status validation in the member router controller, affecting all self-hosted Ghost instances from v4.22.0 through v6.54.0. Unauthenticated users who possess or can discover an archived offer ID can submit a valid checkout request and obtain unauthorized subscription discounts or access at a revoked price point. No public exploit code has been identified and this CVE is absent from CISA KEV, but the direct financial impact on subscription-based Ghost sites makes it a meaningful business-logic risk for affected operators.
Tool source code disclosure in Open WebUI (≤ 0.10.2) allows any authenticated non-admin user who holds a read grant on a shared workspace tool to retrieve the full Python source of that tool via three unguarded API endpoints. The root cause is a Pydantic response-model inheritance defect where the `ToolUserResponse` subclass re-admitted the `content` field that the parent `ToolResponse` schema deliberately excluded, combined with a separate query-level defect in the list path. Because tool source commonly embeds hard-coded API keys, credentials, and internal service URLs, the practical confidentiality loss frequently exceeds the code itself; a detailed proof-of-concept is published in the GitHub security advisory, and the vendor-confirmed fix is available in 0.11.0 with no active exploitation (CISA KEV) recorded at time of analysis.
DNS rebinding bypasses Open WebUI's SSRF protection in all versions prior to 0.11.0, enabling authenticated attackers who control authoritative DNS for a submitted hostname to reach internal resources - including cloud instance metadata services (e.g., 169.254.169.254), loopback admin APIs, and internal network services. The root cause is a TOCTOU race: the hostname is resolved once for validation and again at connection time, letting a TTL=0 DNS record switch from a public IP during the check to an internal IP during the actual fetch. On most vulnerable paths the internal response is returned directly to the attacker; the OAuth path additionally forwards the OAuth access token as a Bearer header to the attacker-controlled internal target, enabling credential theft. No public exploit identified at time of analysis.
Insecure temporary file creation in Lenovo XClarity Essentials OneCLI 5.5.0 and earlier on Linux enables a local low-privileged attacker to overwrite or truncate arbitrary system files via a race condition (CWE-377), but only when a privileged user concurrently executes OneCLI with elevated rights. The attack timing requirement (AT:P in the vendor CVSS 4.0 vector) confirms this is a classic TOCTOU-style symlink race, limiting realistic exploitation to shared multi-user Linux environments where an administrator routinely runs the tool elevated. No public exploit code or CISA KEV listing exists; the vendor has released a patch via advisory LEN-ht116433.
NVIDIA Dynamo for Linux versions 0 through v1.2.0 leaks sensitive information through crafted error message generation, exploitable remotely without authentication. The CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) confirms low-complexity unauthenticated network access is sufficient to trigger disclosure. No public exploit code has been identified at time of analysis and no CISA KEV listing exists, indicating this is not currently confirmed as actively exploited at scale.
Out-of-bounds read in Systerel S2OPC versions 1.7.0 through 1.7.3 allows a local, low-privileged attacker to disrupt the OPC-UA client process by triggering a memory read violation in the DeleteMonitoredItemsRequest handler state machine function. The flaw is confined to the client-side wrapper component and results in an availability impact rather than code execution or data exfiltration. A public proof-of-concept exploit has been released on GitHub, and the vendor has not responded to coordinated disclosure, leaving no official patch confirmed at time of analysis.
Memory exhaustion in Django's `check_for_language()` function allows denial-of-service via the `set_language` view when it is explicitly enabled in URL configuration. Attackers can submit many distinct, very long language codes via POST requests, causing each code to be cached as an in-memory key and progressively consuming process memory. Django rates this severity 'low' because built-in guards - `DATA_UPLOAD_MAX_MEMORY_SIZE` and the cache's maximum entry count - bound the total exploitable memory; no public exploit identified at time of analysis.
Denial-of-service via recursive GEOMETRYCOLLECTION parsing crashes Django processes through a segmentation fault in the underlying GEOS library. Django's GEOSGeometry class, GeometryField form field, and spatial field lookups in versions 5.2, 6.0, 6.1 (RC), and main are all affected when processing WKT or WKB input containing deeply nested or excessively numerous GEOMETRYCOLLECTION objects. No public exploit code or active exploitation has been identified at time of analysis; the Django team rated this 'moderate' severity and issued fixed releases Django 5.2.17 and 6.0.8 on August 4, 2026.
Information disclosure in Qualcomm Snapdragon chipsets exposes private data transmitted during NG-eCall SIP signaling when IPSec negotiation fails or is improperly established. Attackers adjacent to the network can intercept unprotected signaling traffic, gaining access to sensitive session data - potentially including location coordinates and caller identity transmitted as part of the automated emergency call system. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
Information disclosure in Qualcomm Snapdragon wireless subsystem allows an adjacent-network attacker to leak sensitive memory contents by transmitting malformed wireless channel switch frames with invalid length fields. The root cause is CWE-191 (integer underflow), where improperly formatted length values trigger an arithmetic wrap condition during 802.11 management frame parsing, resulting in out-of-bounds memory reads. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, though the low attack complexity and no-authentication requirement on an adjacent wireless segment represent a meaningful real-world risk for shared wireless environments.
Stack-based out-of-bounds read in stunnel's s_vlog logging function allows remote unauthenticated attackers to crash the service by sending protocol inputs that generate log messages exceeding 1024 bytes via vsnprintf. The primary impact is service disruption (availability), with a limited integrity impact in corner cases where trailing newline characters in the stack buffer can be overwritten with null bytes. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Information disclosure in Firefox for Android and Firefox Focus for Android exposes sensitive user data to network-based attackers who can lure a victim into interacting with a crafted web resource. The vulnerability, tracked under CWE-200 and assigned a CVSS score of 6.5 with high confidentiality impact, is limited to Android platform builds and does not affect desktop Firefox. Mozilla patched this in Firefox 153.0.3 per advisory mfsa2026-73; no public exploit or active exploitation has been identified at time of analysis.
Observable response discrepancy in HUMANIST Digital Human Resources 26.0 exposes the system to unauthenticated account footprinting, enabling attackers to enumerate valid user accounts by analyzing differentiated server responses. The vulnerability is classified under CWE-204 and was reported by TR-CERT (Turkish national CERT), affecting the HR platform's authentication or account-lookup endpoints. No active exploitation has been identified in CISA KEV and no public exploit code is known, but the network-accessible, zero-authentication attack surface makes this a viable reconnaissance vector preceding credential-based attacks.
Insufficient session expiration in HUMANIST Digital Human Resources version 26.0 allows an attacker who obtains a valid session token to replay it indefinitely, effectively hijacking an authenticated user's session and gaining unauthorized access to HR data. Reported by TR-CERT (TR-26-0737), the flaw affects all 26.0 builds prior to 26.1 and carries a high confidentiality impact due to the sensitive nature of human resources data processed by the platform. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog.
Resource exhaustion via oversized serialized Lottie animation payloads in Samsung Open Source rlottie allows denial-of-service against any application embedding the library. The library failed to bound precomposition nesting depth, total render-node count, Repeater element copy counts, and did not validate non-finite float values (NaN/Infinity) for polystar and polygon point counts during deserialization and rendering. When a user or application opens a crafted Lottie JSON file, the renderer enters unbounded recursion or allocates excessive memory, crashing or hanging the host application. No public exploit or active exploitation (KEV) has been identified at time of analysis.
Broken object-level authorization in the REST API Log WordPress plugin (all versions before 1.7.1) permits unauthenticated attackers who hold any valid log-download token - regardless of which entry it was issued for - to retrieve arbitrary log entries from any other user, exposing stored credentials, authentication tokens, and private REST API payloads. The root cause is twofold: tokens are not cryptographically bound to specific log entry IDs, and the plugin performs no WordPress capability check on the requester. A public exploit PoC is referenced via WPScan, though EPSS at 0.18% and SSVC exploitation status of 'none' indicate no confirmed widespread abuse at time of analysis.
Uninitialized heap memory disclosure in SSSD's NSS responder exposes cached directory data and heap layout to local authenticated users on RHEL 6 through 10 and OpenShift Container Platform 4. The sss_nss_protocol_fill_initgr() function pre-allocates a reply buffer sized for all group entries but fails to shrink it when groups are skipped, causing uninitialized heap bytes to be included in the response transmitted back to the requesting client. No public exploit code has been identified at time of analysis, and this is not listed in CISA KEV; however, leaked heap addresses may assist in chained attacks targeting ASLR bypass in sssd_nss.
Forced logout via unsigned backchannel requests affects Red Hat Build of Keycloak when an OIDC identity provider is configured to skip signature validation. Under this non-default configuration, the backchannel logout endpoint in keycloak-services improperly accepts logout requests lacking any cryptographic signature (CWE-347), violating the OIDC backchannel logout specification. An unauthenticated network attacker who possesses knowledge of a target user's session identifiers can submit a forged unsigned logout request, terminating that session without the user's consent. No public exploit or active exploitation (CISA KEV) has been identified; with CVSS 3.7 and EPSS data absent from the input, this is a low-priority availability-only issue gated by a specific non-default configuration.
Debug unlock token cross-device reuse in Caliptra Core ROM and Core Firmware (subsystem mode) allows an attacker who already holds access to an integrator's debug unlock signing service to unlock production debug on an unintended device by presenting a token originally issued for a different device sharing the same debug unlock key hash. The 384-bit challenge nonce prevents replay of previously captured tokens but does not bind a token to a specific target device identity, enabling lateral debug access within a shared-key-hash trust group. No public exploit has been identified and the CVSS 4.0 score of 1.8 reflects the narrow real-world impact, which is bounded by the requirement for high-privilege signing-service access and the hard constraint that exploitation cannot cross key-hash group boundaries.
Microsoft Edge (Chromium-based) is affected by a Time-of-Check Time-of-Use (TOCTOU) race condition that allows a remote, unauthenticated attacker to disclose sensitive information over the network, contingent on user interaction. The flaw exploits the timing gap between a security check and subsequent resource use within the Chromium-based browser engine, potentially exposing cross-origin data or internal browser state. No active exploitation has been confirmed by CISA KEV, and the temporal CVSS metrics (E:U) confirm no proven exploit code exists at time of analysis; a vendor patch is available via MSRC.
Wildcard DNS SAN matching in python-cryptography's X.509 chain verifier prior to 49.0.0 allows a leaf certificate bearing *.example.com to satisfy a constrained intermediate CA's permittedSubtrees restriction of foo.example.com, enabling scope escape to sibling domains such as bar.example.com. Applications relying on the PolicyBuilder/Store verification API are exposed to acceptance of invalid certificate chains that should be rejected per RFC 5280 §4.2.1.10. A public proof-of-concept is confirmed in the GHSA advisory; the vulnerability is not in the CISA KEV catalog, but the CVSS 4.0 E:P modifier reflects the POC's availability.
Cookie domain scope bypass in Guzzle PHP HTTP client (prior to 7.15.2 and 8.0.1) allows improper cookie sharing via non-canonical IP address representations in cookie Domain attributes. The flaw in SetCookie::matchesDomain() fails to recognize hexadecimal (e.g., 0x7f000001), mixed-base octal (e.g., 0177.0.0.0x1), and percent-escaped (e.g., 192.168.0.%31) host spellings as IP literals, so cookies set for such domains incorrectly gain subdomain scope while libcurl resolves the same strings as actual IP addresses. This divergence enables an adversary-controlled host (e.g., evil.0x7f000001) to receive session cookies intended for the target IP, facilitating credential disclosure and session fixation; no public exploit identified at time of analysis.
HTTP request smuggling in aiohttp's server-side parser allows unauthenticated remote attackers to inject and misdirect HTTP traffic by exploiting a protocol-switch race in the WebSocket upgrade path. Versions 3.14.1 and earlier prematurely mark the connection as upgraded before the full request body is consumed, causing trailing bytes - potentially an attacker-controlled HTTP request - to be interpreted as WebSocket or pipelined data by the server or any upstream proxy. No public exploit code exists and the vulnerability is not listed in CISA KEV, but CVSS 4.0 AC:H reflects the edge-case nature of the trigger condition.
Man-in-the-middle interception of SSH sessions and file transfers is possible through the EMR SSH helper commands in Amazon AWS CLI v1 before 1.45.28 and v2 before 2.35.3 due to missing entity authentication during the SSH key exchange. Network-positioned attackers - requiring no privileges or user interaction - can substitute their own key material during the handshake and silently relay or inspect the session. No active exploitation is confirmed by CISA KEV, and no public proof-of-concept has been identified at time of analysis; however, the impact on downstream EMR cluster confidentiality is rated high (SC:H in the CVSS 4.0 vector).
Server-side template injection (SSTI) in Dify's Jinja2 Handler (versions ≤1.14.2) allows remote, low-privileged authenticated attackers to inject malicious Jinja2 template expressions through the code execution subsystem, resulting in information disclosure and potential further impact. A public proof-of-concept exploit is available on GitHub, materially lowering the bar for exploitation. The vendor did not respond to responsible disclosure, meaning no patch has been released and no official mitigation guidance exists.
Provisioning data interception in TP-Link Omada's cloud-based device adoption workflow allows a low-privileged network attacker to receive configuration secrets intended for a legitimate device. The vulnerability is a classic race condition (CWE-362): an attacker who can interact with the adoption workflow before a legitimate device completes registration can position themselves to receive the provisioning payload. Affected products span the full Omada ecosystem - controllers, access points, switches, and gateways. No public exploit or CISA KEV listing exists at time of analysis, but the confidentiality impact is rated High by the vendor's own CVSS 4.0 assessment.
Insufficient entropy in session key generation within the TP-Link Omada adoption protocol exposes encrypted controller-to-device communications to decryption by adjacent network attackers. The adoption protocol - the handshake sequence by which Omada Controllers onboard and establish management sessions with gateways, switches, and access points - generates session encryption keys with insufficient randomness, making them potentially recoverable through cryptanalytic means after traffic interception. No confirmed active exploitation (not in CISA KEV) and no public exploit code has been identified at time of analysis; however, the CVSS 4.0 score of 6.9 and the high confidentiality impact on both the vulnerable and subsequent systems indicate meaningful confidentiality risk for organizations relying on Omada-managed network infrastructure.
Hard-coded cryptographic keys in the TP-Link Omada adoption protocol allow adjacent-network attackers to impersonate trusted controllers or managed devices, exposing sensitive authentication material exchanged during device adoption. The flaw affects the entire Omada product line - gateways, switches, access points, and controllers - because all share the same embedded keys, meaning any attacker who extracts the keys from firmware can spoof identity during any adoption event on the same network segment. No public exploit or CISA KEV listing exists at time of analysis, but a vendor patch is available and should be applied promptly given the high confidentiality impact on subsequent systems.
Uncontrolled search path exploitation in CheckMAL AppCheck Pro 3.1.43.10's kernel mini-filter driver (AppCheckD.sys) allows a local attacker with low privileges to redirect the driver's library loading path, potentially achieving kernel-level code execution on the target host. A public proof-of-concept exploit has been released despite the vendor declining to respond to coordinated disclosure, making this a no-patch, public-exploit scenario. While high attack complexity (AC:H) reduces opportunistic risk, the complete confidentiality, integrity, and availability impact at the kernel layer makes successful exploitation highly damaging.
Improper export of the DialerActivity component in textPlus Text Message and Call App (Android, versions up to 8.3.5) allows any co-installed application on the same device to invoke the com.gogii.textplus dialer component without authorization. Classified under CWE-926, this flaw permits a locally-present malicious app to trigger dialer functionality, leading to limited information disclosure and unauthorized interaction with call-related features. No public KEV listing confirms active exploitation, but a proof-of-concept is publicly available on GitHub, lowering the technical barrier for abuse.
GNU tar's --one-top-level extraction mode fails to confine hardlink targets to the designated top-level directory, allowing a crafted archive to plant hardlinks that escape the intended extraction boundary. When combined with a preexisting symbolic link already present under the working directory, an attacker who can induce a victim to extract a malicious archive may read or write files outside the intended extraction scope on systems running affected RHEL versions (6 through 10) and Red Hat Hardened Images. No public exploit has been identified at time of analysis, and exploitation requires both user interaction and a specific environmental pre-condition, keeping real-world risk moderate despite GNU tar's ubiquitous deployment.
HCL iControl v3.2.0 exposes sensitive data in transit by advertising support for deprecated TLS 1.0 and TLS 1.1 protocol versions, which lack modern cryptographic protections. The CVSS vector (AV:N/AC:H/PR:N/UI:N) indicates a network-reachable flaw requiring high attack complexity - consistent with a man-in-the-middle positioning requirement for exploitation. No public exploit code and no CISA KEV listing exist at time of analysis, placing this in the medium-priority tier despite its network exposure, though organizations with regulatory requirements around cryptographic standards (PCI-DSS, NIST SP 800-52) should treat remediation as mandatory.
Out-of-bounds read in SSSD's NSS responder allows a local user with standard privileges to crash the SSSD process by sending a crafted GETHOSTBYADDR request, causing system-wide denial of authentication and name resolution services. The vulnerable function `sss_nss_protocol_parse_addr()` fails to validate the `addrlen` field against the actual remaining packet body size, enabling heap over-read and process termination. No public exploit code or active exploitation has been identified at time of analysis, and this vulnerability is not listed in CISA KEV.
Sharp Corporation's Network Scanner Tool and Network Scanner Tool Lite expose unauthenticated, unlimited file upload endpoints by default, enabling two distinct attack outcomes against any PC running the software in its initial configuration. An unauthenticated network attacker can flood the host with uploaded files to exhaust disk or system resources, causing a denial-of-service condition; separately, a threat actor can stage malicious executables that a local PC user may be socially engineered into running, enabling downstream attacks against other systems. No public exploit code has been identified at time of analysis, and no CISA KEV listing exists, though the default-insecure nature and zero authentication requirement lower the barrier to exploitation significantly.
Unauthenticated network access to address book editing and Document Filing features is possible on Sharp and Toshiba Tec multifunction printers (MFPs) sold outside Japan, because these devices ship from the factory with user authentication disabled. The root cause is CWE-1188 (Insecure Default Initialization of Resource) - the authentication control exists but is not activated in the initial configuration, meaning any network-reachable attacker can access sensitive stored data and modify contact directories without credentials. No public exploit code and no CISA KEV listing exist at time of analysis, but the CVSS vector confirms network-level unauthenticated access with no interaction required.
Incomplete cleanup of cached print job data in Sharp and Toshiba Tec multifunction printers exposes previously printed documents to subsequent physical users of the same device. Affecting all versions per CPE data (cpe:2.3:a:sharp_corporation:sharp_mfps and cpe:2.3:a:toshiba_tec_corporation:toshiba_tec_mfps), the flaw (CWE-459) means internal caches are not wiped after a print job completes, allowing the next person who physically accesses the device to potentially retrieve another user's data. No public exploit code exists and the vulnerability has not been added to CISA KEV, consistent with the low CVSS score of 2.4 and a physical-access attack vector.
Unauthenticated network access to stored image data affects Sharp and Toshiba Tec multifunction printers via a forced browsing vulnerability (CWE-425). Remote attackers without any credentials can directly request URLs referencing scanned or copied image data held on the device, bypassing the authorization layer entirely. Reported by JPCERT, this is an information disclosure issue with no public exploit identified at time of analysis and no confirmed active exploitation.
Sandbox escape in vxcontrol PentAGI up to 2.1.0 exposes a privilege boundary weakness in the Tool Management Protocol Handler, rooted in the pentester prompt template file. Remote unauthenticated attackers who can craft sufficiently complex inputs may bypass sandbox constraints on the AI agent's tool execution context, achieving limited confidentiality, integrity, and availability impact against the vulnerable system. A public proof-of-concept exists on GitHub; no patch has been released and the vendor has not responded to disclosure - leaving all deployments on versions up to 2.1.0 without a vendor-sanctioned fix.
Cleartext storage of personally identifiable information in Meesho Online Shopping App (Android, versions through 20260607) exposes user_id, phone number, email address, and name in the com.meesho.supply component without encryption. Exploitation requires physical access to the device and a degree of local privilege, making this a low-severity, localized threat rather than a remote or mass-exploitation risk. A proof-of-concept is publicly available via GitHub and Google Drive, though no active exploitation has been confirmed by CISA KEV.
NLTK's downloader in version 3.9.4 installs attacker-controlled package bytes by writing and potentially extracting downloaded content before enforcing SHA-256 or MD5 checksum validation. Any user or CI pipeline invoking `nltk.download()` against a compromised mirror, rogue proxy, or network-level MITM is at risk of silently installing malicious corpora or model files. No public exploit identified at time of analysis; active exploitation not confirmed (no CISA KEV listing). The AC:H CVSS metric correctly reflects the non-trivial infrastructure access an attacker must achieve, but the downstream trust propagation - NLP applications consuming poisoned models - amplifies the realistic impact beyond the base score.
Username enumeration is possible in PaperCut NG/MF via an observable timing side-channel in the authentication component, exploitable by unauthenticated remote attackers. The system conditionally executes password hash comparison only when a submitted username corresponds to a valid account, producing a measurable latency difference that reveals account existence. No public exploit code or CISA KEV listing has been identified at time of analysis; however, with a CVSS 4.0 score of 6.9 and an AV:N/PR:N vector, the attack surface is entirely remote and requires no credentials, making it accessible to any attacker with network reach to the login endpoint.
PaperCut NG/MF's login component fails to enforce account lockout or rate-limiting controls in certain configurations, allowing unauthenticated remote attackers to conduct unrestricted brute-force or credential-stuffing attacks against user accounts. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N) confirms no authentication or user interaction is required, though the 'in some configurations' qualifier in the CVE description indicates exploitation is conditional on the absence of hardening controls. PaperCut published a security bulletin on August 3, 2026; no public exploit code or CISA KEV listing has been identified at time of analysis.
Out-of-bounds read in mz-automation libiec61850 up to version 1.6.1 allows remote unauthenticated attackers to crash the IEC 61850 MMS server process and potentially leak heap or stack memory contents by sending a crafted MMS DataSet access request. The root cause is unconstrained string copy operations in the checkDataSetAccess function, now confirmed fixed in v1.6.2 via bounded copy with a 129-byte limit. A public exploit has been disclosed; however, this vulnerability is not listed in CISA KEV and the CVSS 4.0 score of 6.9 (Medium) reflects limited impact scope confined to availability of the vulnerable system.
Out-of-bounds read in MediaTek's GeniZone trusted execution environment (TEE) exposes memory on 17 affected chipset models to local information disclosure, but only after an attacker has already acquired System-level privilege. The vulnerability stems from a missing bounds check in the geniezone driver (CWE-125, Patch ID ALPS11036877), and is tracked by MediaTek as MSV-7132. No public exploit code exists and CISA has not listed this in KEV; with an EPSS of 0.14% (4th percentile) and SSVC exploitation status of 'none', this is a low-urgency finding despite the breadth of affected silicon.
Out-of-bounds read in the MediaTek Wi-Fi driver component on MT6988, MT6990, and MT6890 chipsets permits local information disclosure against devices where an attacker has already obtained System-level privilege. The missing bounds check in the Wi-Fi stack allows reading memory beyond the intended buffer boundary, exposing potentially sensitive kernel or driver memory contents. No public exploit exists and EPSS at 0.13% (3rd percentile) reflects the significant privilege prerequisite that constrains real-world exploitation; CISA KEV does not list this vulnerability.
Out-of-bounds read in MediaTek's ccci (Cross Core Communication Interface) driver on multiple chipsets enables local denial of service by a System-privileged attacker. Affected chipsets include MT6813, MT6988, MT6982VB, MT6986D, and MT6986 - targeting mid-range and flagship Android SoC lines. No public exploit code exists and CISA has not added this to KEV; real-world impact is constrained by the high privilege prerequisite, making this a post-compromise availability risk rather than an initial access vector.
Local information disclosure in the display subsystem of multiple MediaTek SoC chipsets results from a CWE-125 out-of-bounds read triggered by an integer overflow. Seventeen distinct chipsets are confirmed affected per the EUVD listing, spanning devices such as MT8910, MT8188, MT8768, and MT6991 - all prevalent in mid-range and budget Android hardware. Exploitation requires an attacker who has already attained System-level privilege on the device; no public exploit exists and EPSS sits at 0.14% (4th percentile), consistent with the SSVC exploitation rating of 'none'.
Local information disclosure in MediaTek's display subsystem exposes arbitrary kernel memory to a privileged local process due to a missing bounds check (CWE-125). Exploitation is limited to actors who have already obtained System-level privileges on a device running one of 17 affected MediaTek chipsets (MT6991, MT8676, MT8799, and others). No public exploit code and no active exploitation have been identified; EPSS sits at 0.14% (4th percentile), consistent with SSVC's 'none' exploitation status and 'no automatable' classification.
Information disclosure in the TFA (Trusted Firmware-A) component of MediaTek chipsets allows a local attacker who has already obtained System-level privilege to retrieve sensitive secure-world data without user interaction, due to a missing permission check (CWE-201). The flaw spans 39 distinct MediaTek chipsets across the MT6xxx and MT8xxx families, covering a broad range of Android smartphones, tablets, and embedded devices. No public exploit code or active exploitation has been identified; EPSS stands at 0.14% (4th percentile), consistent with the high privilege prerequisite limiting real-world impact.
Local information disclosure in the Telephony component across 42 MediaTek chipsets enables any unprivileged application on the device to extract sensitive telephony data without elevated permissions. The root cause is a missing Android permission check (CWE-926: Improper Export of Android Application Components), allowing improperly exported Telephony interfaces to be queried by any installed app. No active exploitation is confirmed - EPSS sits at 0.15% (5th percentile) and the vulnerability is absent from CISA KEV - but the breadth of affected chipsets spanning budget through flagship tiers gives this issue significant deployment reach. Patch ALPS11086431 is available per MediaTek's August 2026 security bulletin.
Remote unauthenticated crash in mz-automation libiec61850 1.6.0-1.6.1 allows a network attacker to terminate an IEC 61850 MMS server by supplying an oversized Report ID string to the Report Control Block write handler, triggering a free of non-heap memory (CWE-590). No authentication or user interaction is required per the CVSS 4.0 vector (PR:N/UI:N/AV:N), and a public proof-of-concept exploit exists at the referenced GitHub issue. Active exploitation has not been confirmed by CISA KEV, but the combination of a public PoC and trivial exploitation path elevates practical risk in operational technology environments where IEC 61850 server continuity is safety-critical.
PSA Crypto key slot exhaustion in Zephyr's Bluetooth Mesh subnet.c permanently leaks one key slot on every subnet key teardown when CONFIG_BT_MESH_PRIV_BEACONS is enabled (the default). Devices running Zephyr 3.6.0 through 4.4.x are affected: a provisioner or network administrator with the node's device key can trigger the leak via Config Server NetKey Delete, Key Refresh Procedure, or reprovisioning over the Bluetooth Mesh network. With the default pool of 16 PSA key slots, roughly a dozen such operations exhaust the pool, preventing subnet creation and potentially starving other on-device PSA consumers until a reboot. No public exploit or CISA KEV listing exists; real-world impact is constrained by the high-privilege and proximity requirements.
PHP object injection in the Event Booking Manager for WooCommerce WordPress plugin (all versions before 5.3.7) allows authenticated contributors to deserialize attacker-controlled PHP objects through event content fields. Exploitation to achieve remote code execution, arbitrary file deletion, or sensitive data retrieval depends entirely on the presence of a usable POP (Property-Oriented Programming) chain from a co-installed plugin or theme - none exists within this plugin itself. A publicly available exploit exists per WPScan (EUVD-2026-51948), and this CVE represents an incomplete remediation of prior object-injection advisories affecting the same plugin.
Local HDF5 file content disclosure in keras-team/keras versions 3.14.0 and earlier allows an attacker who can deliver a malicious model file to exfiltrate arbitrary local filesystem data from a victim's machine. Both the `KerasFileEditor` class and `keras.saving.load_weights` function fail to invoke the `safe_get_h5_group` and `safe_get_h5_dataset` helpers before traversing HDF5 group children, causing automatic dereferencing of embedded ExternalLinks and SoftLinks that point to attacker-controlled paths on the victim's filesystem. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the attack mechanism is straightforward and the commit diff makes the vulnerability trivially reproducible.
Read-side prototype pollution gadgets in axios allow a secondary attacker primitive to corrupt HTTP request semantics when Object.prototype has already been polluted by a separate, pre-existing vulnerability in the same application. Affected are the bodyless method aliases - axios.get(), axios.delete(), axios.head(), and axios.options() - across all 1.x releases below 1.18.0 and all 0.x releases below 0.33.0. An attacker who controls Object.prototype pollution can inject a fabricated request body into what the application intends as a bodyless request, or, via lower-level adapter paths, route requests through an attacker-controlled proxy or invoke custom URL serialization logic. No public exploit identified at time of analysis and no CISA KEV listing, but the CVSS 4.0 AT:P metric explicitly models the required precondition attack.
Stale session persistence in better-auth allows deleted users to maintain authenticated access for up to seven days after account removal. Affected are deployments of better-auth versions 0.3.4 through 1.6.10 running with secondaryStorage (Redis, KV, or similar external cache) and the default storeSessionInDatabase=false setting, where user deletion flows through the admin, anonymous, or SCIM plugins. Because deleteSessions is never called before deleteUser in these code paths, the session payload remains live in the cache until TTL expiry, meaning a terminated employee or compromised account that has been administratively deleted can continue making authenticated requests. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV.
Out-of-bounds heap read in FreeRDP's UVC H.264 extension-unit parser affects all versions prior to 3.29.0, allowing an attacker with physical USB access to trigger denial of service during camera stream setup. The parser fails to validate descriptor length before accessing the GUID field, enabling a read beyond allocated heap bounds when a malicious USB video camera is connected. No public exploit has been identified, KEV listing is absent, and the CVSS 4.0 score of 2.4 accurately reflects the constrained physical-access attack surface.
Divide-by-zero in FreeRDP's rdpecam camera redirection channel allows a malicious or compromised RDP server to crash the connecting client process by sending a StartStreamsRequest PDU with FrameRateDenominator set to zero. All FreeRDP releases up to and including 3.28.0 are affected when camera redirection is enabled; exploitation delivers a reliable client-side denial-of-service (SIGFPE termination) with no code execution potential. No public exploit or CISA KEV listing exists at time of analysis; this is a medium-severity availability issue patched in FreeRDP 3.29.0.
Out-of-bounds read in FreeRDP 3.28.0 and earlier allows a malicious or compromised RDP server to leak client-side memory contents or crash the FreeRDP process by sending a crafted truncated planar-encoded bitmap or surface update. The flaw lives in the RDP6 planar RLE decoder (libfreerdp/codec/planar.c), where attacker-declared raw byte counts of 0-15 bytes following a bounds-checked control byte are consumed without verifying remaining buffer space. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis; FreeRDP 3.29.0 contains the confirmed vendor patch.
Proxy-Authorization header leakage in guzzlehttp/guzzle before 7.14.2 allows origin servers to receive proxy credentials due to a cURL handler misclassification bug. When requests are routed via SOCKS proxies, match no_proxy bypass rules, connect directly with proxying disabled, or cross proxy boundaries during redirects, Guzzle fails to migrate the Proxy-Authorization header from cURL's origin header list to the proxy-only channel - the credential arrives at the origin server instead of being confined to the proxy hop. An attacker who controls or monitors a destination origin server can harvest these credentials from access logs, then abuse the proxy to impersonate the proxy principal or reach destinations gated behind that proxy. No public exploit code has been identified at time of analysis.
Session revocation via forged cookies in better-auth's multi-session plugin (npm, versions 1.3.34 through <1.4.0) allows any authenticated attacker to arbitrarily delete session tokens belonging to other users by supplying a crafted `_multi-*` cookie to the /sign-out after-hook, which forwards cookie values to `internalAdapter.deleteSessions()` without verifying the cryptographic signature. The flaw is not listed in the CISA KEV catalog and no public exploit code has been identified, but the low attack complexity makes unauthorized targeted session termination straightforward once an attacker holds any valid application session. Version 1.4.0 resolves the issue via patch commit cfc453a2a6eb02951f9a0a7c944064936e73eee8.
Out-of-bounds read in Zephyr RTOS DHCPv4 client (versions 1.7.0 through 4.4.x) allows an adjacent-network attacker to crash the DHCP client or leak adjacent pointer contents by sending a crafted DHCP reply with a message-type value greater than 8. The defect is a classic sizeof-vs-ARRAY_SIZE confusion: the bounds guard compares a raw msg_type byte against the byte-size of a pointer array (32 or 64, depending on architecture) rather than its element count of 8, so values 9-31/63 bypass the check and cause a wild-pointer dereference inside a debug log call. Exploitation is gated on a non-default build configuration (CONFIG_NET_DHCPV4_LOG_LEVEL_DBG), substantially reducing the real-world attack surface. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
Bluetooth GATT notification and indication paths in Zephyr RTOS 2.6.0 through 4.4.x skip the application-configured encryption, authentication, and LESC security requirements for characteristic values when the application follows the documented idiom of passing the Characteristic Declaration attribute to the notify/indicate APIs. A remote Bluetooth peer within radio range can connect without pairing and trigger the server to emit protected characteristic values over an unsecured link by writing the Client Characteristic Configuration descriptor, achieving an access-control bypass and information disclosure. No public exploit is identified at time of analysis; exploitation requires adjacent network access and specific application configuration.
Unauthenticated sensitive information disclosure in the WooCommerce PayPal Payments WordPress plugin (all versions through 3.3.2) allows remote attackers to harvest full customer billing PII from recently placed orders. The vulnerability is a two-stage IDOR chain: the `enqueue_paypal_insights_script_on_order_received()` function exposes order keys without validating the caller's identity, and those keys can then be replayed against the WooCommerce Store API - which grants a 10-minute post-order grace period - to retrieve names, email addresses, phone numbers, and street addresses. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, but the network-reachable, zero-authentication attack path and PII sensitivity elevate practical risk above the CVSS 5.3 numeric score.
Sensitive information exposure in the Advanced Views WordPress plugin (wplakeorg, all versions ≤ 3.9.1) allows any authenticated subscriber-level user to harvest admin-authored editor content - including template markup, CSS, JavaScript, and PHP controller variables - via improperly authorized REST API routes. Wordfence identified the flaw across three CPT interactive field classes (base, Layout, and Post Selection). No public exploit code or CISA KEV listing exists at time of analysis, but the low authentication bar of subscriber-level access makes this trivially exploitable on any WordPress site with open user registration.
Sensitive WooCommerce order data exposure in the PixelYourSite WordPress plugin (all versions through 11.2.1) allows unauthenticated remote attackers to retrieve full purchase metadata - product names, quantities, per-item prices, order totals, currency, and transaction IDs - for any order by supplying an arbitrary or invalid order key alongside a known order ID. The plugin's getWooPurchaseEventParams function resolves orders solely from the URL path order ID without validating the accompanying key, then emits the complete woo_purchase tracking payload directly into rendered page HTML via the pysOptions JavaScript object across all three supported integrations (Facebook Pixel, Google Analytics, and Google Tag Manager). No public exploit has been identified at time of analysis, but because WooCommerce order IDs are sequential integers by default, mass enumeration of the entire order history requires only a trivial HTTP loop.
Local file inclusion in the GetPaid WordPress plugin (versions ≤ 2.8.56) enables authenticated administrators to include and execute arbitrary PHP files on the server by supplying a crafted element type value to the getpaid_payment_form_element function. The root cause (CWE-98) is twofold: the element type string was used unsanitized to construct a PHP template file path, and the bare extract($element) call without EXTR_SKIP allowed attacker-controlled array keys to overwrite internal variables including the path already resolved. No public exploit code or active exploitation (CISA KEV listing) has been identified at time of analysis; real-world risk is substantially constrained by the administrator-level access and PHP file upload prerequisites.