Information Disclosure

Insecure Direct Object Reference in BookWyrm's status edit endpoint (EditStatus) through version 0.9.1 exposes followers-only and direct-message reviews to any authenticated user. Because status IDs are sequential and the edit view does not validate the requesting user's visibility permissions against the target status, an authenticated attacker can enumerate integer IDs to retrieve the raw content of private statuses they should not be able to read. No public exploit has been identified at time of analysis, but a public researcher writeup with proof-of-concept reproduction steps exists, lowering the bar for exploitation.

JetFormBuilder - Dynamic Blocks Form Builder for WordPress before version 3.6.5.2 exposes sensitive site data to unauthenticated remote attackers due to missing authorization checks during page rendering. By submitting crafted requests that reference internal WordPress data sources, attackers can read arbitrary user properties including password hashes, private and draft post content, term metadata, and secrets stored by the plugin in post metadata fields. A publicly available proof-of-concept exploit exists, and the zero-privilege network attack path makes this a credible mass-scanning target for WordPress infrastructure.

Plaintext MQTT transmission in Trueview TI8161 firmware 6.0.23.4 exposes all device communications on TCP port 1883 to passive interception by any attacker on the same network segment. The device sends MQTT traffic without TLS encryption, allowing recovery of device identifiers, operational metadata, and control-related payloads with no authentication required. No public exploit has been identified beyond a GitHub research writeup, and EPSS is very low (0.15%, 4th percentile), though the absence of transport security makes passive interception trivially straightforward for any adjacent network attacker.

Improper verification of cryptographic signatures in the MQTT command handler of Trueview T18161 S firmware 6.0.23.4 lets a network-positioned attacker replay or tamper with captured MQTT messages — including their nonce, timestamp, and signature fields — and have the device accept and execute the embedded commands. The flaw (CWE-347) yields high

Full physical memory disclosure in PassMark's shared kernel driver DirectIo64.sys affects PerformanceTest (before 11.1 build 1012), BurnInTest (before 11.1 build 1000), and OSForensics (before 11.1 build 1016) on Windows. A low-privileged local attacker can issue a single IOCTL call supplying an attacker-controlled output path, causing the driver to enumerate all physical memory ranges via MmGetPhysicalMemoryRanges and map each page through ZwMapViewOfSection on the PhysicalMemory section object, writing a complete RAM image to disk in SYSTEM context and bypassing user-mode ACLs. Exposed data includes LSASS working-set memory, per-process heap contents, and in-use cryptographic keying material from all running processes. A public proof-of-concept is available at GitHub and no active exploitation (KEV) has been confirmed at time of analysis.

Physical memory disclosure and arbitrary SYSTEM-context file write in PassMark PerformanceTest (before 11.1 build 1012), BurnInTest (before 11.1 build 1000), and OSForensics (before 11.1 build 1016) are caused by the shared DirectIo64.sys kernel driver accepting a single IOCTL with no caller-identity validation. Any unprivileged local Windows user can invoke the handler to dump all physical memory in PAGEDU64 crash-dump format to an attacker-chosen path, with the write executed in SYSTEM context - enabling cross-process memory extraction, credential harvesting, and writes to otherwise-inaccessible filesystem locations. Publicly available exploit code exists (GitHub repository confirmed by VulnCheck); no active exploitation has been confirmed in CISA KEV at time of analysis.

undici's cache interceptor mishandles the Set-Cookie response header, failing to either refuse storage or strip it, so in the default shared-cache mode a cacheable response carrying Set-Cookie is stored and later replayed to a different caller matching the same cache key. This discloses one caller's cookies to another party and lets an untrusted origin inject cookies into cached responses served to every subsequent caller. Affected are undici 7.0.0 through 7.29.1 and 8.0.0 through 8.10.2; fixes are available in 7.29.1 and 8.10.2, exploitation is not confirmed in CISA KEV, EPSS probability is low (0.25%), and no public exploit code has been identified.

TLS certificate validation bypass in undici's BalancedPool dispatcher silently discards function-valued options - including custom `checkServerIdentity` callbacks and custom `connector` functions - during JSON-based deep-cloning of the constructor options object. Affected versions span 7.24.1 through 7.29.0 and 8.0.0 through 8.10.1. An attacker performing a network man-in-the-middle attack can present a TLS certificate that passes Node.js's built-in hostname and chain checks but would have been rejected by the application's custom validation logic, allowing an unauthorized TLS session to be silently established. No public exploit code has been identified at time of analysis, but the CVSS I:H and C:H signals confirm the potential for both data interception and traffic tampering.

Server-side template injection (SSTI) in IBM Verify Identity Access and Security Verify Access exposes sensitive information to unauthenticated remote attackers via a network-accessible endpoint. The vulnerability affects both traditional appliance deployments and container variants across IBM's IAM product family (versions 10.x and 11.x), and is particularly notable given that IAM platforms routinely handle authentication tokens, user credentials, and security policy configuration - data whose disclosure has outsized downstream impact. IBM has assessed the impact as confidentiality-only (I:N/A:N in the CVSS vector), suggesting the template injection is sandboxed against code execution, but no public exploit or active exploitation has been identified at time of analysis.

Cross-origin cache key confusion in undici 8.10.0 and 8.10.1 allows unauthenticated network attackers to receive responses intended for a different upstream origin and to persistently poison the cache with attacker-controlled content. When the cache or request-deduplication interceptor is composed directly onto a Client or Pool instance, the origin is silently dropped from the key and falls back to an empty string, meaning any two origins sharing the same HTTP method, path, and relevant headers share a single cache slot. The OpenJS Foundation reporter demonstrated full authentication bypass in which a JWT signed with an attacker-controlled key was accepted in place of a trusted issuer's token because the trusted origin was never contacted; no public exploit code has been released at time of analysis.

