Information Disclosure
Monthly
Information disclosure in Google Chrome's DevTools (versions prior to 152.0.7977.65) lets a remote attacker who convinces a user to install a crafted Chrome extension read adjacent memory inside the renderer sandbox via an off-by-one error. Chromium rates the security severity as Low, and there is no public exploit identified at time of analysis; SSVC lists exploitation status as none and EPSS is negligible (0.16%, 6th percentile).
Type confusion in Chrome's V8 JavaScript engine exposes memory contents within the browser sandbox to remote attackers who can socially engineer victims into visiting a crafted HTML page. All Chrome desktop releases prior to 152.0.7977.65 are affected, confirmed by the Chrome Stable Channel advisory linked in references. Despite the vendor-assigned CVSS 8.8, Chromium's own security team rated this 'Low' severity - reflecting the sandboxed scope of the memory disclosure and the required social engineering step - and EPSS probability stands at only 0.26% (18th percentile) with no CISA KEV listing, consistent with SSVC 'Exploitation: none'.
Out-of-bounds read in Google Chrome's ANGLE graphics engine on Windows prior to version 152.0.7977.65 enables remote attackers to potentially execute arbitrary code outside the browser sandbox. Exploitation requires no authentication and only that a victim navigate to a crafted HTML page, yielding a CVSS 8.8 score with high impact across confidentiality, integrity, and availability. A vendor-released patch is available; no public exploit or confirmed active exploitation has been identified at time of analysis.
Out-of-bounds read in Chrome's Skia graphics library, affecting all versions prior to 152.0.7977.65, allows a remote unauthenticated attacker to leak sandbox-contained memory by delivering a crafted media file to a victim. The CVSS 8.1 score reflects high confidentiality and availability impact, though exploitation is bounded by Chrome's renderer sandbox. No public exploit or CISA KEV listing exists at time of analysis; a vendor patch is available and should be deployed via Chrome's standard update channel.
Improper state validation in Google Chrome's Performance component (all versions prior to 152.0.7977.65) enables remote attackers to read memory contents within the Chrome sandbox by luring a user to a crafted HTML page. The scope is contained to the sandbox (S:U), limiting blast radius to in-process data, but sensitive browser state such as cookies, session tokens, or page content may be exposed. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS of 0.22% (13th percentile) corroborates low observed exploitation activity.
Out-of-bounds read in Chrome's ANGLE graphics component (Windows builds prior to 152.0.7977.65) lets a remote attacker escape the renderer sandbox and potentially run arbitrary code after a victim opens a crafted HTML page. Google rates the Chromium severity High, and the CVSS is 9.6 driven by the sandbox-escape scope change; there is no public exploit identified at time of analysis and EPSS is low (0.42%).
DNS rebinding in genieacs-mcp's Streamable HTTP transport (versions <= 0.3.1) allows a malicious website to route browser requests through loopback to the unauthenticated /mcp listener and invoke arbitrary GenieACS NBI operations against managed CPE devices. Affected deployments expose full read/write access to TR-069 device state - including firmware update tasks, parameter changes, device reboots, presets, and connection requests - to any attacker who can lure the server operator to a malicious web page. A proof-of-concept is documented in the GitHub security advisory (GHSA-cmwv-wf9p-p8wx); no CISA KEV listing is present, indicating targeted rather than widespread exploitation at time of analysis.
Out-of-bounds pointer arithmetic in OpenEXR's TypedDeepImageChannel::row() - and parallel methods in FlatImageChannel and SampleCountChannel - affects all releases before 3.2.11, 3.3.13, and 3.4.14, exposing applications that process deep EXR files with nonzero dataWindow origins to deterministic crash or limited heap memory disclosure. The CVSS 7.1 score (AV:N/AC:L/PR:N/UI:R) reflects unauthenticated, low-complexity delivery of a crafted image file requiring only that a user or pipeline opens it, with high availability impact and limited confidentiality exposure. No CISA KEV listing and no public exploit code have been identified at time of analysis; patched releases are available from the Academy Software Foundation.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a victim opens a specially crafted VI (Virtual Instrument) file. The root cause is CWE-787 (Out-of-bounds Write), indicating a write operation beyond the bounds of an allocated buffer during VI file parsing. No public exploit code or active exploitation has been identified at time of analysis, but the file-borne delivery model is realistic in engineering and research environments where LabVIEW projects are routinely shared.
Heap out-of-bounds read in OpenEXRUtil's deep and flat image channel row() API allows an attacker supplying a crafted EXR file with a non-zero dataWindow origin to crash any application that processes the file, with conditional heap memory disclosure dependent on attacker-controlled heap layout. Affected are OpenEXRUtil versions 3.3.0-3.3.12 and 3.4.0-3.4.12; the flaw exists across three channel header implementations (ImfDeepImageChannel.h, ImfFlatImageChannel.h, ImfSampleCountChannel.h). No public exploit identified at time of analysis, and patched releases 3.3.13 and 3.4.13 are available.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The root cause is an out-of-bounds read (CWE-125) that, combined with tags indicating buffer overflow behavior, can corrupt memory state sufficient to achieve code execution. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.5 reflects the high impact potential once a victim opens a malicious VI file.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Rooted in CWE-125 (Out-of-bounds Read), the parser reads beyond allocated buffer boundaries, which can expose adjacent memory or - under favorable heap conditions - enable full code execution. No public exploit or CISA KEV listing has been identified at time of analysis, though the RCE potential and broad LabVIEW user base warrant prioritized patching.
Memory corruption in NI LabVIEW (all versions through 26.3.0) enables information disclosure or arbitrary code execution when a user opens a specially crafted VI (Virtual Instrument) file. The CVSS 4.0 base score of 8.5 reflects high impact across confidentiality, integrity, and availability on the vulnerable system, with local file-based delivery requiring passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE potential and industrial control / engineering deployment context warrant prompt patching.
Memory corruption in NI LabVIEW 26.3.0 and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Classified under CWE-125 (Out-of-bounds Read), the flaw's buffer-overflow and RCE tags suggest that the out-of-bounds read condition can, under certain memory layout circumstances, corrupt control-flow data and escalate beyond information disclosure to full code execution. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog at time of analysis; NI has published a vendor security advisory.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The CWE-787 out-of-bounds write root cause combined with the high-impact CVSS 4.0 score of 8.5 places this in a serious tier for LabVIEW deployments across engineering, scientific, and industrial automation environments. No public exploit code has been identified at time of analysis, but the user-interaction trigger (social engineering via malicious VI file) is a well-understood threat model for desktop engineering tools.
Remote code execution with root privileges is achievable against OpenRGB server instances by sending unauthenticated TCP messages to port 6742, exploiting the UPDATEMODE and SAVE_PROFILE message handlers in combination. The OpenRGB server daemon, deployed as a systemd service in openSUSE Tumbleweed with full root privileges and listening on all interfaces (0.0.0.0:6742), enforces zero authentication or authorization on its custom binary protocol, allowing any network-reachable attacker to drive the exploit chain to full system compromise. A Python reproducer script demonstrating the attack was publicly released alongside the oss-security disclosure on August 25, 2026; publicly available exploit code exists.
Remote unauthenticated arbitrary file overwrite in OpenRGB's custom TCP network protocol (port 6742) allows any network-reachable attacker to overwrite arbitrary files on the host by sending a crafted SAVE_PROFILE message with an attacker-controlled file path. When the daemon is deployed as a systemd service running with full root privileges - as packaged in openSUSE Tumbleweed - this file overwrite primitive translates directly into trivial full remote system compromise. A researcher-published Python reproducer script was released alongside this advisory; upstream release 1.0rc3-hotfix partially addresses the most critical issues.
Local file disclosure in the Kaltura HTML5 player's mwEmbedLoader.php endpoint allows unauthenticated remote attackers to read arbitrary files from the server's filesystem. The root cause is that the ServiceUrl parameter - used as a base URL for backend requests - accepts non-HTTP URI schemes including file://, which the server then fetches; when an exception is raised, the raw deserialized response is reflected back to the client in the error message, leaking file contents. Affected releases span html5lib v2.45, v2.103, and earlier v2.x versions; no public exploit or KEV listing has been identified at time of analysis, though the attack path is straightforward for any attacker with access to the exposed endpoint.
Credential leakage in the urllib Node.js HTTP client (npm package node-modules/urllib) allows attacker-controlled redirect targets to capture sensitive authentication headers sent by the victim application. Versions through 4.9.0 (v3/v4 branch) and through 2.44.0 (v2 branch) recursively reuse the original caller-supplied options object - including Authorization, Cookie, Proxy-Authorization, x-api-key, x-auth-token, and x-access-token headers - when following redirects to a different origin, violating the WHATWG Fetch specification's cross-origin header-stripping requirement. No public exploit code has been released beyond the proof-of-concept topology described in the GHSA advisory, and no active exploitation has been confirmed by CISA KEV at time of analysis.
Code injection in NVIDIA Unified Fabric Manager Enterprise's plugin management API allows low-privileged, adjacent-network authenticated users to execute arbitrary commands on the UFM host by submitting a specially crafted API request. All current release tracks - GA, LTS 2023, LTS 2024, and LTS 2025 - are confirmed affected per vendor-supplied CPE data. Successful exploitation yields code execution, privilege escalation, and information disclosure on a platform that controls InfiniBand fabric infrastructure, amplifying downstream impact on managed HPC and AI compute clusters. No public exploit code or CISA KEV listing has been identified at time of analysis.
Disabled TLS certificate verification in X-AnyLabeling's model downloader exposes all versions prior to v4.0.0-beta.9 to man-in-the-middle model substitution during HTTPS downloads. Because `ssl._create_unverified_context()` disables both hostname checking and certificate chain validation, a network-positioned attacker can serve arbitrary model files without detection. For configurations using .pth/.pt files - including the shipped SAM2, YOLOE, UPN, and open_vision setups - the application calls `torch.load` without `weights_only=True`, so a substituted file achieves arbitrary code execution on PyTorch releases predating the `weights_only` default change. No public exploit was identified at time of analysis and this vulnerability is not listed in CISA KEV.
NULL pointer dereference in NVIDIA DGX Spark system firmware enables a local privileged attacker to achieve code execution with scope change into other system components. All versions of the DGX Spark firmware are affected per the wildcard CPE, with potential impacts spanning code execution, privilege escalation, denial of service, information disclosure, and data tampering. No public exploit code or CISA KEV listing has been identified at time of analysis.
Out-of-bounds write in NVIDIA DGX Spark system firmware enables a privileged local attacker to corrupt memory and achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. The CVSS scope-change indicator (S:C) is the critical risk amplifier here - successful exploitation can breach the firmware's security boundary and affect components outside it, including potentially the host OS or hypervisor layer. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
Out-of-bounds write in NVIDIA DGX Spark system firmware permits a locally authenticated, highly privileged attacker to corrupt firmware memory in a way that crosses the firmware's isolation boundary into the broader system. Successful exploitation may yield arbitrary code execution, privilege escalation beyond the initial firmware context, denial of service, information disclosure, and data tampering - all stemming from a single CWE-787 write primitive. No public exploit code or CISA KEV listing has been identified at time of analysis, but the scope-changing nature of the CVSS vector (S:C) elevates the potential blast radius significantly for affected AI compute infrastructure.
Cross-site request forgery against the PraisonAI MCP HTTP-stream transport allows unauthenticated remote attackers to execute arbitrary MCP tools on a developer's local machine when a victim visits a malicious webpage. The attack is enabled by a flawed prefix-match origin check (`startswith`) in versions prior to 4.6.58 that accepts `http://localhost.attacker.com` as a valid localhost origin, and is further facilitated by the absence of a default API key and the CORS simple-request mechanism (Content-Type: text/plain) that bypasses browser preflight. The highest-impact consequence is persistent prompt injection: a forged request can write attacker-controlled agent instruction files that the runtime loads on every subsequent agent run. No public exploit is identified at time of analysis; vendor-released patch 4.6.58 is confirmed.
Unsafe dynamic class instantiation in Vocos allows arbitrary code execution when a user loads a model from an attacker-controlled Hugging Face repository. The library's `Vocos.from_pretrained` fetches a remote `config.yaml` from a caller-supplied repository and passes it directly to `instantiate_class`, which imports and calls any Python callable named in the configuration without an allowlist. Any user who loads a Vocos model from a repository they do not fully trust is exposed to full code execution in their Python process. No public exploit has been identified at time of analysis, but the attack path requires minimal sophistication given the direct code path from remote config to `__import__`/`getattr`/call.
Cleartext disclosure of AWS STS session tokens affects rclone before 1.74.4 when its S3 backend follows a redirect that keeps the same host:port but downgrades the scheme from HTTPS to HTTP. The redirect-safety logic added in v1.74.3 (commit e7b1eb774) compares only URL.Host and ignores URL.Scheme, so the X-Amz-Security-Token header is re-sent over the now-plaintext connection, letting any passive observer on the path harvest the temporary credential. Reported by VulnCheck; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Repository migration operations in JFrog Artifactory expose a missing authorization check (CWE-862) that allows any authenticated low-privileged user to initiate migrations against repositories they do not have permission to access or control. Affected instances across all Artifactory versions per the CPE wildcard are subject to information disclosure of restricted artifact contents, unauthorized state changes via migration side-effects, and high-impact service disruption to artifact delivery pipelines. No public exploit code has been identified and this vulnerability is not listed in CISA KEV at time of analysis, though the CVSS 7.6 High rating and PR:L attack vector make it a realistic insider or compromised-credential threat.
SSRF protection bypass in PraisonAI's praisonaiagents library (all versions before 1.6.58) lets low-privileged users route agent web-fetching functions to internal HTTP services by supplying hostnames - such as 127.0.0.1.nip.io - that pass the static IP blocklist in spider_tools._host_is_blocked() because the function never performs DNS resolution before validation. The affected functions scrape_page, extract_links, crawl, and extract_text are registered as default LLM-callable agent tools, so any agent prompted to retrieve a user-supplied URL will trigger this path; a live proof-of-concept is documented in the GitHub Security Advisory (GHSA-x44h-65qv-cw74), confirming that publicly available exploit code exists. The CVSS scope change (S:C) and high confidentiality impact (C:H) reflect real ability to exfiltrate responses from internal services such as cloud metadata endpoints or localhost-bound APIs.
Persistent authentication bypass in Ech0 (lin-snow's self-hosted lightweight publishing/memo app) before 4.7.3 lets an attacker who has stolen a 'never-expire' access token retain valid authenticated access indefinitely. Because such tokens carry no JWT 'exp' claim, all three revocation paths fail - logout panics on the nil ExpiresAt field, RevokeToken short-circuits when remaining TTL is zero, and admin 'Delete token' never blacklists the JTI - so a leaked token stays cryptographically valid until the operator rotates the signing key. No public exploit identified at time of analysis; there is no CISA KEV listing and no POC referenced in the provided intelligence.
JWT signing key replacement in Cloud Foundry UAA allows a remote authenticated attacker holding only the zones.write authority to fully compromise the entire Cloud Foundry deployment. By exploiting a case sensitivity mismatch between the authorization layer (which performs a case-sensitive string comparison against the literal 'uaa' identifier) and the MySQL persistence layer (which resolves identifiers case-insensitively under its default collation), an attacker submitting 'UAA' or 'Uaa' bypasses the privilege check while the database silently resolves the request against the real system zone record. Exploitation enables overwriting the system zone's JWT signing key, forging tokens claiming admin and administrator scopes, and cascading into full UAA and Cloud Foundry compromise; no public exploit has been identified at time of analysis, though the Changed-Scope CVSS vector and PR:H signal a high-severity, low-noise attack path against MySQL-backed deployments.
PHP Object Injection in the Kalles Addons WordPress plugin (all versions up to and including 1.0.6) allows unauthenticated remote attackers to deserialize untrusted PHP objects via a network-accessible deserialization endpoint. Exploitation is strictly conditional: the plugin itself contains no known POP (Property-Oriented Programming) chain, so real-world impact - ranging from arbitrary file deletion and sensitive data retrieval to remote code execution - only materializes when a separately installed plugin or theme on the same WordPress instance supplies a usable POP chain. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Server-Side Template Injection in TYPO3's Event Management and Registration extension allows authenticated backend editors to disclose sensitive application data or execute TypoScript content objects by supplying Fluid ViewHelper syntax in the email subject field. The flaw affects backend users with edit access to the event registration plugin or backend module - an insider-level privilege boundary that limits but does not eliminate risk, particularly in multi-tenant or agency-managed TYPO3 installations. No public exploit code or CISA KEV listing exists at time of analysis, though the CVSS 4.0 score of 7.7 reflects the high potential impact if the precondition is met.
Unauthorized organizer attribution in the TYPO3 Events 2 frontend management extension allows any authenticated organizer-role user to create events falsely attributed to another organizer's record by supplying a foreign organizer identifier in the event creation request. The flaw stems from a permission check that validates only the presence of any organizer role rather than verifying the submitting user's ownership of the specific organizer referenced in the request. No public exploit has been identified and this vulnerability is absent from CISA KEV; however, the CVSS 4.0 score of 7.1 reflects a high integrity impact on the vulnerable system driven by straightforward, low-privilege network exploitation with no additional attack requirements.
SMS authentication bypass in Weidmüller IE-SR-2TX-WL-4G industrial 4G routers allows a remote attacker to permanently disable the SMS password requirement by deliberately submitting five or more invalid passwords, after which the device executes all subsequent SMS management commands without any authentication. The root flaw is in the lockout logic: rather than locking out the attacker, the device disables its own password enforcement mechanism, rewarding brute-force attempts with unrestricted SMS command access. Impacts include limited configuration tampering, limited information leakage, and potentially full loss of device availability; no public exploit code or active exploitation is confirmed at time of analysis.
Local File Inclusion in Edge-Themes' Shuffle WordPress theme (all versions through 1.8) exposes WordPress installations to unauthenticated remote code execution. An attacker without any credentials can supply a crafted path parameter to the theme's PHP include logic, causing the server to load and execute arbitrary PHP files - including attacker-uploaded content disguised as images. No public exploit has been identified at time of analysis, but the attack pattern (LFI chained with WordPress media uploads) is well-documented in the ecosystem, and the unauthenticated network vector warrants prompt remediation.
Local File Inclusion in the Verdure Core WordPress plugin (versions ≤ 1.2) enables unauthenticated remote attackers to include and execute arbitrary PHP files on the server. Rooted in CWE-98 (improper PHP include/require path control), the flaw can be chained with file upload functionality - an attacker uploads a PHP-bearing image or other 'safe' file, then triggers the LFI to execute it - yielding full remote code execution, access control bypass, and sensitive data disclosure. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
The XML import feature in Tuleap Enterprise Edition versions 17.0 through 17.5 assigns default passwords to user accounts created during XML import operations (CWE-1393), exposing those accounts to network-accessible credential guessing with no authentication or user interaction required. Successful exploitation grants an attacker full control of an affected user account, resulting in high confidentiality and integrity impact per the CVSS 7.7 score. No public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV, but the unauthenticated network vector makes this a realistic threat for any organization that has used XML import for bulk user migration.
Local File Inclusion in the Mane WordPress theme (all versions up to and including 1.7) allows unauthenticated remote attackers to include and execute arbitrary server-side PHP files, with a realistic path to full remote code execution when file upload functionality is accessible. The CVSS 8.1 score with AC:H signals that the most severe impact - arbitrary code execution - depends on a specific precondition, most likely an attacker-controlled file already present on the server filesystem. No public exploit has been identified at time of analysis, though the LFI-to-RCE chain on WordPress is a well-understood and widely practiced attack class.
Arbitrary file read in GitPython versions before 3.1.59 exposes sensitive filesystem content to low-privileged network attackers through an incomplete argument-injection guard. The unsafe_git_revision_options denylist in Repo.blame() omits the --contents and -S git options, allowing attackers to supply revision values such as --contents=/etc/passwd and receive the target file's contents embedded in the blame output. No public exploit has been identified at time of analysis, but the bypass is conceptually trivial - a crafted string is all that is required once access to the blame API is established.
GitPython before 3.1.59 discloses local file content through exception messages when parsing .gitmodules files that contain [include] directives, because the library fails to disable the merge_includes feature in GitConfigParser. An attacker who can introduce a malicious .gitmodules into a repository processed by a vulnerable GitPython instance can cause the first line of any locally readable file to appear verbatim in a MissingSectionHeaderError exception when repo.submodules is accessed. No active exploitation has been confirmed (absent from CISA KEV) and no public POC is referenced in available intelligence; a vendor-released patch exists in version 3.1.59.
Information disclosure in Grav CMS before 2.0.16 enables authenticated users holding page-edit permission to retrieve sensitive system configuration values - including Redis passwords and other stored credentials - by invoking `config.get()` or `config.toArray()` within Twig templates. The root cause is an incomplete default denylist in the Twig sandbox configuration that fails to block access to the `config` object when the `config_access` feature is enabled. No public exploit has been identified and the vulnerability is not confirmed actively exploited at time of analysis.
Server-Side Template Injection in the Grav Email plugin (getgrav/grav-plugin-email) before 4.2.2 permits authenticated remote code execution on the host running PHP. Any account holding only api.access and api.pages.write permissions - typical content-editor roles - can embed a Twig payload in the header.form.process.email.body Email action parameter, publish the page, and trigger arbitrary OS command execution by submitting the associated form. No active exploitation has been confirmed by CISA KEV and no public exploit has been identified at time of analysis, but the low privilege bar and well-understood SSTI attack class make this a high-priority remediation target.
Password reset and account activation token comparison in Grav Login Plugin before 3.9.1 uses PHP's non-constant-time === operator instead of hash_equals(), exposing a CWE-208 timing oracle in both taskReset() (classes/Controller.php) and the activation handler (login.php). Combined with the absence of rate limiting on the token-submission endpoint, an unauthenticated network attacker can submit high-volume repeated token guesses against a known username and statistically recover a valid reset token via timing discrepancy. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; the vendor itself characterizes practical exploitability as low, and no end-to-end network exploitation has been demonstrated.
Email address enumeration in the Grav Login plugin (getgrav/grav-plugin-login) before 3.9.1 lets unauthenticated remote attackers determine which email addresses are registered on a Grav CMS site. The register() method returns a distinct EMAIL_NOT_AVAILABLE error for already-registered addresses while proceeding normally otherwise, and because the registration endpoint enforces no rate limiting, an attacker can test addresses at scale, one per request. No public exploit identified at time of analysis; the assigned CVSS 4.0 score of 9.3 appears substantially inflated for what is fundamentally an information-disclosure weakness.
Configuration secret disclosure in Grav CMS before 2.0.16 allows authenticated content editors to extract sensitive values - including cache credentials - from system, site, and theme configuration arrays via the Twig templating engine. The sandboxed Twig render context fails to filter these configuration objects, permitting attackers to bypass the intended config_denied_paths restrictions using standard dot-notation syntax. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 4.0 score of 7.1 reflects a high confidentiality impact for installations where editor access is not fully trusted.
Symlink following in Grav CMS Scheduler's Job::createLockFile() enables local attackers to overwrite arbitrary files writable by the web server process, affecting all versions prior to 2.0.16. The flaw arises because lock files are written to predictable paths inside a world-writable temp directory with no verification that the target path is not an attacker-controlled symlink; the next scheduled job execution blindly writes the job ID string to whatever the symlink points at. No public exploit has been identified at time of analysis, but the predictable path and world-writable directory make the conditions straightforward to stage on shared-hosting or multi-tenant systems.
AEAD authentication bypass in OpenSSL 3.0-4.0 lets attackers forge valid empty-ciphertext/tag pairs when applications encrypt or decrypt via the low-level EVP_Cipher() path with AES-OCB or ChaCha20-Poly1305. A zero-length cipher update was short-circuited to return success without producing or verifying the authentication tag, breaking the integrity guarantee that AEAD is supposed to provide. No public exploit is identified at time of analysis and EPSS is low (0.12%), but the flaw is confirmed and patched by the OpenSSL project and Ubuntu.
Unauthenticated sensitive data exposure in the SiteLeads WordPress plugin (Lead Generation Contact Widget & AI Chatbot) versions 1.2.0 and earlier allows any remote, unauthenticated attacker to retrieve sensitive information from affected WordPress installations. The vulnerability stems from improper protection of sensitive system data (CWE-497), where plugin-stored data - likely including lead contact details, API credentials, or configuration values - is accessible without authentication. No public exploit or CISA KEV listing has been identified at the time of analysis, though the CVSS score of 7.5 (High) reflects the low-effort, network-accessible nature of the attack.
Unauthenticated broken authentication in the WPLegalPages WordPress plugin (versions ≤ 3.7.0) allows remote attackers to bypass access controls on one or more plugin endpoints without any credentials or user interaction, as confirmed by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The vulnerability is classified under CWE-288, meaning an alternate path or channel exists that circumvents the intended authentication gate. No public exploit code and no active exploitation (CISA KEV) have been identified at time of analysis, but the low attack complexity means opportunistic scanning is a realistic threat.
Local File Inclusion in MagicAI for WordPress (versions up to and including 1.4) allows authenticated subscribers to include arbitrary PHP files from the server's filesystem by manipulating user-controlled input that is passed to a PHP file-inclusion function without adequate path validation. With CVSS 8.8 (High) and network-accessible exploitation requiring only subscriber-level authentication, this flaw grants attackers full confidentiality, integrity, and availability impact over the affected WordPress installation. No public exploit or CISA KEV listing has been identified at time of analysis.
Out-of-bounds read in Autodesk 3ds Max's SVG file parser enables crash, sensitive memory disclosure, or arbitrary code execution within the 3ds Max process context when a user opens a maliciously crafted SVG file. Affected releases span 3ds Max 2026 prior to 2026.3.4 and 3ds Max 2027 prior to 2027.2.0, as confirmed by EUVD-2026-65150. EPSS stands at 0.25% (16th percentile) with SSVC exploitation status of 'none,' indicating no current active exploitation; however, the RCE-capable impact triad warrants patching in affected professional environments.
Out-of-bounds read in SpaceDot AcubeSAT On-Board Computer software exposes the spacecraft's CAN bus message handler to denial-of-service attacks. An attacker with access to the CAN bus network can send a crafted PerformFunction message to the OBC, triggering an out-of-bounds read in the CAN::Application::parsePerformFunctionMessage component that crashes the on-board computer. No public exploit identified at time of analysis, and EPSS exploitation probability sits at 0.14% (4th percentile), consistent with a highly specialized embedded aerospace target.
Sensitive credential disclosure in RansomLook (versions 0 through 2.0.0) exposes full API keys in the rendered HTML of the authenticated /admin/apikeys page: although the UI only shows a truncated key, each token is embedded verbatim in hidden form fields backing the enable/disable, private-access, and delete actions. Anyone able to view the admin page source or DOM, or any intermediary that retains HTTP response bodies (debugging proxies, browser caches, monitoring systems), can recover the complete tokens and then authenticate with those keys' privileges, including access to private data. There is no public exploit identified at time of analysis; the issue is fixed upstream by replacing rendered tokens with SHA-256-derived opaque handles.
Dolibarr's Members REST API before version 24.0.0 exposes bcrypt password hash verifiers to any authenticated user holding member-read rights, enabling offline password cracking attacks against member accounts. Both the member list and individual member detail endpoints return the crypted password verifier field because neither the base API serializer nor the Members API class applies field-level filtering to strip credential material from responses. A public proof-of-concept exists; this is not confirmed as actively exploited via CISA KEV, but the low access bar combined with exposed credential hashes and available exploit code makes this a genuine remediation priority for organizations running affected versions.
SQL injection in Dolibarr's users REST API (all versions before 24.0.0) allows authenticated users holding only user-read rights to exfiltrate sensitive database columns - including salary figures and password verifier hashes - that the API is explicitly designed to withhold from normal responses. The injection path targets unsanitized filter parameters concatenated directly into SQL WHERE clauses with no column-level access gating, enabling blind binary search on numeric fields and LIKE prefix iteration on string fields; raw database error messages in the same endpoint additionally leak internal column names. A publicly available exploit writeup documents the full technique (codeant.ai, VulnCheck); no CISA KEV listing is recorded at time of analysis.
Header-filter bypass in the Apache Camel Undertow component (4.11.0-4.14.8, 4.15.0-4.18.3, and 4.19.0-4.21.x) lets remote senders smuggle legacy 'websocket.' dispatch headers across the undertow transport boundary. Because UndertowEndpoint overwrote the UndertowHeaderFilterStrategy with the base HttpHeaderFilterStrategy, undertow-specific filtering never ran on endpoint-configured routes, so an undertow HTTP consumer maps attacker-controlled 'websocket.*' wire headers onto the Exchange and a downstream undertow WebSocket producer can be steered to deliver to a peer other than the one the route selected. No public exploit identified at time of analysis, EPSS is low (0.16%, 5th percentile), and the fix is available from Apache.
Stored cross-site scripting in NethServer's WebTop calendar component (versions 1.5.6 and earlier) permits an authenticated attacker to inject malicious JavaScript into calendar event fields, which silently executes in the browser of any user who subsequently views the poisoned event. The impact scope includes session hijacking, unauthorized access to emails, contacts, and files, and the ability to perform actions as the victim within the platform - all without the victim taking any action beyond viewing the event. No active exploitation or public exploit code has been identified at time of analysis; a vendor-released patch exists in WebTop 1.5.7.
Token exfiltration in Black Duck blackduck-c-cpp 1.0.17 through 3.0.6 allows any actor with code execution inside a scanned project's build to read the Black Duck API token from the process environment inherited by scanning subprocesses. The token - when supplied via BLACKDUCK_API_TOKEN or BD_HUB_TOKEN - is passed in plaintext to child processes spawned during build capture and signature scanning, where it is observable by co-located code. No public exploit has been identified at time of analysis; however, the vendor explicitly warns that upgrading does not remediate prior exposure, making token rotation a mandatory incident-response step for all affected deployments.
Sensitive scraping credentials and bypass logic were exposed to unauthenticated callers through multiple RansomLook API endpoints. Location records associated with monitored ransomware groups and markets were returned verbatim - including the `header` field containing authentication tokens and session cookies, the `init_script` field holding CAPTCHA and anti-bot bypass logic, and `browser` metadata revealing the scraping environment - whenever a location was not explicitly marked private. The patch, confirmed via GitHub commit cc9182930306ff36c7b3424817d49f18df3c85d1, introduces a strict field allowlist and a sanitization function applied across all three affected API routes; no public exploit or KEV listing has been identified at time of analysis.
HCL Hive employs a risky cryptographic primitive (CWE-1240) that creates systemic trust failure across the platform: if any single internal component is compromised, an attacker can exploit the weak cryptographic construction to achieve unauthorized lateral movement or harvest credentials at scale. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) indicates the flaw is reachable over the network without authentication, though high attack complexity caps opportunistic risk. No public exploit code or active exploitation has been identified at time of analysis.
Local File Inclusion in the Måne WordPress theme (versions ≤ 1.7) exposes sites to unauthenticated file inclusion attacks exploitable over the network, classified under CWE-98 (Improper Control of Filename for PHP Include/Require). Attackers can force the theme's PHP code to include arbitrary server-side files, potentially exposing sensitive configuration data or — when chained with a writable server location — achieving remote code execution under the web server's process identity. No public exploit code or CISA KEV active-exploitation listing has been identified at time of analysis, though the vulnerability class is technically well-understood and widely targeted in WordPress ecosystems.
Arbitrary file disclosure in the WP Cafe Pro WordPress plugin (all versions before 3.0.15) lets remote unauthenticated attackers perform Local File Inclusion, reading sensitive server files such as wp-config.php or, in PHP include contexts, potentially executing attacker-controlled code. The flaw is network-reachable with no privileges or user interaction (CVSS 9.8), was reported by Patchstack, and a vendor patch exists in 3.0.15. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Unauthenticated sensitive data exposure in WP Cafe Pro WordPress plugin versions prior to 3.0.15 allows any remote attacker without credentials to retrieve sensitive information directly from affected WordPress installations. Classified under CWE-201 (Insertion of Sensitive Information Into Sent Data), the flaw is network-exploitable with no authentication or user interaction required, yielding a CVSS 3.1 score of 7.5 (High). No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor-released patch is available in version 3.0.15.
Local File Inclusion in the Tonda Core WordPress plugin (all versions prior to 2.6) exposes unauthenticated remote attackers to arbitrary local-file disclosure and, under secondary conditions, potential remote code execution on the host server. Reported by Patchstack and registered under ENISA EUVD-2026-64791, the flaw carries a CVSS 3.1 score of 8.1 with full C/I/A impact and no authentication requirement. A vendor-released patch is available at version 2.6; no confirmed active exploitation or public exploit code has been identified at time of analysis.
Local File Inclusion in the Tonda WordPress theme (versions below 2.6) enables unauthenticated remote attackers to manipulate PHP include statements and read arbitrary files from the server filesystem. The vulnerability is network-exploitable without authentication, but the CVSS AC:H rating indicates exploitation requires specific conditions or input validation bypass rather than trivial mass exploitation. Vendor patch is available at version 2.6; no public exploit or CISA KEV listing has been identified at time of analysis.
Local File Inclusion in the Verdure Core WordPress plugin (versions ≤ 1.2) allows unauthenticated remote attackers to include arbitrary files from the server's filesystem by passing unsanitized input to PHP include/require statements. Successful exploitation can expose sensitive server files such as wp-config.php - disclosing database credentials - and, under certain PHP configurations, may enable remote code execution through log poisoning or PHP wrapper abuse. No public exploit code or CISA KEV listing has been identified at time of analysis, though the unauthenticated attack vector lowers the barrier for opportunistic targeting of vulnerable WordPress installations.
Prototype pollution in exceljs-hardened before 5.0.0 lets a remote attacker corrupt Object.prototype by feeding parsed JSON containing a malicious __proto__ property into a cell note, because the deepMerge helper in the note-serialization path fails to reject __proto__, constructor, or prototype keys. Any application that uses this library to process untrusted spreadsheet or note data is affected, and polluting the global prototype can cascade into denial of service, logic tampering, or code execution via downstream gadgets. No public exploit is identified at time of analysis, and the flaw is not listed in CISA KEV.
OneNav 1.2.4's import_link() function allows any authenticated user to delete arbitrary files on the host system via path traversal, scoring CVSS 8.1 with High integrity and availability impact. Publicly available exploit code exists per SSVC assessment (exploitation: poc), though EPSS probability remains very low at 0.14% (4th percentile), indicating limited widespread exploitation activity. The attack requires only low-privilege authentication over the network with no user interaction, making it accessible to any registered user of an exposed OneNav instance.
PHP Object Injection in PPWP - Password Protect Pages (WordPress plugin, versions up to and including 1.9.18) permits authenticated attackers holding Contributor-level roles or higher to deserialize attacker-controlled data via the 'post_protection_roles' parameter, injecting arbitrary PHP objects into the application. Real-world impact is fully contingent on a Property-Oriented Programming (POP) chain being present in another co-installed plugin or theme - absent that chain, the vulnerability has no exploitable effect, but where one exists, outcomes can include arbitrary file deletion, sensitive data retrieval, or remote code execution. No public exploit code or active exploitation has been identified at time of analysis; however, a Wordfence advisory and a WordPress SVN changeset (3567221) both indicate a fix has been committed.
Insufficient access control granularity in docker-socket-proxy allows adjacent-network attackers without credentials to read arbitrary files and exfiltrate entire container filesystems via four unguarded Docker API endpoints. When the CONTAINERS environment variable is set, the HAProxy-based proxy fails to block /containers/{id}/archive, /containers/{id}/export, /containers/{id}/logs, and /containers/{id}/top, treating namespace-level permission as blanket endpoint permission. No active exploitation or confirmed public exploit code has been identified at time of analysis, though a researcher gist is referenced alongside the upstream fix in PR #183.
Race condition in the Linux kernel's GPIO PCA953x driver allows local low-privileged users on systems with PCA953x I2C GPIO expander hardware to trigger incorrect register reads or writes by exploiting missing mutex coverage in pca953x_irq_bus_sync_unlock(). A prior partial fix protected only the interrupt mask register write but left the direction register read unguarded, permitting concurrent threads to interleave I2C transactions and corrupt GPIO expander state on affected kernel stable branches including 6.1.101-6.2, 6.6.42-6.7, and 6.9.11-6.10. No public exploit has been identified and EPSS exploitation probability is 0.20% at the 10th percentile, consistent with negligible real-world exploitation interest.
Use-after-free in the Linux kernel's sched_ext (extensible BPF scheduler) subsystem allows a local low-privileged attacker to corrupt kernel memory, potentially achieving full confidentiality, integrity, and availability compromise of the affected system. The race condition arises when a sub-scheduler enable fails before being linked into the scheduler hierarchy, yet the full teardown path still executes concurrently against root scheduler disable, causing tasks to be re-homed onto an already-freed scheduler hierarchy. No public exploit or POC has been identified at time of analysis, and EPSS at 0.20% (10th percentile) reflects negligible observed exploitation activity.
A use-after-free in the Linux kernel's NFSv4 client can occur when a FREE_STATEID operation is delayed and the associated 'struct nfs_server' is torn down (for example on unmount) while the operation is still in flight, leaving the RPC referencing freed memory. The fix pins the nfs_server by bumping its refcount for the duration of the FREE_STATEID call. This is a client-side race condition, not a server-facing service bug; no public exploit identified at time of analysis, and EPSS is low (0.22%, 13th percentile).
Use-after-free in the Linux kernel's ovpn (in-kernel OpenVPN data-channel offload) module lets a local privileged attacker corrupt kernel memory by racing peer-management operations. A time-of-check/time-of-use window between ovpn_peer_get_by_id() and acquisition of ovpn->lock allows a peer that was concurrently removed to be re-inserted into the rehash tables, resurrecting a peer userspace believes is gone and leaving embedded hash entries linked to memory later freed via call_rcu. There is no public exploit identified at time of analysis and EPSS is low (0.21%, 11th percentile), consistent with a hard-to-win kernel race rather than a mass-exploitable bug.
Null-pointer dereference and promiscuity counter underflow in the Linux kernel bonding driver's ALB monitor can crash the kernel or permanently pin a network interface in promiscuous mode. The bond_alb_monitor() workqueue function reads primary_is_promisc under RCU, drops that lock, then acquires RTNL - allowing the active slave to be removed or changed in the intervening window, leaving the monitor to act on stale state. Linux systems from kernel 2.6.24 through unpatched stable branches (5.10.x, 5.15.x, 6.1.x, 6.6.x, 6.12.x, 6.18.x, 7.1.x, 7.2) with network bonding explicitly configured in ALB mode are affected. No public exploit identified at time of analysis.
Use-after-free in the Linux kernel's enic driver (Cisco VIC Ethernet NIC) allows a local attacker with low privileges to corrupt kernel heap memory during network device removal. The enic_remove() teardown function fails to cancel or disable the tx_hang_reset work item, creating a race window where a TX watchdog timeout can reschedule enic_tx_hang_reset() to execute after free_netdev() has already released the underlying network device structure. No public exploit exists and EPSS probability is 0.21% (11th percentile), though the kernel use-after-free primitive carries high C/I/A impact if reliably triggered.
Reference count underflow in the Linux kernel amdxdna (AMD XDNA NPU accelerator) driver allows a local low-privileged user to corrupt kernel memory via a double invocation of vm_ops->close() triggered by failed mmap page insertions. Two error paths in amdxdna_insert_pages() incorrectly release the shmem pages_pin_count and backing GEM object reference while the VMA remains live; the kernel's subsequent VMA teardown fires vm_ops->close() a second time, producing a reference count underflow with potential use-after-free consequences and high impact across confidentiality, integrity, and availability. No public exploit has been identified at time of analysis and EPSS is 0.20% (10th percentile), consistent with the niche AMD Ryzen AI hardware requirement limiting real-world exposure.
Privilege escalation in the Linux kernel BPF verifier affects versions from 4.16 through current stable branches due to incomplete pointer state propagation during commuted arithmetic (scalar += pointer) in adjust_ptr_min_max_vals(). Local attackers with BPF program loading privileges can exploit the verifier's failure to copy the full bpf_reg_state structure, potentially bypassing memory safety enforcement and achieving arbitrary kernel memory access. No public exploit has been identified at time of analysis and EPSS is low at 0.22%, but the CVSS score of 7.8 (C:H/I:H/A:H) reflects the severity of kernel-level impact if successfully exploited.
Use-after-free in the Linux kernel's BPF TCP iterator exposes systems running kernel versions from 5.15 onward to local privilege escalation with high impact across confidentiality, integrity, and availability. The race condition in bpf_iter_tcp_established_batch() allows a low-privileged local attacker to hold a reference to a request_sock whose refcount is still zero, corrupting kernel memory when the publishing CPU's refcount_set() subsequently overwrites the saturated value. No public exploit has been identified at time of analysis, and EPSS sits at 0.21% (12th percentile), though the race is described as reproducible within seconds under controlled conditions with tcp_syncookies=0.
Unbounded memory allocation in the Linux kernel's vhost_iotlb subsystem allows availability impact on the host system via exhaustion of kernel memory. The flaw exists in vhost_iotlb_add_range_ctx(), where non-retiring IOTLB tables bypass the configured entry limit and continue allocating entries indefinitely - including via guest-controlled or userspace requests to vhost, mlx5 vDPA, VDUSE, and vhost-vDPA subsystems. No public exploit code has been identified at time of analysis, and EPSS probability is very low (0.20%), but the CVSS scope-change metric (S:C) reflects that a guest workload can impact host kernel availability.
Out-of-bounds kernel memory read in the Linux kernel AF_XDP subsystem allows a local low-privileged user to trigger reads beyond registered memory regions by supplying TX metadata shorter than 16 bytes. Affected systems include Linux kernel versions from the introduction of commit 341ac980eab9 through multiple stable branches, with patches available at 6.12.104, 7.1.9, and 7.2. No public exploit has been identified and EPSS is 0.21% (11th percentile), indicating low current exploitation activity despite the high CVSS score.
Memory corruption in the Linux kernel's AF_XDP socket (xsk) subsystem arises from two related flaws: missing size validation for launch-time metadata fields that extend beyond the first 16 bytes of struct xsk_tx_metadata, and a race condition where user space can modify transmit flags concurrently with kernel transmit processing. A local attacker with low-privilege access who can create and configure AF_XDP sockets may trigger out-of-bounds memory access, leading to high-impact compromise of confidentiality, integrity, and availability consistent with the CVSS 7.8 score. No public exploit code has been identified, EPSS sits at 0.21% (11th percentile), and the CVE is absent from CISA KEV, placing practical exploitation risk well below what the raw CVSS score might suggest.
Use-after-free in the Linux kernel's UDP tunnel GSO segmentation path (__skb_udp_tunnel_segment()) occurs when the code dereferences a saved UDP header pointer after a skb_pull() reallocates skb->head, invalidating that pointer. The flaw affects hosts that software-segment UDP-encapsulated tunnel traffic (VXLAN/GENEVE/FoU), and can lead to a kernel crash or potential information disclosure. No public exploit is identified at time of analysis, EPSS is low (0.22%), and the issue is not on CISA KEV; the upstream fix reorders the header fetch to occur after the pull.
Remote denial of service in the Linux kernel's CAKE traffic scheduler (sch_cake) allows an unauthenticated network attacker to trigger a kernel panic or persistent warning-log flood by sending malformed IP packets to a system with the CAKE qdisc actively configured. Affected systems running Linux 4.19 through unpatched versions of the 7.x series face kernel panic if the non-default `panic_on_warn=1` boot parameter is set, or dmesg flooding otherwise. No public exploit has been identified and this CVE is not in the CISA KEV catalog, but the fix is low-risk and multiple patched stable kernel versions are available.
Kernel panic in Linux kernel's vhost-scsi subsystem can be triggered by a malicious guest VM when T10 Protection Information (PI) is negotiated, crashing the host kernel and all co-hosted virtual machines. A guest sends a malformed SCSI request with protection byte lengths equal to or exceeding the payload, causing an integer underflow or zero-count scatterlist that hits an unconditional BUG_ON assertion in sg_alloc_table_chained(). With EPSS at 0.21% (11th percentile), no CISA KEV listing, and no public proof-of-concept identified at time of analysis, exploitation probability is currently low but the guest-to-host scope change makes this a meaningful availability risk in multi-tenant virtualized storage environments.
The vhost-scsi subsystem in the Linux kernel allows a local attacker with low privileges on a KVM virtualization host to trigger a kernel BUG_ON assertion and crash the host by manipulating VIRTIO feature bits after SCSI endpoint setup. The flaw is that vhost_scsi_set_features() incorrectly accepted changes to VIRTIO_SCSI_F_T10_PI after an active endpoint was established, leaving per-command protection scatterlist arrays (prot_sgl) unallocated while the I/O path proceeded under the updated feature state; when a 129-page protection payload arrives, a BUG_ON(nents > SG_CHUNK_SIZE) fires in sg_pool_index(), panicking the host kernel. Patches are confirmed for stable branches 6.18.45 and 7.1.9 and mainline 7.2; no public exploit exists and no CISA KEV listing is present, with an EPSS of 0.21% (11th percentile).
Kernel BUG triggerable in the Open vSwitch (OVS) net subsystem allows a local low-privileged attacker to crash the kernel or potentially escalate privileges by injecting undersized Ethernet frames through a TUN device. Affected kernels from Linux 4.10 onward trust the user-supplied skb->protocol field on ARPHRD_NONE devices without validating that sufficient linear data exists for Ethernet header parsing, causing __skb_pull() to hit an unconditional BUG halt. No public exploit code has been identified and EPSS probability stands at 0.22% (13th percentile), indicating low opportunistic exploitation risk; however, patches are available across all active stable branches.
Use-after-free in the Linux kernel's traffic control classifier API (net/sched/cls_api) allows a local attacker with CAP_NET_ADMIN to corrupt kernel memory by racing two concurrent tc_new_tfilter() calls targeting the same chain and priority with different classifier types. A proof-of-concept is referenced in the upstream kernel commit but is not independently confirmed as publicly released. EPSS is 0.21% and the vulnerability is not listed in CISA KEV, indicating no observed widespread exploitation at time of analysis.
Data corruption in the Linux kernel bnxt_en driver (Broadcom NetXtreme-E) occurs when TCP Packet Aggregation (TPA) is active alongside PCIe Relaxed Ordering (RO) on AGG rings. When EOP (End-of-frame padding) is used, zero-padding bytes appended at the end of one aggregated segment can spill over and overwrite valid data at the start of the subsequent segment. Older chips (P5 generation and earlier, including the Broadcom 57508) do not automatically suppress RO when EOP is active, making ARM-hosted deployments using these adapters particularly vulnerable to silent data corruption in received network traffic. No public exploit is identified at time of analysis, and EPSS probability is low at 0.21% (12th percentile).
Information disclosure in Google Chrome's DevTools (versions prior to 152.0.7977.65) lets a remote attacker who convinces a user to install a crafted Chrome extension read adjacent memory inside the renderer sandbox via an off-by-one error. Chromium rates the security severity as Low, and there is no public exploit identified at time of analysis; SSVC lists exploitation status as none and EPSS is negligible (0.16%, 6th percentile).
Type confusion in Chrome's V8 JavaScript engine exposes memory contents within the browser sandbox to remote attackers who can socially engineer victims into visiting a crafted HTML page. All Chrome desktop releases prior to 152.0.7977.65 are affected, confirmed by the Chrome Stable Channel advisory linked in references. Despite the vendor-assigned CVSS 8.8, Chromium's own security team rated this 'Low' severity - reflecting the sandboxed scope of the memory disclosure and the required social engineering step - and EPSS probability stands at only 0.26% (18th percentile) with no CISA KEV listing, consistent with SSVC 'Exploitation: none'.
Out-of-bounds read in Google Chrome's ANGLE graphics engine on Windows prior to version 152.0.7977.65 enables remote attackers to potentially execute arbitrary code outside the browser sandbox. Exploitation requires no authentication and only that a victim navigate to a crafted HTML page, yielding a CVSS 8.8 score with high impact across confidentiality, integrity, and availability. A vendor-released patch is available; no public exploit or confirmed active exploitation has been identified at time of analysis.
Out-of-bounds read in Chrome's Skia graphics library, affecting all versions prior to 152.0.7977.65, allows a remote unauthenticated attacker to leak sandbox-contained memory by delivering a crafted media file to a victim. The CVSS 8.1 score reflects high confidentiality and availability impact, though exploitation is bounded by Chrome's renderer sandbox. No public exploit or CISA KEV listing exists at time of analysis; a vendor patch is available and should be deployed via Chrome's standard update channel.
Improper state validation in Google Chrome's Performance component (all versions prior to 152.0.7977.65) enables remote attackers to read memory contents within the Chrome sandbox by luring a user to a crafted HTML page. The scope is contained to the sandbox (S:U), limiting blast radius to in-process data, but sensitive browser state such as cookies, session tokens, or page content may be exposed. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS of 0.22% (13th percentile) corroborates low observed exploitation activity.
Out-of-bounds read in Chrome's ANGLE graphics component (Windows builds prior to 152.0.7977.65) lets a remote attacker escape the renderer sandbox and potentially run arbitrary code after a victim opens a crafted HTML page. Google rates the Chromium severity High, and the CVSS is 9.6 driven by the sandbox-escape scope change; there is no public exploit identified at time of analysis and EPSS is low (0.42%).
DNS rebinding in genieacs-mcp's Streamable HTTP transport (versions <= 0.3.1) allows a malicious website to route browser requests through loopback to the unauthenticated /mcp listener and invoke arbitrary GenieACS NBI operations against managed CPE devices. Affected deployments expose full read/write access to TR-069 device state - including firmware update tasks, parameter changes, device reboots, presets, and connection requests - to any attacker who can lure the server operator to a malicious web page. A proof-of-concept is documented in the GitHub security advisory (GHSA-cmwv-wf9p-p8wx); no CISA KEV listing is present, indicating targeted rather than widespread exploitation at time of analysis.
Out-of-bounds pointer arithmetic in OpenEXR's TypedDeepImageChannel::row() - and parallel methods in FlatImageChannel and SampleCountChannel - affects all releases before 3.2.11, 3.3.13, and 3.4.14, exposing applications that process deep EXR files with nonzero dataWindow origins to deterministic crash or limited heap memory disclosure. The CVSS 7.1 score (AV:N/AC:L/PR:N/UI:R) reflects unauthenticated, low-complexity delivery of a crafted image file requiring only that a user or pipeline opens it, with high availability impact and limited confidentiality exposure. No CISA KEV listing and no public exploit code have been identified at time of analysis; patched releases are available from the Academy Software Foundation.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a victim opens a specially crafted VI (Virtual Instrument) file. The root cause is CWE-787 (Out-of-bounds Write), indicating a write operation beyond the bounds of an allocated buffer during VI file parsing. No public exploit code or active exploitation has been identified at time of analysis, but the file-borne delivery model is realistic in engineering and research environments where LabVIEW projects are routinely shared.
Heap out-of-bounds read in OpenEXRUtil's deep and flat image channel row() API allows an attacker supplying a crafted EXR file with a non-zero dataWindow origin to crash any application that processes the file, with conditional heap memory disclosure dependent on attacker-controlled heap layout. Affected are OpenEXRUtil versions 3.3.0-3.3.12 and 3.4.0-3.4.12; the flaw exists across three channel header implementations (ImfDeepImageChannel.h, ImfFlatImageChannel.h, ImfSampleCountChannel.h). No public exploit identified at time of analysis, and patched releases 3.3.13 and 3.4.13 are available.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The root cause is an out-of-bounds read (CWE-125) that, combined with tags indicating buffer overflow behavior, can corrupt memory state sufficient to achieve code execution. No public exploit or CISA KEV listing has been identified at time of analysis, but the CVSS 4.0 score of 8.5 reflects the high impact potential once a victim opens a malicious VI file.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Rooted in CWE-125 (Out-of-bounds Read), the parser reads beyond allocated buffer boundaries, which can expose adjacent memory or - under favorable heap conditions - enable full code execution. No public exploit or CISA KEV listing has been identified at time of analysis, though the RCE potential and broad LabVIEW user base warrant prioritized patching.
Memory corruption in NI LabVIEW (all versions through 26.3.0) enables information disclosure or arbitrary code execution when a user opens a specially crafted VI (Virtual Instrument) file. The CVSS 4.0 base score of 8.5 reflects high impact across confidentiality, integrity, and availability on the vulnerable system, with local file-based delivery requiring passive user interaction. No public exploit code or CISA KEV listing has been identified at time of analysis, though the RCE potential and industrial control / engineering deployment context warrant prompt patching.
Memory corruption in NI LabVIEW 26.3.0 and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. Classified under CWE-125 (Out-of-bounds Read), the flaw's buffer-overflow and RCE tags suggest that the out-of-bounds read condition can, under certain memory layout circumstances, corrupt control-flow data and escalate beyond information disclosure to full code execution. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog at time of analysis; NI has published a vendor security advisory.
Memory corruption in NI LabVIEW 2026 Q3 (26.3.0) and all prior versions enables information disclosure or arbitrary code execution when a user opens a specially crafted Virtual Instrument (VI) file. The CWE-787 out-of-bounds write root cause combined with the high-impact CVSS 4.0 score of 8.5 places this in a serious tier for LabVIEW deployments across engineering, scientific, and industrial automation environments. No public exploit code has been identified at time of analysis, but the user-interaction trigger (social engineering via malicious VI file) is a well-understood threat model for desktop engineering tools.
Remote code execution with root privileges is achievable against OpenRGB server instances by sending unauthenticated TCP messages to port 6742, exploiting the UPDATEMODE and SAVE_PROFILE message handlers in combination. The OpenRGB server daemon, deployed as a systemd service in openSUSE Tumbleweed with full root privileges and listening on all interfaces (0.0.0.0:6742), enforces zero authentication or authorization on its custom binary protocol, allowing any network-reachable attacker to drive the exploit chain to full system compromise. A Python reproducer script demonstrating the attack was publicly released alongside the oss-security disclosure on August 25, 2026; publicly available exploit code exists.
Remote unauthenticated arbitrary file overwrite in OpenRGB's custom TCP network protocol (port 6742) allows any network-reachable attacker to overwrite arbitrary files on the host by sending a crafted SAVE_PROFILE message with an attacker-controlled file path. When the daemon is deployed as a systemd service running with full root privileges - as packaged in openSUSE Tumbleweed - this file overwrite primitive translates directly into trivial full remote system compromise. A researcher-published Python reproducer script was released alongside this advisory; upstream release 1.0rc3-hotfix partially addresses the most critical issues.
Local file disclosure in the Kaltura HTML5 player's mwEmbedLoader.php endpoint allows unauthenticated remote attackers to read arbitrary files from the server's filesystem. The root cause is that the ServiceUrl parameter - used as a base URL for backend requests - accepts non-HTTP URI schemes including file://, which the server then fetches; when an exception is raised, the raw deserialized response is reflected back to the client in the error message, leaking file contents. Affected releases span html5lib v2.45, v2.103, and earlier v2.x versions; no public exploit or KEV listing has been identified at time of analysis, though the attack path is straightforward for any attacker with access to the exposed endpoint.
Credential leakage in the urllib Node.js HTTP client (npm package node-modules/urllib) allows attacker-controlled redirect targets to capture sensitive authentication headers sent by the victim application. Versions through 4.9.0 (v3/v4 branch) and through 2.44.0 (v2 branch) recursively reuse the original caller-supplied options object - including Authorization, Cookie, Proxy-Authorization, x-api-key, x-auth-token, and x-access-token headers - when following redirects to a different origin, violating the WHATWG Fetch specification's cross-origin header-stripping requirement. No public exploit code has been released beyond the proof-of-concept topology described in the GHSA advisory, and no active exploitation has been confirmed by CISA KEV at time of analysis.
Code injection in NVIDIA Unified Fabric Manager Enterprise's plugin management API allows low-privileged, adjacent-network authenticated users to execute arbitrary commands on the UFM host by submitting a specially crafted API request. All current release tracks - GA, LTS 2023, LTS 2024, and LTS 2025 - are confirmed affected per vendor-supplied CPE data. Successful exploitation yields code execution, privilege escalation, and information disclosure on a platform that controls InfiniBand fabric infrastructure, amplifying downstream impact on managed HPC and AI compute clusters. No public exploit code or CISA KEV listing has been identified at time of analysis.
Disabled TLS certificate verification in X-AnyLabeling's model downloader exposes all versions prior to v4.0.0-beta.9 to man-in-the-middle model substitution during HTTPS downloads. Because `ssl._create_unverified_context()` disables both hostname checking and certificate chain validation, a network-positioned attacker can serve arbitrary model files without detection. For configurations using .pth/.pt files - including the shipped SAM2, YOLOE, UPN, and open_vision setups - the application calls `torch.load` without `weights_only=True`, so a substituted file achieves arbitrary code execution on PyTorch releases predating the `weights_only` default change. No public exploit was identified at time of analysis and this vulnerability is not listed in CISA KEV.
NULL pointer dereference in NVIDIA DGX Spark system firmware enables a local privileged attacker to achieve code execution with scope change into other system components. All versions of the DGX Spark firmware are affected per the wildcard CPE, with potential impacts spanning code execution, privilege escalation, denial of service, information disclosure, and data tampering. No public exploit code or CISA KEV listing has been identified at time of analysis.
Out-of-bounds write in NVIDIA DGX Spark system firmware enables a privileged local attacker to corrupt memory and achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. The CVSS scope-change indicator (S:C) is the critical risk amplifier here - successful exploitation can breach the firmware's security boundary and affect components outside it, including potentially the host OS or hypervisor layer. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog at time of analysis.
Out-of-bounds write in NVIDIA DGX Spark system firmware permits a locally authenticated, highly privileged attacker to corrupt firmware memory in a way that crosses the firmware's isolation boundary into the broader system. Successful exploitation may yield arbitrary code execution, privilege escalation beyond the initial firmware context, denial of service, information disclosure, and data tampering - all stemming from a single CWE-787 write primitive. No public exploit code or CISA KEV listing has been identified at time of analysis, but the scope-changing nature of the CVSS vector (S:C) elevates the potential blast radius significantly for affected AI compute infrastructure.
Cross-site request forgery against the PraisonAI MCP HTTP-stream transport allows unauthenticated remote attackers to execute arbitrary MCP tools on a developer's local machine when a victim visits a malicious webpage. The attack is enabled by a flawed prefix-match origin check (`startswith`) in versions prior to 4.6.58 that accepts `http://localhost.attacker.com` as a valid localhost origin, and is further facilitated by the absence of a default API key and the CORS simple-request mechanism (Content-Type: text/plain) that bypasses browser preflight. The highest-impact consequence is persistent prompt injection: a forged request can write attacker-controlled agent instruction files that the runtime loads on every subsequent agent run. No public exploit is identified at time of analysis; vendor-released patch 4.6.58 is confirmed.
Unsafe dynamic class instantiation in Vocos allows arbitrary code execution when a user loads a model from an attacker-controlled Hugging Face repository. The library's `Vocos.from_pretrained` fetches a remote `config.yaml` from a caller-supplied repository and passes it directly to `instantiate_class`, which imports and calls any Python callable named in the configuration without an allowlist. Any user who loads a Vocos model from a repository they do not fully trust is exposed to full code execution in their Python process. No public exploit has been identified at time of analysis, but the attack path requires minimal sophistication given the direct code path from remote config to `__import__`/`getattr`/call.
Cleartext disclosure of AWS STS session tokens affects rclone before 1.74.4 when its S3 backend follows a redirect that keeps the same host:port but downgrades the scheme from HTTPS to HTTP. The redirect-safety logic added in v1.74.3 (commit e7b1eb774) compares only URL.Host and ignores URL.Scheme, so the X-Amz-Security-Token header is re-sent over the now-plaintext connection, letting any passive observer on the path harvest the temporary credential. Reported by VulnCheck; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Repository migration operations in JFrog Artifactory expose a missing authorization check (CWE-862) that allows any authenticated low-privileged user to initiate migrations against repositories they do not have permission to access or control. Affected instances across all Artifactory versions per the CPE wildcard are subject to information disclosure of restricted artifact contents, unauthorized state changes via migration side-effects, and high-impact service disruption to artifact delivery pipelines. No public exploit code has been identified and this vulnerability is not listed in CISA KEV at time of analysis, though the CVSS 7.6 High rating and PR:L attack vector make it a realistic insider or compromised-credential threat.
SSRF protection bypass in PraisonAI's praisonaiagents library (all versions before 1.6.58) lets low-privileged users route agent web-fetching functions to internal HTTP services by supplying hostnames - such as 127.0.0.1.nip.io - that pass the static IP blocklist in spider_tools._host_is_blocked() because the function never performs DNS resolution before validation. The affected functions scrape_page, extract_links, crawl, and extract_text are registered as default LLM-callable agent tools, so any agent prompted to retrieve a user-supplied URL will trigger this path; a live proof-of-concept is documented in the GitHub Security Advisory (GHSA-x44h-65qv-cw74), confirming that publicly available exploit code exists. The CVSS scope change (S:C) and high confidentiality impact (C:H) reflect real ability to exfiltrate responses from internal services such as cloud metadata endpoints or localhost-bound APIs.
Persistent authentication bypass in Ech0 (lin-snow's self-hosted lightweight publishing/memo app) before 4.7.3 lets an attacker who has stolen a 'never-expire' access token retain valid authenticated access indefinitely. Because such tokens carry no JWT 'exp' claim, all three revocation paths fail - logout panics on the nil ExpiresAt field, RevokeToken short-circuits when remaining TTL is zero, and admin 'Delete token' never blacklists the JTI - so a leaked token stays cryptographically valid until the operator rotates the signing key. No public exploit identified at time of analysis; there is no CISA KEV listing and no POC referenced in the provided intelligence.
JWT signing key replacement in Cloud Foundry UAA allows a remote authenticated attacker holding only the zones.write authority to fully compromise the entire Cloud Foundry deployment. By exploiting a case sensitivity mismatch between the authorization layer (which performs a case-sensitive string comparison against the literal 'uaa' identifier) and the MySQL persistence layer (which resolves identifiers case-insensitively under its default collation), an attacker submitting 'UAA' or 'Uaa' bypasses the privilege check while the database silently resolves the request against the real system zone record. Exploitation enables overwriting the system zone's JWT signing key, forging tokens claiming admin and administrator scopes, and cascading into full UAA and Cloud Foundry compromise; no public exploit has been identified at time of analysis, though the Changed-Scope CVSS vector and PR:H signal a high-severity, low-noise attack path against MySQL-backed deployments.
PHP Object Injection in the Kalles Addons WordPress plugin (all versions up to and including 1.0.6) allows unauthenticated remote attackers to deserialize untrusted PHP objects via a network-accessible deserialization endpoint. Exploitation is strictly conditional: the plugin itself contains no known POP (Property-Oriented Programming) chain, so real-world impact - ranging from arbitrary file deletion and sensitive data retrieval to remote code execution - only materializes when a separately installed plugin or theme on the same WordPress instance supplies a usable POP chain. No public exploit code and no CISA KEV listing have been identified at time of analysis.
Server-Side Template Injection in TYPO3's Event Management and Registration extension allows authenticated backend editors to disclose sensitive application data or execute TypoScript content objects by supplying Fluid ViewHelper syntax in the email subject field. The flaw affects backend users with edit access to the event registration plugin or backend module - an insider-level privilege boundary that limits but does not eliminate risk, particularly in multi-tenant or agency-managed TYPO3 installations. No public exploit code or CISA KEV listing exists at time of analysis, though the CVSS 4.0 score of 7.7 reflects the high potential impact if the precondition is met.
Unauthorized organizer attribution in the TYPO3 Events 2 frontend management extension allows any authenticated organizer-role user to create events falsely attributed to another organizer's record by supplying a foreign organizer identifier in the event creation request. The flaw stems from a permission check that validates only the presence of any organizer role rather than verifying the submitting user's ownership of the specific organizer referenced in the request. No public exploit has been identified and this vulnerability is absent from CISA KEV; however, the CVSS 4.0 score of 7.1 reflects a high integrity impact on the vulnerable system driven by straightforward, low-privilege network exploitation with no additional attack requirements.
SMS authentication bypass in Weidmüller IE-SR-2TX-WL-4G industrial 4G routers allows a remote attacker to permanently disable the SMS password requirement by deliberately submitting five or more invalid passwords, after which the device executes all subsequent SMS management commands without any authentication. The root flaw is in the lockout logic: rather than locking out the attacker, the device disables its own password enforcement mechanism, rewarding brute-force attempts with unrestricted SMS command access. Impacts include limited configuration tampering, limited information leakage, and potentially full loss of device availability; no public exploit code or active exploitation is confirmed at time of analysis.
Local File Inclusion in Edge-Themes' Shuffle WordPress theme (all versions through 1.8) exposes WordPress installations to unauthenticated remote code execution. An attacker without any credentials can supply a crafted path parameter to the theme's PHP include logic, causing the server to load and execute arbitrary PHP files - including attacker-uploaded content disguised as images. No public exploit has been identified at time of analysis, but the attack pattern (LFI chained with WordPress media uploads) is well-documented in the ecosystem, and the unauthenticated network vector warrants prompt remediation.
Local File Inclusion in the Verdure Core WordPress plugin (versions ≤ 1.2) enables unauthenticated remote attackers to include and execute arbitrary PHP files on the server. Rooted in CWE-98 (improper PHP include/require path control), the flaw can be chained with file upload functionality - an attacker uploads a PHP-bearing image or other 'safe' file, then triggers the LFI to execute it - yielding full remote code execution, access control bypass, and sensitive data disclosure. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog.
The XML import feature in Tuleap Enterprise Edition versions 17.0 through 17.5 assigns default passwords to user accounts created during XML import operations (CWE-1393), exposing those accounts to network-accessible credential guessing with no authentication or user interaction required. Successful exploitation grants an attacker full control of an affected user account, resulting in high confidentiality and integrity impact per the CVSS 7.7 score. No public exploit code has been identified at time of analysis and this CVE is not listed in CISA KEV, but the unauthenticated network vector makes this a realistic threat for any organization that has used XML import for bulk user migration.
Local File Inclusion in the Mane WordPress theme (all versions up to and including 1.7) allows unauthenticated remote attackers to include and execute arbitrary server-side PHP files, with a realistic path to full remote code execution when file upload functionality is accessible. The CVSS 8.1 score with AC:H signals that the most severe impact - arbitrary code execution - depends on a specific precondition, most likely an attacker-controlled file already present on the server filesystem. No public exploit has been identified at time of analysis, though the LFI-to-RCE chain on WordPress is a well-understood and widely practiced attack class.
Arbitrary file read in GitPython versions before 3.1.59 exposes sensitive filesystem content to low-privileged network attackers through an incomplete argument-injection guard. The unsafe_git_revision_options denylist in Repo.blame() omits the --contents and -S git options, allowing attackers to supply revision values such as --contents=/etc/passwd and receive the target file's contents embedded in the blame output. No public exploit has been identified at time of analysis, but the bypass is conceptually trivial - a crafted string is all that is required once access to the blame API is established.
GitPython before 3.1.59 discloses local file content through exception messages when parsing .gitmodules files that contain [include] directives, because the library fails to disable the merge_includes feature in GitConfigParser. An attacker who can introduce a malicious .gitmodules into a repository processed by a vulnerable GitPython instance can cause the first line of any locally readable file to appear verbatim in a MissingSectionHeaderError exception when repo.submodules is accessed. No active exploitation has been confirmed (absent from CISA KEV) and no public POC is referenced in available intelligence; a vendor-released patch exists in version 3.1.59.
Information disclosure in Grav CMS before 2.0.16 enables authenticated users holding page-edit permission to retrieve sensitive system configuration values - including Redis passwords and other stored credentials - by invoking `config.get()` or `config.toArray()` within Twig templates. The root cause is an incomplete default denylist in the Twig sandbox configuration that fails to block access to the `config` object when the `config_access` feature is enabled. No public exploit has been identified and the vulnerability is not confirmed actively exploited at time of analysis.
Server-Side Template Injection in the Grav Email plugin (getgrav/grav-plugin-email) before 4.2.2 permits authenticated remote code execution on the host running PHP. Any account holding only api.access and api.pages.write permissions - typical content-editor roles - can embed a Twig payload in the header.form.process.email.body Email action parameter, publish the page, and trigger arbitrary OS command execution by submitting the associated form. No active exploitation has been confirmed by CISA KEV and no public exploit has been identified at time of analysis, but the low privilege bar and well-understood SSTI attack class make this a high-priority remediation target.
Password reset and account activation token comparison in Grav Login Plugin before 3.9.1 uses PHP's non-constant-time === operator instead of hash_equals(), exposing a CWE-208 timing oracle in both taskReset() (classes/Controller.php) and the activation handler (login.php). Combined with the absence of rate limiting on the token-submission endpoint, an unauthenticated network attacker can submit high-volume repeated token guesses against a known username and statistically recover a valid reset token via timing discrepancy. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; the vendor itself characterizes practical exploitability as low, and no end-to-end network exploitation has been demonstrated.
Email address enumeration in the Grav Login plugin (getgrav/grav-plugin-login) before 3.9.1 lets unauthenticated remote attackers determine which email addresses are registered on a Grav CMS site. The register() method returns a distinct EMAIL_NOT_AVAILABLE error for already-registered addresses while proceeding normally otherwise, and because the registration endpoint enforces no rate limiting, an attacker can test addresses at scale, one per request. No public exploit identified at time of analysis; the assigned CVSS 4.0 score of 9.3 appears substantially inflated for what is fundamentally an information-disclosure weakness.
Configuration secret disclosure in Grav CMS before 2.0.16 allows authenticated content editors to extract sensitive values - including cache credentials - from system, site, and theme configuration arrays via the Twig templating engine. The sandboxed Twig render context fails to filter these configuration objects, permitting attackers to bypass the intended config_denied_paths restrictions using standard dot-notation syntax. No public exploit code or CISA KEV listing has been identified at time of analysis, though the CVSS 4.0 score of 7.1 reflects a high confidentiality impact for installations where editor access is not fully trusted.
Symlink following in Grav CMS Scheduler's Job::createLockFile() enables local attackers to overwrite arbitrary files writable by the web server process, affecting all versions prior to 2.0.16. The flaw arises because lock files are written to predictable paths inside a world-writable temp directory with no verification that the target path is not an attacker-controlled symlink; the next scheduled job execution blindly writes the job ID string to whatever the symlink points at. No public exploit has been identified at time of analysis, but the predictable path and world-writable directory make the conditions straightforward to stage on shared-hosting or multi-tenant systems.
AEAD authentication bypass in OpenSSL 3.0-4.0 lets attackers forge valid empty-ciphertext/tag pairs when applications encrypt or decrypt via the low-level EVP_Cipher() path with AES-OCB or ChaCha20-Poly1305. A zero-length cipher update was short-circuited to return success without producing or verifying the authentication tag, breaking the integrity guarantee that AEAD is supposed to provide. No public exploit is identified at time of analysis and EPSS is low (0.12%), but the flaw is confirmed and patched by the OpenSSL project and Ubuntu.
Unauthenticated sensitive data exposure in the SiteLeads WordPress plugin (Lead Generation Contact Widget & AI Chatbot) versions 1.2.0 and earlier allows any remote, unauthenticated attacker to retrieve sensitive information from affected WordPress installations. The vulnerability stems from improper protection of sensitive system data (CWE-497), where plugin-stored data - likely including lead contact details, API credentials, or configuration values - is accessible without authentication. No public exploit or CISA KEV listing has been identified at the time of analysis, though the CVSS score of 7.5 (High) reflects the low-effort, network-accessible nature of the attack.
Unauthenticated broken authentication in the WPLegalPages WordPress plugin (versions ≤ 3.7.0) allows remote attackers to bypass access controls on one or more plugin endpoints without any credentials or user interaction, as confirmed by the CVSS vector (AV:N/AC:L/PR:N/UI:N). The vulnerability is classified under CWE-288, meaning an alternate path or channel exists that circumvents the intended authentication gate. No public exploit code and no active exploitation (CISA KEV) have been identified at time of analysis, but the low attack complexity means opportunistic scanning is a realistic threat.
Local File Inclusion in MagicAI for WordPress (versions up to and including 1.4) allows authenticated subscribers to include arbitrary PHP files from the server's filesystem by manipulating user-controlled input that is passed to a PHP file-inclusion function without adequate path validation. With CVSS 8.8 (High) and network-accessible exploitation requiring only subscriber-level authentication, this flaw grants attackers full confidentiality, integrity, and availability impact over the affected WordPress installation. No public exploit or CISA KEV listing has been identified at time of analysis.
Out-of-bounds read in Autodesk 3ds Max's SVG file parser enables crash, sensitive memory disclosure, or arbitrary code execution within the 3ds Max process context when a user opens a maliciously crafted SVG file. Affected releases span 3ds Max 2026 prior to 2026.3.4 and 3ds Max 2027 prior to 2027.2.0, as confirmed by EUVD-2026-65150. EPSS stands at 0.25% (16th percentile) with SSVC exploitation status of 'none,' indicating no current active exploitation; however, the RCE-capable impact triad warrants patching in affected professional environments.
Out-of-bounds read in SpaceDot AcubeSAT On-Board Computer software exposes the spacecraft's CAN bus message handler to denial-of-service attacks. An attacker with access to the CAN bus network can send a crafted PerformFunction message to the OBC, triggering an out-of-bounds read in the CAN::Application::parsePerformFunctionMessage component that crashes the on-board computer. No public exploit identified at time of analysis, and EPSS exploitation probability sits at 0.14% (4th percentile), consistent with a highly specialized embedded aerospace target.
Sensitive credential disclosure in RansomLook (versions 0 through 2.0.0) exposes full API keys in the rendered HTML of the authenticated /admin/apikeys page: although the UI only shows a truncated key, each token is embedded verbatim in hidden form fields backing the enable/disable, private-access, and delete actions. Anyone able to view the admin page source or DOM, or any intermediary that retains HTTP response bodies (debugging proxies, browser caches, monitoring systems), can recover the complete tokens and then authenticate with those keys' privileges, including access to private data. There is no public exploit identified at time of analysis; the issue is fixed upstream by replacing rendered tokens with SHA-256-derived opaque handles.
Dolibarr's Members REST API before version 24.0.0 exposes bcrypt password hash verifiers to any authenticated user holding member-read rights, enabling offline password cracking attacks against member accounts. Both the member list and individual member detail endpoints return the crypted password verifier field because neither the base API serializer nor the Members API class applies field-level filtering to strip credential material from responses. A public proof-of-concept exists; this is not confirmed as actively exploited via CISA KEV, but the low access bar combined with exposed credential hashes and available exploit code makes this a genuine remediation priority for organizations running affected versions.
SQL injection in Dolibarr's users REST API (all versions before 24.0.0) allows authenticated users holding only user-read rights to exfiltrate sensitive database columns - including salary figures and password verifier hashes - that the API is explicitly designed to withhold from normal responses. The injection path targets unsanitized filter parameters concatenated directly into SQL WHERE clauses with no column-level access gating, enabling blind binary search on numeric fields and LIKE prefix iteration on string fields; raw database error messages in the same endpoint additionally leak internal column names. A publicly available exploit writeup documents the full technique (codeant.ai, VulnCheck); no CISA KEV listing is recorded at time of analysis.
Header-filter bypass in the Apache Camel Undertow component (4.11.0-4.14.8, 4.15.0-4.18.3, and 4.19.0-4.21.x) lets remote senders smuggle legacy 'websocket.' dispatch headers across the undertow transport boundary. Because UndertowEndpoint overwrote the UndertowHeaderFilterStrategy with the base HttpHeaderFilterStrategy, undertow-specific filtering never ran on endpoint-configured routes, so an undertow HTTP consumer maps attacker-controlled 'websocket.*' wire headers onto the Exchange and a downstream undertow WebSocket producer can be steered to deliver to a peer other than the one the route selected. No public exploit identified at time of analysis, EPSS is low (0.16%, 5th percentile), and the fix is available from Apache.
Stored cross-site scripting in NethServer's WebTop calendar component (versions 1.5.6 and earlier) permits an authenticated attacker to inject malicious JavaScript into calendar event fields, which silently executes in the browser of any user who subsequently views the poisoned event. The impact scope includes session hijacking, unauthorized access to emails, contacts, and files, and the ability to perform actions as the victim within the platform - all without the victim taking any action beyond viewing the event. No active exploitation or public exploit code has been identified at time of analysis; a vendor-released patch exists in WebTop 1.5.7.
Token exfiltration in Black Duck blackduck-c-cpp 1.0.17 through 3.0.6 allows any actor with code execution inside a scanned project's build to read the Black Duck API token from the process environment inherited by scanning subprocesses. The token - when supplied via BLACKDUCK_API_TOKEN or BD_HUB_TOKEN - is passed in plaintext to child processes spawned during build capture and signature scanning, where it is observable by co-located code. No public exploit has been identified at time of analysis; however, the vendor explicitly warns that upgrading does not remediate prior exposure, making token rotation a mandatory incident-response step for all affected deployments.
Sensitive scraping credentials and bypass logic were exposed to unauthenticated callers through multiple RansomLook API endpoints. Location records associated with monitored ransomware groups and markets were returned verbatim - including the `header` field containing authentication tokens and session cookies, the `init_script` field holding CAPTCHA and anti-bot bypass logic, and `browser` metadata revealing the scraping environment - whenever a location was not explicitly marked private. The patch, confirmed via GitHub commit cc9182930306ff36c7b3424817d49f18df3c85d1, introduces a strict field allowlist and a sanitization function applied across all three affected API routes; no public exploit or KEV listing has been identified at time of analysis.
HCL Hive employs a risky cryptographic primitive (CWE-1240) that creates systemic trust failure across the platform: if any single internal component is compromised, an attacker can exploit the weak cryptographic construction to achieve unauthorized lateral movement or harvest credentials at scale. The CVSS vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N) indicates the flaw is reachable over the network without authentication, though high attack complexity caps opportunistic risk. No public exploit code or active exploitation has been identified at time of analysis.
Local File Inclusion in the Måne WordPress theme (versions ≤ 1.7) exposes sites to unauthenticated file inclusion attacks exploitable over the network, classified under CWE-98 (Improper Control of Filename for PHP Include/Require). Attackers can force the theme's PHP code to include arbitrary server-side files, potentially exposing sensitive configuration data or — when chained with a writable server location — achieving remote code execution under the web server's process identity. No public exploit code or CISA KEV active-exploitation listing has been identified at time of analysis, though the vulnerability class is technically well-understood and widely targeted in WordPress ecosystems.
Arbitrary file disclosure in the WP Cafe Pro WordPress plugin (all versions before 3.0.15) lets remote unauthenticated attackers perform Local File Inclusion, reading sensitive server files such as wp-config.php or, in PHP include contexts, potentially executing attacker-controlled code. The flaw is network-reachable with no privileges or user interaction (CVSS 9.8), was reported by Patchstack, and a vendor patch exists in 3.0.15. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Unauthenticated sensitive data exposure in WP Cafe Pro WordPress plugin versions prior to 3.0.15 allows any remote attacker without credentials to retrieve sensitive information directly from affected WordPress installations. Classified under CWE-201 (Insertion of Sensitive Information Into Sent Data), the flaw is network-exploitable with no authentication or user interaction required, yielding a CVSS 3.1 score of 7.5 (High). No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor-released patch is available in version 3.0.15.
Local File Inclusion in the Tonda Core WordPress plugin (all versions prior to 2.6) exposes unauthenticated remote attackers to arbitrary local-file disclosure and, under secondary conditions, potential remote code execution on the host server. Reported by Patchstack and registered under ENISA EUVD-2026-64791, the flaw carries a CVSS 3.1 score of 8.1 with full C/I/A impact and no authentication requirement. A vendor-released patch is available at version 2.6; no confirmed active exploitation or public exploit code has been identified at time of analysis.
Local File Inclusion in the Tonda WordPress theme (versions below 2.6) enables unauthenticated remote attackers to manipulate PHP include statements and read arbitrary files from the server filesystem. The vulnerability is network-exploitable without authentication, but the CVSS AC:H rating indicates exploitation requires specific conditions or input validation bypass rather than trivial mass exploitation. Vendor patch is available at version 2.6; no public exploit or CISA KEV listing has been identified at time of analysis.
Local File Inclusion in the Verdure Core WordPress plugin (versions ≤ 1.2) allows unauthenticated remote attackers to include arbitrary files from the server's filesystem by passing unsanitized input to PHP include/require statements. Successful exploitation can expose sensitive server files such as wp-config.php - disclosing database credentials - and, under certain PHP configurations, may enable remote code execution through log poisoning or PHP wrapper abuse. No public exploit code or CISA KEV listing has been identified at time of analysis, though the unauthenticated attack vector lowers the barrier for opportunistic targeting of vulnerable WordPress installations.
Prototype pollution in exceljs-hardened before 5.0.0 lets a remote attacker corrupt Object.prototype by feeding parsed JSON containing a malicious __proto__ property into a cell note, because the deepMerge helper in the note-serialization path fails to reject __proto__, constructor, or prototype keys. Any application that uses this library to process untrusted spreadsheet or note data is affected, and polluting the global prototype can cascade into denial of service, logic tampering, or code execution via downstream gadgets. No public exploit is identified at time of analysis, and the flaw is not listed in CISA KEV.
OneNav 1.2.4's import_link() function allows any authenticated user to delete arbitrary files on the host system via path traversal, scoring CVSS 8.1 with High integrity and availability impact. Publicly available exploit code exists per SSVC assessment (exploitation: poc), though EPSS probability remains very low at 0.14% (4th percentile), indicating limited widespread exploitation activity. The attack requires only low-privilege authentication over the network with no user interaction, making it accessible to any registered user of an exposed OneNav instance.
PHP Object Injection in PPWP - Password Protect Pages (WordPress plugin, versions up to and including 1.9.18) permits authenticated attackers holding Contributor-level roles or higher to deserialize attacker-controlled data via the 'post_protection_roles' parameter, injecting arbitrary PHP objects into the application. Real-world impact is fully contingent on a Property-Oriented Programming (POP) chain being present in another co-installed plugin or theme - absent that chain, the vulnerability has no exploitable effect, but where one exists, outcomes can include arbitrary file deletion, sensitive data retrieval, or remote code execution. No public exploit code or active exploitation has been identified at time of analysis; however, a Wordfence advisory and a WordPress SVN changeset (3567221) both indicate a fix has been committed.
Insufficient access control granularity in docker-socket-proxy allows adjacent-network attackers without credentials to read arbitrary files and exfiltrate entire container filesystems via four unguarded Docker API endpoints. When the CONTAINERS environment variable is set, the HAProxy-based proxy fails to block /containers/{id}/archive, /containers/{id}/export, /containers/{id}/logs, and /containers/{id}/top, treating namespace-level permission as blanket endpoint permission. No active exploitation or confirmed public exploit code has been identified at time of analysis, though a researcher gist is referenced alongside the upstream fix in PR #183.
Race condition in the Linux kernel's GPIO PCA953x driver allows local low-privileged users on systems with PCA953x I2C GPIO expander hardware to trigger incorrect register reads or writes by exploiting missing mutex coverage in pca953x_irq_bus_sync_unlock(). A prior partial fix protected only the interrupt mask register write but left the direction register read unguarded, permitting concurrent threads to interleave I2C transactions and corrupt GPIO expander state on affected kernel stable branches including 6.1.101-6.2, 6.6.42-6.7, and 6.9.11-6.10. No public exploit has been identified and EPSS exploitation probability is 0.20% at the 10th percentile, consistent with negligible real-world exploitation interest.
Use-after-free in the Linux kernel's sched_ext (extensible BPF scheduler) subsystem allows a local low-privileged attacker to corrupt kernel memory, potentially achieving full confidentiality, integrity, and availability compromise of the affected system. The race condition arises when a sub-scheduler enable fails before being linked into the scheduler hierarchy, yet the full teardown path still executes concurrently against root scheduler disable, causing tasks to be re-homed onto an already-freed scheduler hierarchy. No public exploit or POC has been identified at time of analysis, and EPSS at 0.20% (10th percentile) reflects negligible observed exploitation activity.
A use-after-free in the Linux kernel's NFSv4 client can occur when a FREE_STATEID operation is delayed and the associated 'struct nfs_server' is torn down (for example on unmount) while the operation is still in flight, leaving the RPC referencing freed memory. The fix pins the nfs_server by bumping its refcount for the duration of the FREE_STATEID call. This is a client-side race condition, not a server-facing service bug; no public exploit identified at time of analysis, and EPSS is low (0.22%, 13th percentile).
Use-after-free in the Linux kernel's ovpn (in-kernel OpenVPN data-channel offload) module lets a local privileged attacker corrupt kernel memory by racing peer-management operations. A time-of-check/time-of-use window between ovpn_peer_get_by_id() and acquisition of ovpn->lock allows a peer that was concurrently removed to be re-inserted into the rehash tables, resurrecting a peer userspace believes is gone and leaving embedded hash entries linked to memory later freed via call_rcu. There is no public exploit identified at time of analysis and EPSS is low (0.21%, 11th percentile), consistent with a hard-to-win kernel race rather than a mass-exploitable bug.
Null-pointer dereference and promiscuity counter underflow in the Linux kernel bonding driver's ALB monitor can crash the kernel or permanently pin a network interface in promiscuous mode. The bond_alb_monitor() workqueue function reads primary_is_promisc under RCU, drops that lock, then acquires RTNL - allowing the active slave to be removed or changed in the intervening window, leaving the monitor to act on stale state. Linux systems from kernel 2.6.24 through unpatched stable branches (5.10.x, 5.15.x, 6.1.x, 6.6.x, 6.12.x, 6.18.x, 7.1.x, 7.2) with network bonding explicitly configured in ALB mode are affected. No public exploit identified at time of analysis.
Use-after-free in the Linux kernel's enic driver (Cisco VIC Ethernet NIC) allows a local attacker with low privileges to corrupt kernel heap memory during network device removal. The enic_remove() teardown function fails to cancel or disable the tx_hang_reset work item, creating a race window where a TX watchdog timeout can reschedule enic_tx_hang_reset() to execute after free_netdev() has already released the underlying network device structure. No public exploit exists and EPSS probability is 0.21% (11th percentile), though the kernel use-after-free primitive carries high C/I/A impact if reliably triggered.
Reference count underflow in the Linux kernel amdxdna (AMD XDNA NPU accelerator) driver allows a local low-privileged user to corrupt kernel memory via a double invocation of vm_ops->close() triggered by failed mmap page insertions. Two error paths in amdxdna_insert_pages() incorrectly release the shmem pages_pin_count and backing GEM object reference while the VMA remains live; the kernel's subsequent VMA teardown fires vm_ops->close() a second time, producing a reference count underflow with potential use-after-free consequences and high impact across confidentiality, integrity, and availability. No public exploit has been identified at time of analysis and EPSS is 0.20% (10th percentile), consistent with the niche AMD Ryzen AI hardware requirement limiting real-world exposure.
Privilege escalation in the Linux kernel BPF verifier affects versions from 4.16 through current stable branches due to incomplete pointer state propagation during commuted arithmetic (scalar += pointer) in adjust_ptr_min_max_vals(). Local attackers with BPF program loading privileges can exploit the verifier's failure to copy the full bpf_reg_state structure, potentially bypassing memory safety enforcement and achieving arbitrary kernel memory access. No public exploit has been identified at time of analysis and EPSS is low at 0.22%, but the CVSS score of 7.8 (C:H/I:H/A:H) reflects the severity of kernel-level impact if successfully exploited.
Use-after-free in the Linux kernel's BPF TCP iterator exposes systems running kernel versions from 5.15 onward to local privilege escalation with high impact across confidentiality, integrity, and availability. The race condition in bpf_iter_tcp_established_batch() allows a low-privileged local attacker to hold a reference to a request_sock whose refcount is still zero, corrupting kernel memory when the publishing CPU's refcount_set() subsequently overwrites the saturated value. No public exploit has been identified at time of analysis, and EPSS sits at 0.21% (12th percentile), though the race is described as reproducible within seconds under controlled conditions with tcp_syncookies=0.
Unbounded memory allocation in the Linux kernel's vhost_iotlb subsystem allows availability impact on the host system via exhaustion of kernel memory. The flaw exists in vhost_iotlb_add_range_ctx(), where non-retiring IOTLB tables bypass the configured entry limit and continue allocating entries indefinitely - including via guest-controlled or userspace requests to vhost, mlx5 vDPA, VDUSE, and vhost-vDPA subsystems. No public exploit code has been identified at time of analysis, and EPSS probability is very low (0.20%), but the CVSS scope-change metric (S:C) reflects that a guest workload can impact host kernel availability.
Out-of-bounds kernel memory read in the Linux kernel AF_XDP subsystem allows a local low-privileged user to trigger reads beyond registered memory regions by supplying TX metadata shorter than 16 bytes. Affected systems include Linux kernel versions from the introduction of commit 341ac980eab9 through multiple stable branches, with patches available at 6.12.104, 7.1.9, and 7.2. No public exploit has been identified and EPSS is 0.21% (11th percentile), indicating low current exploitation activity despite the high CVSS score.
Memory corruption in the Linux kernel's AF_XDP socket (xsk) subsystem arises from two related flaws: missing size validation for launch-time metadata fields that extend beyond the first 16 bytes of struct xsk_tx_metadata, and a race condition where user space can modify transmit flags concurrently with kernel transmit processing. A local attacker with low-privilege access who can create and configure AF_XDP sockets may trigger out-of-bounds memory access, leading to high-impact compromise of confidentiality, integrity, and availability consistent with the CVSS 7.8 score. No public exploit code has been identified, EPSS sits at 0.21% (11th percentile), and the CVE is absent from CISA KEV, placing practical exploitation risk well below what the raw CVSS score might suggest.
Use-after-free in the Linux kernel's UDP tunnel GSO segmentation path (__skb_udp_tunnel_segment()) occurs when the code dereferences a saved UDP header pointer after a skb_pull() reallocates skb->head, invalidating that pointer. The flaw affects hosts that software-segment UDP-encapsulated tunnel traffic (VXLAN/GENEVE/FoU), and can lead to a kernel crash or potential information disclosure. No public exploit is identified at time of analysis, EPSS is low (0.22%), and the issue is not on CISA KEV; the upstream fix reorders the header fetch to occur after the pull.
Remote denial of service in the Linux kernel's CAKE traffic scheduler (sch_cake) allows an unauthenticated network attacker to trigger a kernel panic or persistent warning-log flood by sending malformed IP packets to a system with the CAKE qdisc actively configured. Affected systems running Linux 4.19 through unpatched versions of the 7.x series face kernel panic if the non-default `panic_on_warn=1` boot parameter is set, or dmesg flooding otherwise. No public exploit has been identified and this CVE is not in the CISA KEV catalog, but the fix is low-risk and multiple patched stable kernel versions are available.
Kernel panic in Linux kernel's vhost-scsi subsystem can be triggered by a malicious guest VM when T10 Protection Information (PI) is negotiated, crashing the host kernel and all co-hosted virtual machines. A guest sends a malformed SCSI request with protection byte lengths equal to or exceeding the payload, causing an integer underflow or zero-count scatterlist that hits an unconditional BUG_ON assertion in sg_alloc_table_chained(). With EPSS at 0.21% (11th percentile), no CISA KEV listing, and no public proof-of-concept identified at time of analysis, exploitation probability is currently low but the guest-to-host scope change makes this a meaningful availability risk in multi-tenant virtualized storage environments.
The vhost-scsi subsystem in the Linux kernel allows a local attacker with low privileges on a KVM virtualization host to trigger a kernel BUG_ON assertion and crash the host by manipulating VIRTIO feature bits after SCSI endpoint setup. The flaw is that vhost_scsi_set_features() incorrectly accepted changes to VIRTIO_SCSI_F_T10_PI after an active endpoint was established, leaving per-command protection scatterlist arrays (prot_sgl) unallocated while the I/O path proceeded under the updated feature state; when a 129-page protection payload arrives, a BUG_ON(nents > SG_CHUNK_SIZE) fires in sg_pool_index(), panicking the host kernel. Patches are confirmed for stable branches 6.18.45 and 7.1.9 and mainline 7.2; no public exploit exists and no CISA KEV listing is present, with an EPSS of 0.21% (11th percentile).
Kernel BUG triggerable in the Open vSwitch (OVS) net subsystem allows a local low-privileged attacker to crash the kernel or potentially escalate privileges by injecting undersized Ethernet frames through a TUN device. Affected kernels from Linux 4.10 onward trust the user-supplied skb->protocol field on ARPHRD_NONE devices without validating that sufficient linear data exists for Ethernet header parsing, causing __skb_pull() to hit an unconditional BUG halt. No public exploit code has been identified and EPSS probability stands at 0.22% (13th percentile), indicating low opportunistic exploitation risk; however, patches are available across all active stable branches.
Use-after-free in the Linux kernel's traffic control classifier API (net/sched/cls_api) allows a local attacker with CAP_NET_ADMIN to corrupt kernel memory by racing two concurrent tc_new_tfilter() calls targeting the same chain and priority with different classifier types. A proof-of-concept is referenced in the upstream kernel commit but is not independently confirmed as publicly released. EPSS is 0.21% and the vulnerability is not listed in CISA KEV, indicating no observed widespread exploitation at time of analysis.
Data corruption in the Linux kernel bnxt_en driver (Broadcom NetXtreme-E) occurs when TCP Packet Aggregation (TPA) is active alongside PCIe Relaxed Ordering (RO) on AGG rings. When EOP (End-of-frame padding) is used, zero-padding bytes appended at the end of one aggregated segment can spill over and overwrite valid data at the start of the subsequent segment. Older chips (P5 generation and earlier, including the Broadcom 57508) do not automatically suppress RO when EOP is active, making ARM-hosted deployments using these adapters particularly vulnerable to silent data corruption in received network traffic. No public exploit is identified at time of analysis, and EPSS probability is low at 0.21% (12th percentile).