Session isolation failure in IBM ContextForge MCP Gateway - Translate Utility (≤ 1.0.8) permits unauthenticated remote attackers to access session data belonging to other users and potentially inject content into those sessions, due to improper enforcement of session boundaries (CWE-488). The CVSS AC:H metric indicates exploitation depends on specific timing or concurrency conditions - likely a race condition or shared mutable state in multi-tenant request handling - rather than a trivially triggerable flaw. IBM has released a remediation; no public exploit code has been identified at time of analysis.

Unauthenticated remote information disclosure in IBM Langflow OSS 1.0.0 through 1.11.2 allows network-accessible attackers to retrieve sensitive credential fields that are incompletely scrubbed from API responses or workflow data outputs. The CVSS vector (AV:N/AC:L/PR:N/UI:N/C:H) confirms this is exploitable over the network without any authentication or user interaction, and the high confidentiality impact reflects that leaked credentials may include API keys, passwords, or tokens used to integrate with downstream services. No public exploit code or active exploitation has been identified at time of analysis, and IBM has released a patch via their security advisory.

Credential disclosure in Onyx 4.6.6 allows any authenticated user to retrieve plaintext API keys and authorization headers that administrators configured for custom tool integrations. By calling GET /tool or GET /tool/{tool_id} with standard user credentials, an attacker can read admin-defined third-party API keys stored in custom_headers fields without any privilege escalation. A proof-of-concept exists per SSVC classification, and the stolen credentials can be leveraged to directly access upstream APIs the Onyx instance is connected to, entirely outside the platform's audit trail.

Unauthenticated arbitrary file read in the surya 0.22.1 screenshot server allows any network-reachable attacker to exfiltrate image and PDF files from the host filesystem by supplying attacker-controlled paths to three unprotected HTTP routes. The /info, /page, and /process endpoints pass raw file_path parameters directly to Pillow's Image.open and pypdfium2.PdfDocument, returning rendered file contents as base64-encoded HTTP responses. The /info route additionally acts as a file-existence oracle, enabling systematic enumeration of host paths before targeted exfiltration; no public exploit has been identified at time of analysis.

Unauthenticated arbitrary-path file read in Xinference v3.x (including commit 4a94832 and v3.3.0) exposes server filesystem content to any network-accessible attacker via the POST /v1/models/llm/auto-register endpoint. The endpoint accepts a caller-supplied model_path without authentication or path validation, reads config.json, tokenizer_config.json, and chat_template.jinja from that path, and reflects the parsed content in the HTTP response. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, but the zero-prerequisite network attack makes any internet-exposed Xinference instance immediately at risk.

Observable response discrepancy in GastroMenum Web Panel exposes account existence to unauthenticated remote attackers via differential server responses, enabling systematic account footprinting. All versions prior to 31.08.2026 of the web panel are affected. Reported by TR-CERT, this flaw (CWE-204) allows an attacker to distinguish valid from invalid accounts without any credentials, providing a reliable enumeration primitive for downstream attacks such as credential stuffing or targeted phishing. No public exploit code or CISA KEV listing identified at time of analysis.

Observable response discrepancy in Menulux Portal (all builds before 20260903211448) enables unauthenticated account footprinting against the portal's login or account-resolution endpoint. By observing measurable differences in server responses - such as distinct HTTP status codes, error messages, or timing - for valid versus invalid account identifiers, an attacker can systematically enumerate existing user accounts. Reported by TR-CERT with no public exploit code or CISA KEV listing identified at time of analysis.

Plaintext password storage in Menulux Portal (CWE-256) exposes embedded credentials to any low-privileged authenticated user over the network. All portal versions prior to build 20260903211448 are affected. Disclosed by TR-CERT; no public exploit code or active exploitation has been identified at time of analysis, though the High CVSS confidentiality rating reflects full credential retrieval capability.

Heap use-after-free in libsoup's HTTP/2 client implementation allows a malicious HTTP/2 server or MITM attacker to corrupt memory during asynchronous file upload operations. When a GNOME application uploads a file over HTTP/2 and the server sends a GOAWAY frame while the request body is being read asynchronously, the freed memory region can be accessed again, leading to information disclosure or arbitrary code execution on the client. No public exploit has been identified at time of analysis, and no KEV listing is present, but the unauthenticated network reachability combined with user-interaction-only barrier makes this a meaningful client-side threat.

Sensitive system information exposure in XING CPTrans-ME-X (a rack-mounted accessory from XING Inc., distributed under the JOYSOUND product ecosystem) allows unauthenticated remote attackers to retrieve confidential system details over the network without any privileges or user interaction. Classified as CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), the vulnerability was reported by JPCERT and documented in JVN advisory JVN#32505330. No public exploit code has been identified at time of analysis, though the unauthenticated, low-complexity network attack vector makes opportunistic probing accessible to low-skilled actors if the device is network-reachable.

Session hijacking in the Canva Android App before version 2.376.0 arises from an unrestricted header-reflection flaw in a privileged WebView component. An attacker who can control an external origin loaded within that WebView receives sensitive HTTP headers - including session tokens - that the app fails to suppress, exposing the authenticated user's session and enabling full account takeover. No public exploit has been identified at time of analysis; the flaw is patched in v2.376.0 per the Canva trust advisory.

Session hijacking in the Canva Android App before 2.376.0 lets an attacker-controlled web page interact with the Canva application using the victim's authenticated session because an external origin could be loaded inside a privileged WebView (CWE-940). A threat actor who lures a user into loading a malicious page can send requests to Canva as the user, reading and modifying account data. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.

Local File Inclusion in the Divi Ajax Filter WordPress plugin (all versions through 5.1.2) lets remote unauthenticated attackers include and execute arbitrary .php files on the server via the 'custom_loop_template' parameter. Reported by Wordfence and rated CVSS 9.8, it enables access-control bypass, sensitive-data disclosure, and - where an attacker can plant a .php file (e.g. through an upload) - remote code execution. No public exploit has been identified at time of analysis and the plugin is not in CISA KEV.

WHMCS's 2Checkout payment gateway endpoint exposes customer data to unauthenticated remote attackers due to a missing authorization check (CWE-862) across versions 8.13.0 through pre-8.13.8, 9.0.0 through pre-9.0.8, and all end-of-life releases from 4.5.0 onward. The flaw enables an unauthenticated network attacker who meets specific deployment conditions - the 2Checkout payment gateway must be configured and active - to retrieve WHMCS customer records through the unprotected endpoint. Vendor-released patches are available as WHMCS 8.13.8 and 9.0.8; no public exploit code or CISA KEV listing has been identified at time of analysis.

Server-side request forgery (SSRF) in Invoice Ninja v5.13.24 enables attackers to make the application server issue HTTP requests to internal and loopback network targets via unsanitized webhook destination URLs in StoreWebhookRequest.php, UpdateWebhookRequest.php, and WebhookSingle.php. By supplying RFC 1918 private addresses, loopback targets (127.0.0.1, ::1), or cloud metadata endpoints as webhook destinations, an attacker can probe internal services and retrieve sensitive responses that should be inaccessible from the internet. No public exploit code or active exploitation (CISA KEV) has been identified; EPSS at 0.17% (6th percentile) reflects minimal current exploitation interest.

NoSQL injection in Microsoft Discovery Studio enables unauthenticated, network-based attackers to extract confidential data from the application's backend data store. The CWE-943 flaw allows specially crafted query inputs to bypass intended data-access boundaries, with the CVSS scope-change (S:C) indicating that leakage can extend beyond the directly targeted component - potentially exposing data belonging to other users or system contexts. Exploitation requires user interaction (UI:R), constraining opportunistic mass attacks; no public exploit code and no CISA KEV listing have been identified at time of analysis.

Unauthenticated buffer over-read in MOOS core-moos through 10.4.0 allows any attacker with TCP access to the MOOSDB port to crash the server or leak process memory by sending a crafted 4-byte packet. The CMOOSCommPkt deserialization path fails to validate that the declared packet length meets the minimum header size before calling Serialize(), causing it to read the message-count field from memory beyond the end of the received data. No authentication is required - exploitation precedes any credential exchange, making this reachable on any exposed MOOSDB instance. No public exploit has been identified at time of analysis, but the fix PR (GitHub #75) precisely documents the trigger condition.

Unauthenticated network attackers can trigger out-of-bounds memory reads in MOOS-IvP through version 24.8.1 by sending NODE_REPORT messages containing leading or trailing whitespace. The three affected functions - isQuoted(), isBraced(), and isChevroned() in MBUtils.cpp - strip whitespace into a modified string but then index that shorter buffer using the original string's length, causing reads past the end of the stripped buffer and exposing adjacent heap memory or crashing the process. No public exploit or CISA KEV listing has been identified at time of analysis; the upstream fix is available as a GitHub commit and pull request but a tagged release version has not been independently confirmed.

Unauthenticated shore-route hijacking in MOOS-IvP's uFldNodeBroker (through 24.8.1) lets any client of the vehicle's MOOSDB message bus enroll an attacker-controlled shore route by publishing a spoofed TRY_SHORE_HOST message, which the broker accepts without verifying its source. Once enrolled, the vehicle bridges its configured variables to the attacker's address, redirecting sensor telemetry and control-channel traffic. Reported by VulnCheck; a vendor fix exists as an upstream PR, and there is no public exploit identified at time of analysis.

Bridge-route injection in MOOS-IvP's uFldShoreBroker component (through version 24.8.1) lets remote unauthenticated attackers redirect bridged mission variables to attacker-controlled hosts. The shore broker accepts NODE_BROKER_PING messages and builds outbound pShare bridge routes from the sender-supplied HostRecord without verifying the ping's authenticity (CWE-345), so a forged ping can silently reroute autonomous-vehicle telemetry and control traffic. A vendor patch exists (PR #123 / commit 2f5224d) and the flaw was reported by VulnCheck, but no public exploit or active exploitation has been reported.

Out-of-bounds heap read in DASYLab's .DSB file parser allows memory disclosure and potentially code execution when a victim opens a specially crafted workspace file. All DASYLab versions prior to 2026.0.0 are affected. The CVSS 4.0 vector assigns high confidentiality, integrity, and availability impact to the vulnerable system, indicating the flaw may be exploitable beyond simple information leakage - a heap OOB read during string conversion can sometimes be chained into controlled code execution depending on heap layout. No public exploit or CISA KEV listing is identified at this time.

Out-of-bounds memory read in DASYLab's .DSB file parser (all versions before 2026.0.0) allows an attacker to read beyond the bounds of an allocated data structure, potentially disclosing adjacent memory contents and crashing the application. Exploitation requires convincing a user - typically an engineer, lab technician, or researcher - to open a specially crafted DASYLab worksheet file. No public exploit code or active exploitation has been identified at time of analysis; vendor measX has released version 2026.0.0 as the fix.

Out-of-bounds heap read during .DSB file parsing in DASYLab (all versions prior to 2026.0.0) allows an attacker who can persuade a user to open a specially crafted data file to potentially disclose heap memory contents and crash the application. The root cause is CWE-125: insufficient validation of user-supplied length or offset fields during file-handling routines, causing reads a few bytes past an allocated heap buffer boundary. No public exploit code or active exploitation has been identified at time of analysis; vendor-released patch is version 2026.0.0.

Unauthenticated information exposure in Apache Allura through version 1.20.0 allows remote attackers to retrieve non-public project content via the search functionality, bypassing access controls enforced elsewhere in the application. The search subsystem fails to apply visibility restrictions consistently, meaning private tickets, wiki pages, discussions, or code artifacts indexed by search may be readable without authentication. No public exploit code has been identified at time of analysis, and the EPSS score of 0.20% (10th percentile) reflects minimal observed exploitation interest despite the unauthenticated attack vector.

Unauthenticated exposure of OAuth client_secret credentials via the /oauth2/register endpoint affects Medplum versions 4.1.10 through 5.1.6, a healthcare developer platform widely used to build FHIR-compliant apps. When a caller submits a redirect_uri that matches a pre-configured entry in the server's defaultOAuthClients configuration block, the registration endpoint reflects the stored client_secret back in the response - effectively handing an attacker the credential needed to impersonate that OAuth client. The vendor patched this in version 5.1.7 (PR #8837); no public exploit has been identified at time of analysis.

Token forgery in python-jose through 3.5.0 lets an attacker who possesses the service's asymmetric public key mint valid HS256 (HMAC) JWTs, because the library's HMAC key initialization accepts DER-encoded public keys that lack PEM armor or SSH prefixes and never rejects them as asymmetric material. This is a classic JWT algorithm-confusion (RSA/EC-to-HMAC) attack that succeeds whenever the verifying application does not explicitly restrict the accepted algorithms, and it represents an incomplete fix for CVE-2024-33663. There is no public exploit identified at time of analysis, though the technique is well-documented and the same class of flaw has prior public tooling.

TLS certificate validation is disabled by default in the Federator component of Eclipse aeriOS, enabling man-in-the-middle interception of all outbound HTTPS connections made by the component. Any attacker who can position themselves on the network path between the Federator and external services - including OAuth authorization servers - can impersonate those services and harvest OAuth client credentials and bearer tokens. This affects only the current pre-release development codebase; a source-level fix is confirmed in commit 9c63b60, but no official tagged release exists. No public exploit or CISA KEV listing has been identified at time of analysis.

Improper TLS certificate validation in MISP's CurlClient class allows an adjacent-network attacker to perform man-in-the-middle attacks against outbound HTTPS connections made by the MISP instance, including threat intelligence synchronization. The PHP property `CurlClient::$verifyPeer` was left uninitialized, defaulting to null, which cURL interprets as falsy and therefore disables peer certificate verification. A successful attacker can observe authentication material and exchanged threat intelligence, and inject falsified data into MISP's responses from remote services. No public exploit has been identified; SSVC rates exploitation as none at time of analysis.

Cross-tenant vault key disclosure in Helicone's AI proxy and observability platform exposes plaintext upstream provider credentials - including OpenAI, Anthropic, and AWS Bedrock API keys - to any authenticated admin or owner of a separate tenant organization. The vulnerability exists in VaultManager.getDecryptedProviderKeyById(), invoked via GET /v1/vault/key/{providerKeyId}, which decrypts and returns vault secrets without verifying that the requesting user's organization matches the organization that owns the target key. A vendor patch commit is available; no active exploitation or public proof-of-concept has been identified at time of analysis.

Predictable HMAC shared secrets generated by the API Publisher component of WSO2 API Manager allow a sophisticated attacker to forecast future webhook signing secrets and forge event payloads that the API Gateway accepts as authentic. All supported release lines are affected — API Manager 4.1.0, 4.2.0, 4.3.0, 4.4.0 and 4.5.0, plus API Control Plane 4.5.0 — with fixes shipped as vendor update levels (for example 4.4.0.68, 4.3.0.104, 4.5.0.52 and 4.1.0.253). Exploitation is not currently observed: EPSS is only 0.27% (19th percentile), CISA's SSVC rates exploitation as 'none' and automatable as 'no', and no public exploit code has been identified at time of analysis, so the practical risk is driven by the sensitivity of the webhook-integrated downstream systems rather than by mass scanning activity.

TLS private key disclosure in SiYuan <=3.8.1 allows any authenticated user - or any network client on default no-auth-code deployments - to exfiltrate the server's TLS private key (conf/key.pem) and CA private key (conf/ca.key) via a simple POST to /api/file/getFile. The root cause is a dual flaw: the IsForbiddenAbsPath() blocklist covers only conf/conf.json by exact match while leaving sibling key material unprotected, and the getFile handler unconditionally skips the blocklist for RoleAdministrator - a role granted to every authenticated user in v3.8.1. On TLS-enabled, network-exposed instances this enables retrospective decryption of captured HTTPS sessions and forgery of certificates already trusted by clients that imported SiYuan's CA. No public exploit identified at time of analysis; vendor-confirmed fix is available in v3.8.2.

SiYuan's full-text search logging mechanism writes admin API tokens in plaintext to an accessible log file when requests exceed internal timing thresholds, enabling authenticated low-privilege users to escalate to permanent administrative access. All self-hosted SiYuan instances before v3.8.2 are affected; because API tokens are passed as query parameters and the log file is retrievable via the built-in getFile endpoint, the privilege escalation path requires no additional exploitation steps beyond triggering a slow search and reading the file. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog. Vendor-released patch v3.8.2 resolves the issue.

Out-of-bounds memory read in the Linux kernel's DRM HDMI connector subsystem allows a local, low-privileged user to potentially leak up to 32 bytes of adjacent kernel heap memory or trigger a page fault leading to kernel crash. The flaw exists in a helper function that copies audio infoframe data using the destination buffer size (60 bytes) rather than the source structure size (28 bytes), reading 32 bytes beyond the source allocation. No public exploit code exists, and EPSS sits at the 10th percentile; however, the availability impact is real - the overread can cross a page boundary and cause an access violation.

Uninitialized heap memory disclosure in FreeRDP 3.0.0-3.30.0 exposes up to 576 bytes of stale server or proxy heap contents - potentially including cleartext credentials from prior RDP sessions - to any authenticated downstream RDP client. Three PDU-serialization functions in libfreerdp/core/info.c advance the stream write pointer with Stream_Seek over reserved padding bytes instead of zeroing them with Stream_Zero, leaving prior malloc heap contents in Save Session Info PDUs transmitted to clients. FreeRDP-based server deployments and freerdp-proxy instances are the affected roles; a vendor-confirmed fix ships in version 3.31.0, and no public exploit or active exploitation has been identified at time of analysis.

HTTPX2's SOCKS5 proxy implementation omits TLS negotiation for WebSocket Secure (wss://) origins, exposing the full WebSocket session - opening handshake, query parameters, Authorization headers, cookies, and message frames - in plaintext to anyone who can observe or control the proxy path. Affected are applications using Client.websocket() or AsyncClient.websocket() in HTTPX2 versions 2.6.0 through 2.9.1 when routing through a SOCKS5 proxy. An adjacent-network attacker can passively eavesdrop on or actively modify traffic, and can impersonate the WebSocket server due to the missing certificate verification step. No public exploit code has been identified at time of analysis and this CVE does not appear in the CISA KEV catalog.

Verification bypass in prevail eBPF verifier versions before 0.2.4 allows any caller with eBPF program submission access - including unprivileged users on BPF-enabled kernels - to load programs that incorrectly pass safety checks but destroy the upper 32 bits of kernel pointer registers at runtime via ALU32 ADD and SUB instructions. The runtime effect is either a program fault (availability impact) or exposure of the lower 32 bits of a kernel pointer as a leakable scalar, partially defeating kernel ASLR. A vendor patch is available at v0.2.4; no active exploitation or public exploit code has been identified at time of analysis.

Verifier bypass in PREVAIL (vbpf/prevail), the polynomial-runtime eBPF static verifier, before version 0.2.4 lets an attacker get an unsafe eBPF program accepted as safe. The abstract transformer treats stores through a context-typed (T_CTX) base register as a silent no-op, so a program can overwrite a context pointer field such as ctx->data, reload it typed as a packet pointer (T_PACKET), and dereference an attacker-controlled address while prevail still reports PASS, enabling out-of-bounds memory access. Fixed in 0.2.4; no public exploit identified at time of analysis beyond the maintainer's regression test cases, which concretely demonstrate the bypass shape.

Unauthenticated sensitive data exposure in dotstore's WooCommerce Product Attachment plugin (versions <= 2.3.3) allows remote, unauthenticated attackers to retrieve product attachment files that should be access-controlled. The vulnerability stems from insufficient authorization checks on attachment retrieval endpoints, classified under CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere). No active exploitation has been confirmed by CISA KEV, and no public exploit code is identified at time of analysis, but the low attack complexity and zero-authentication requirement make opportunistic access trivial for any network-reachable attacker.

Certificate validation bypass in libcurl (curl 8.9.1 through 8.21.0) with the wolfSSL TLS backend allows a network-positioned attacker to intercept encrypted communications by exploiting a post-callback CA store reinstatement bug. When an application uses CURLOPT_SSL_CTX_FUNCTION to install a custom trust store at connection time, libcurl silently overwrites that callback-selected store with the previously cached CA bundle, causing certificates that the callback explicitly rejected to be accepted without error. EPSS is 0.13% (3rd percentile) and no active exploitation is confirmed, but exploitation against a susceptible deployment is conceptually straightforward for a MITM-positioned adversary with a suitable certificate.

Secure-flag stripping in curl 8.13.0 through 8.21.0 allows a server to cause curl to transmit session cookies over unencrypted HTTP by returning a Set-Cookie header that places a horizontal tab character (ASCII 9) instead of a space immediately before the Secure attribute. curl's cookie parser fails to recognise the attribute under this condition, stores the cookie without its Secure constraint, and subsequently includes it in plaintext HTTP requests to the same host. No public exploit code has been identified and EPSS probability is 0.22% (12th percentile), reflecting low observed exploitation activity despite the straightforward triggering mechanism.

Cross-user session confusion in libcurl allows one user's HTTP request to be silently transmitted over another user's previously authenticated Negotiate (SPNEGO/Kerberos) connection. When an initial request to a host is made with empty credentials, libcurl incorrectly treats the resulting connection as eligible for reuse, so a subsequent request from a different principal inherits the earlier authenticated context. There is no public exploit identified at time of analysis; EPSS is low (0.26%, 17th percentile), and the flaw is only meaningful in multi-user or proxy-style deployments that share a single libcurl handle/connection pool.

curl and libcurl through version 8.21.0 incorrectly handle domain-scoped cookies for Public Suffix List (PSL) domains, permitting a malicious server to set cookies scoped to a PSL entry rather than rejecting them as standards require. This flaw enables cross-subdomain cookie propagation under shared public suffix registries (e.g., github.io, co.uk), potentially exposing session tokens or enabling session fixation against other services the victim connects to under the same PSL domain. No public exploit code exists and CISA KEV listing is absent; the vulnerability was fixed in curl 8.22.0 released September 2, 2026.

Use-after-free in libcurl's HTTP/2 Server Push handling affects applications that enable server push while sharing connections across easy handles via the curl share interface. A malicious or compromised HTTP/2 server can trigger the freed-then-reused memory during connection cleanup, leading to memory corruption, crashes, and potential integrity impact against any of the vast range of software that embeds libcurl. EPSS is low (0.21%, 11th percentile) and there is a referenced HackerOne report (#3916059) but no public exploit code and no CISA KEV listing; no public exploit identified at time of analysis.

Privilege escalation in FeatherPanel before v1.3.7.10 permits any authenticated subuser to rewrite their own permission record via the `SubuserController::updateSubuser` handler, immediately gaining full server control. The root cause (CWE-862 Missing Authorization) is confirmed by the fix commit, which adds `USER_UPDATE` permission enforcement, a self-modification block, and whitelist validation of permission names - none of which existed in the vulnerable code path. No public exploit code has been independently confirmed, but the VulnCheck advisory and commit diff together provide sufficient technical detail to reconstruct the attack.

Out-of-bounds read in ION-DTN's decodeSdnv() function before version 4.2.0 allows unauthenticated remote attackers to trigger reads up to nine bytes past buffer boundaries by sending a UDP datagram with a truncated SDNV to the LTP link service input port. The unbounded design of the original function - which consumed octets until finding one with a clear high-order bit - made it exploitable whenever all bytes in a truncated input retained the high-order bit set, simultaneously causing byte counter underflow. No public exploit has been identified at time of analysis; a vendor-released patch is available as ION-DTN 4.2.0.

UNION-based SQL injection in AVideo through version 29.0 allows unauthenticated remote attackers to read arbitrary database contents via the User_Location plugin's regions.json.php and cities.json.php endpoints. The country and region GET parameters are passed unsanitized into SQL queries without prepared statement binding, enabling direct extraction of password hashes and sensitive configuration data from the underlying database. No public exploit has been identified at time of analysis, but the UNION-based technique is elementary and well within reach of automated scanning tooling.

Heap memory disclosure in Mozilla Thunderbird's IMAP client allows a malicious IMAP server to trigger a use-after-free by sending a crafted ID extension response, leaking heap contents that are subsequently persisted to the user's prefs.js file on disk. All Thunderbird releases prior to 155, 140.15 (ESR), and 153.2 across three active release channels are affected. No public exploit or active exploitation has been identified at time of analysis; the EPSS score of 0.15% (4th percentile) reflects low current exploitation probability.

Use of uninitialized memory in Mozilla Thunderbird's MIME parser allows a remote attacker who sends a specially crafted email to trigger an error condition in certain MIME bodies, causing the client to read uninitialized memory. Depending on what previously occupied that memory, this can leak sensitive process data or crash the application. The flaw was fixed in Thunderbird 155, 140.15 ESR, and 153.2; no public exploit has been identified and EPSS exploitation probability is low (0.15%, 4th percentile).

Scrapy's S3DownloadHandler transmitted s3:// requests - including signed AWS Authorization headers, temporary session tokens, and full S3 object contents - over plaintext HTTP by default in all versions prior to 2.17.0, exposing credentials and data to any network attacker with a man-in-the-middle position. A passive observer on the network path can harvest AWS credentials silently; an active attacker can modify S3 response bodies, status codes, and headers to poison scraped data exports, corrupt HTTP caches, or manipulate subsequent crawl targets through forged redirects. The root cause is a logic inversion in a single line of s3.py: HTTPS was opt-in rather than opt-out. No public exploit has been identified at time of analysis, and a patched release (2.17.0) is confirmed available.

Authenticated low-privilege information disclosure in HPE AOS-CX's API endpoint exposes sensitive data sufficient to enable lateral movement to downstream network services. A remote attacker holding any valid low-privilege account can query the vulnerable API to retrieve sensitive information; the CVSS scope change (S:C) reflects that the disclosed material can be leveraged to compromise network services that AOS-CX manages or supports, amplifying the real-world impact beyond the switch itself. No public exploit has been identified and this vulnerability is not listed in CISA KEV at time of analysis.

Broken access control in HPE Networking Fabric Composer's API allows authenticated low-privilege operator users to read data beyond their authorized scope, potentially enabling lateral movement or privilege escalation within the management plane. The vulnerability is network-exploitable with low attack complexity once a valid operator credential is obtained, as reflected by the CVSS 7.6 score (AV:N/AC:L/PR:L). No public exploit code or CISA KEV listing has been identified at time of analysis.

Arbitrary file write via the HPE Networking Fabric Composer API allows an authenticated low-privilege operator to escalate privileges and execute arbitrary commands on the underlying operating system, resulting in complete system compromise. The CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N) reflects network-exploitable, low-complexity exploitation requiring only a valid operator account. No public exploit code or CISA KEV listing has been identified at time of analysis, but the clear privilege escalation path from a low-privilege role to OS-level access makes this a high-priority remediation target in any Fabric Composer deployment.

Missing authorization in Elasticsearch's custom inference service allows a low-privileged user holding only inference execution rights to redirect outbound inference traffic to an attacker-controlled endpoint, causing administrator-provisioned credentials to leak to that destination. Affected across the 8.x and 9.x branches (Elasticsearch 8.0.0 through 8.19.18, 9.0.0 through 9.3.7, 9.4.0 through 9.4.3, and 9.5.0), this is a privilege-abuse path where an underprivileged internal user effectively hijacks admin-level secrets without requiring elevated permissions. No public exploit or active exploitation has been identified; EPSS sits at 0.17% and SSVC rates technical impact as partial.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low privileges to achieve arbitrary code execution, data tampering, and information disclosure on the affected host. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N, C:H/I:H/A:H) indicates a local, low-complexity exploit path yielding full triad compromise - consistent with classic unsafe deserialization primitives that reconstruct attacker-controlled object graphs. No public exploit or CISA KEV listing has been identified at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low privileges to achieve arbitrary code execution, tamper with data, and disclose sensitive information. The vulnerability (CWE-502) exists in the Megatron Bridge component of NVIDIA's large-scale model training infrastructure, where attacker-controlled serialized input is processed without adequate validation. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low-privilege access to achieve code execution, data tampering, and information disclosure on the host system. The vulnerability (CWE-502) is exploitable locally without user interaction, making it particularly relevant in multi-tenant high-performance compute environments where Megatron Bridge is used for large-scale model training pipelines. No public exploit code or active exploitation has been identified at time of analysis, but the full C/I/A impact triad elevates the urgency for affected deployments.

Local code execution in NVIDIA Megatron Bridge exploits unsafe deserialization of attacker-controlled data, allowing a low-privileged local user to achieve full process compromise with high confidentiality, integrity, and availability impact. The CVSS 7.8 (High) vector - AV:L/AC:L/PR:L/UI:N - confirms that no network exposure, user interaction, or elevated privileges are required beyond an initial local foothold. No public exploit code and no CISA KEV listing have been identified at time of analysis, but the RCE-capable impact class warrants prompt remediation in multi-user AI training environments.

Deserialization of untrusted data in NVIDIA Megatron Bridge exposes affected systems to code execution, data tampering, and information disclosure by a local low-privileged attacker. The flaw (CWE-502) allows a maliciously crafted serialized object to hijack the application's deserialization routine, granting the attacker the full CIA impact of the process context without requiring elevated privileges or user interaction. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in CISA KEV; however, the high CIA impact and low attack complexity make this a meaningful priority for any organization running Megatron Bridge in multi-tenant or shared compute environments.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a low-privileged local user to achieve arbitrary code execution, data tampering, and information disclosure on the affected host. Reported directly by NVIDIA PSIRT (psirt@nvidia.com) and classified CWE-502, the flaw requires only local system access with standard user privileges, elevating insider threat and lateral-movement risk in shared AI training environments. No public exploit code or active exploitation has been confirmed at time of analysis, but the low attack complexity and full C/I/A impact make patching a real operational priority for any deployment.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low privileges to achieve arbitrary code execution, data tampering, and information disclosure on affected systems. The CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects full CIA impact from a local, low-complexity attack requiring no user interaction, making this a meaningful privilege escalation and code execution risk in shared compute environments such as multi-tenant GPU training clusters. No public exploit code or CISA KEV listing has been identified at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge enables a local low-privileged attacker to achieve code execution, corrupt data, and exfiltrate sensitive information. The vulnerability (CWE-502) is exploitable locally with low privileges and no user interaction, yielding a CVSS 7.8 High rating with full confidentiality, integrity, and availability impact. No public exploit code has been identified at the time of analysis, and CISA has not added this to the Known Exploited Vulnerabilities catalog.

Deserialization of untrusted data in NVIDIA Megatron Bridge exposes local users to code execution, data tampering, and information disclosure. An attacker with low-privileged local access can supply crafted serialized payloads to the Bridge component, which are deserialized without adequate validation. No public exploit code or active exploitation has been identified at time of analysis, but the high C/I/A impact and low-complexity exploitation path make this a meaningful risk in multi-tenant AI training environments.

Deserialization of untrusted data in NVIDIA Megatron Bridge exposes systems to local code execution, data tampering, and information disclosure from a low-privileged local user. The vulnerability (CWE-502) allows an attacker with local access to supply malicious serialized payloads that the bridge processes without sufficient validation. No public exploit or CISA KEV listing is identified at time of analysis, but the full-triad high-impact CVSS score (C:H/I:H/A:H) signals severe post-exploitation potential on any host running the component.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low privileges to achieve code execution, data tampering, and information disclosure on the host system. The CVSS:3.1 vector (AV:L/PR:L) confirms this is a local-access vulnerability targeting NVIDIA's distributed large-model training infrastructure, where a compromised or malicious low-privileged user on the same host could supply a crafted serialized payload to the Bridge component. No public exploit or CISA KEV listing has been identified at time of analysis, but the full-triad impact (C:H/I:H/A:H) makes this a meaningful threat in multi-tenant AI training cluster environments.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low privileges to achieve full system compromise, including arbitrary code execution, data tampering, and information disclosure. The CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N) confirms that exploitation requires local access with minimal privilege but no user interaction, making it a realistic threat in multi-tenant AI training environments where Megatron Bridge is used. No public exploit code or CISA KEV listing has been identified at the time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local low-privileged attacker to achieve arbitrary code execution, tamper with data, and disclose sensitive information on the affected host. The CVSS 7.8 score with local attack vector and low-privilege requirement indicates an authenticated local user can exploit the flaw without user interaction, fully compromising confidentiality, integrity, and availability. No public exploit or active exploitation has been identified at time of analysis, though the CIA triad is fully impacted on successful exploitation, making this a meaningful risk in shared compute environments.

Deserialization of untrusted data in NVIDIA Megatron Bridge enables a local low-privileged attacker to achieve code execution, data tampering, and information disclosure with no user interaction required. The AV:L/PR:L CVSS vector confines the attack to actors who already hold a valid local account on the affected host, limiting but not eliminating real-world risk in shared AI infrastructure. No public exploit code has been identified, and this vulnerability has not been listed in CISA's Known Exploited Vulnerabilities catalog at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local low-privileged attacker to achieve code execution, data tampering, and information disclosure on the affected system. The CVSS vector (AV:L/PR:L) confirms exploitation requires local access with standard user privileges, making this most relevant to shared multi-user HPC or AI/ML training cluster environments where multiple users interact with the same Megatron infrastructure. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a low-privileged local attacker to achieve arbitrary code execution, data tampering, and information disclosure on affected systems. The flaw (CWE-502) requires only an authenticated local OS session - no elevated privileges or user interaction - making it exploitable by any standard user on a host running the Bridge component. Reported directly by NVIDIA PSIRT, no public exploit has been identified at the time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low-level privileges to achieve code execution, data tampering, and information disclosure on the affected system. The CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H vector indicates exploitation requires only local, low-privileged access with no user interaction, making this a meaningful threat in multi-tenant AI training environments where shared compute access is common. No public exploit code or active exploitation via CISA KEV has been identified at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low privileges to execute arbitrary code, tamper with data, and disclose sensitive information on affected systems. The vulnerability stems from CWE-502 (Deserialization of Untrusted Data), where a crafted malicious payload supplied to the Bridge component triggers unsafe deserialization, granting the attacker full control over the vulnerable process. No public exploit or CISA KEV listing has been identified at time of analysis, but the high-impact CVSS 7.8 score reflects the severity of successful exploitation.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local low-privileged attacker to achieve code execution, tamper with data, and disclose sensitive information on the affected host. The CVSS:3.1 score of 7.8 (High) with a local attack vector reflects that exploitation requires an existing foothold on the system, but the low privilege requirement and no user interaction needed make post-access exploitation straightforward. No public exploit code or CISA KEV listing has been identified at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge exposes systems to code execution, data tampering, and information disclosure when an attacker with local user access supplies a malicious serialized payload to the Bridge process. The local attack vector (AV:L) and low-privilege requirement (PR:L) place this vulnerability in the context of shared AI/ML training infrastructure - multi-tenant GPU clusters where lateral movement between users is the realistic threat model. No public exploit code has been identified and the vulnerability is absent from the CISA KEV catalog at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge enables a local low-privileged attacker to achieve code execution, data tampering, and information disclosure on the affected host. The CVSS 7.8 score (AV:L/PR:L) constrains exploitation to local contexts, but the high impact across all three CIA triad components reflects the severity of a successful exploit. No public exploit code and no CISA KEV listing have been identified at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low privileges to achieve arbitrary code execution, tamper with data, and disclose sensitive information on affected systems. Rooted in CWE-502, the flaw arises when the bridge component deserializes attacker-influenced data without adequate validation - a well-understood attack class that is particularly dangerous in distributed AI training infrastructure where serialized model state or inter-process messages transit between components. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge exposes AI training infrastructure to code execution, data tampering, and information disclosure by local low-privileged attackers. The vulnerability (CWE-502) resides in a bridge component of the Megatron-LM distributed training framework, used extensively in large-scale LLM training clusters. No public exploit code or CISA KEV listing has been identified at time of analysis; however, CVSS 7.8 (High) reflects the severity of a full triad (C:H/I:H/A:H) impact if exploitation succeeds.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker holding standard user privileges to achieve arbitrary code execution, data tampering, and information disclosure on the affected host. The CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms the exploitation path is local and low-privilege - no network exposure or administrator rights are required, making insider threats, shared-access HPC environments, and compromised user accounts the primary risk vectors. No public exploit code or active exploitation has been identified at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local, low-privileged attacker to achieve code execution, data tampering, and information disclosure on the affected host. The vulnerability (CWE-502) stems from the application accepting and processing serialized data without adequate validation, enabling crafted payloads to subvert normal deserialization logic. No public exploit code or CISA KEV listing has been identified at time of analysis, but the full C:H/I:H/A:H impact triad indicates a severe outcome if exploited by a user with existing local access.

Deserialization of untrusted data in NVIDIA Megatron Bridge allows a local attacker with low-privilege access to execute arbitrary code, tamper with data, and disclose sensitive information. The CVSS vector (AV:L/AC:L/PR:L) indicates the vulnerability is exploitable locally without elevated privileges or user interaction, making it a significant risk in multi-tenant distributed AI training environments where multiple users share infrastructure. No public exploit or KEV listing is confirmed at time of analysis.

Deserialization of untrusted data in NVIDIA Megatron Bridge enables a local, low-privileged attacker to achieve code execution, data tampering, and information disclosure on the affected host. The vulnerability carries a CVSS 3.1 score of 7.8 with a local attack vector, indicating that an attacker with an existing foothold on the system can escalate impact significantly. No public exploit code or CISA KEV listing has been identified at time of analysis, but the full CIA triad impact (High/High/High) makes this a high-priority remediation target for any organization running Megatron Bridge in research or production AI training environments.