Information Disclosure
Monthly
Authenticated remote code execution in OpenCATS versions prior to 0.10.0 lets an administrator-level user with Settings-module access inject PHP syntax into config.php through the Professional License key field, producing persistent arbitrary code execution as the web server user. The flaw is gated by the PR:H metric in the CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2 High): the attacker must already hold an administrator account with permission to update the Professional License configuration, and config.php must be writable by the web server process for the write-based path to succeed. Successful exploitation gives full confidentiality, integrity and availability impact over candidate, contact, company, job order and user data, and the vendor states unauthenticated exploitation or exploitation by users without Settings access is not established; no public exploit code has been identified at time of analysis and the issue is fixed in v0.10.0.
MongoDB Database Tools builds prior to 100.20.0 (specifically 100.19.0, compiled with Golang 1.26.8) will accept TLS server certificates chaining to the eMudhra CA, which Go's crypto/x509 denylist only began rejecting in Golang 1.27.3. An attacker holding a man-in-the-middle position on the network path and a usable eMudhra-issued certificate for the targeted hostname could therefore intercept DB Tools connections to a MongoDB server and read or alter traffic; the victim must actively initiate the connection. No public exploit code or confirmed active exploitation was identified at the time of analysis, and the flaw is resolved in DB Tools 100.20.0.
Authenticated SQL injection in OpenCATS prior to 0.10.0 lets any logged-in user who can reach the home Calls DataGrid (home:CallsDataGrid) or activity DataGrid (activity:ActivityDataGrid) rewrite the date-filter SQL and read data beyond their intended scope, including user accounts, candidate records, contacts, company records, job orders and activity history. The flaw sits in the request-controlled period, startDate and endDate parameters, which are concatenated into SQL date comparisons in modules/home/dataGrids.php and modules/activity/dataGrids.php without validation or escaping; a valid OpenCATS login is required and unauthenticated exploitation is not established. The confidentiality impact dominates (the data exposure is the practical harm), and no public exploit code was identified at time of analysis; the vendor-released patch is OpenCATS 0.10.0.
AnkiMCP Server addon 0.20.0 and earlier ships a FastMCP Streamable HTTP listener enabled by default on 127.0.0.1:3141 with DNS-rebinding protection globally disabled, so a malicious web page that rebinds a hostname to loopback can complete MCP `initialize`, enumerate tools with `tools/list`, and dispatch `tools/call` against the victim's Anki collection without any bearer token, API key, session secret, or Host/Origin allowlist check. Because the flaw needs the victim to browse an attacker-controlled page while Anki and the listener are live, and depends on successful rebinding and timing (CVSS 3.1 AV:N/AC:H/PR:N/UI:R/S:C), the practical window is conditional rather than continuous; the vendor GHSA includes a reproduction harness that reaches real MCP tool dispatch with substituted Anki bridge responses, but it is not verified as working exploit code that modifies a real collection. There is no CISA KEV entry and no confirmed active exploitation at time of analysis; default impact is unauthorised read of the collection plus non-destructive note/deck creation and updates, since destructive tools stay hidden unless `enabled_destructive_tools` is opted into.
Unauthenticated attackers can leak password hashes, email addresses, and post metadata from WordPress sites running Bricks Theme 2.4.3 and earlier by injecting dynamic-data tags through the query_result REST endpoint. The flaw is remotely exploitable with no authentication or user interaction (CVSS 7.5, confidentiality-only impact), and the vendor has released Bricks 2.4.4 as the fix. No CISA KEV entry is present and no public exploit was identified at time of analysis, but the unauthenticated confidentiality impact makes this a high-priority update.
Stale authentication state in GraphQL Tools' legacy WebSocket executor lets a later caller inherit a previous caller's downstream identity: the closure-scoped executorConnectionParams object retains per-request extensions.connectionParams after cleanupWebsocket tears down the socket, and the retained keys are replayed in a subsequent connection_init payload. Only applications that reuse a single buildWSLegacyExecutor instance across different authorization contexts are exposed - most notably gateway, schema-stitching, or GraphQL Mesh deployments that pass per-user Authorization or tenant values through extensions.connectionParams; an anonymous or lower-privileged request that omits the sensitive key can then have its downstream subscription executed under the earlier user's token, though the credential itself is never disclosed. Applications that build a fresh executor per request, including the in-repository UrlLoader wrapper, are not affected; exploitation is remote and unauthenticated from the library's perspective but gated by the shared-executor architecture, and no public exploit code was identified at time of analysis.
Server-side request forgery in KServe lets any principal that holds namespace-scoped create or update rights on InferenceService custom resources point the model-serving controller at an attacker-chosen destination: the crafted `storageUri` is fetched by the `storage-initializer` init container, which issues arbitrary outbound HTTP/HTTPS requests from inside the cluster. The result is information disclosure rather than data corruption - successful abuse can expose the node's cloud IAM role credentials through instance-metadata endpoints or reach internal-only cluster services that the tenant namespace could not otherwise touch. Exploitation is access-gated, requiring the attacker to already hold those InferenceService RBAC permissions (CVSS PR:L, scope-changed, confidentiality-only), and no public exploit was identified at time of analysis; the vendor rates it this_week, not an emergency.
OAuth token revocation in WSO2 Identity Server fails to invalidate access and refresh tokens for accounts whose usernames contain mixed-case characters when the deployment pairs a case-insensitive user store with a case-sensitive identity database. An authenticated attacker (PR:L) who already holds a valid, unexpired token for such an account can keep using it for actions that should have been blocked after a revocation-triggering lifecycle event, bounded by the token's natural expiry. Affected deployments are a non-default configuration subset, the trigger requires that specific store/database mismatch plus a mixed-case username, and no public exploit has been identified at time of analysis; the input 7.4 score assumes AC:L, whereas the assessed vector uses AC:H, so real-world risk is materially lower than the headline number suggests.
Filesystem sandbox escape in Wasmtime's wasmtime-wasi crate allows a sandboxed guest on macOS or FreeBSD to move host directories accessible to the host process into its own sandbox and then read or write their contents, defeating the runtime's core isolation guarantee. Affected releases are 36.0.17 and earlier, 37.0.0 through 48.0.5, and 49.0.0 through 49.0.2; Linux and Windows hosts are explicitly not affected. Exploitation requires a guest already executing with write access to at least one sandbox directory, and no public exploit code has been identified at time of analysis - though the vendor notes the bug affects every published version as of the advisory and provides no workaround other than upgrading.
Coder deployments that run workspace agents on Google Compute Engine with GCP instance-identity authentication accept replayed GCE identity tokens because the POST /api/v2/workspaceagents/google-instance-identity endpoint never validated the token's audience claim, allowing an attacker holding an unexpired format=full token minted for a different relying party to exchange it for that workspace agent's session token. The resulting agent token stays valid until the workspace's next build, well past the identity token's roughly one-hour lifetime. Affected releases are those before 2.29.21 and the 2.30.0-2.34.11, 2.35.0-2.35.8, 2.36.0-2.36.6 and 2.37.0-2.37.3 ranges, fixed in 2.38.0 and the listed backports; the flaw is unauthenticated per the supplied vector (PR:N) but conditional, since the attacker must already possess a genuine, unexpired token from a VM backing an agent on the workspace's latest build, and no public exploit was identified at time of analysis. The vendor advisory credits independent reports from a customer security team and an external researcher.
n8n versions before 2.43.5 and 2.44.x before 2.44.1 allow an authenticated member who can create and run workflows to bypass project boundaries and list, read, modify, and delete Data Table rows in all projects by supplying a crafted workflow ID such as __proto__. The flaw is a prototype-pollution-style authorization bypass in the in-memory workflow owner-project cache, rated 8.7 with PR:L in the CVSS vector, so exploitation requires a member account and the Data Tables module. Vendor fixes are available in 2.43.5 and 2.44.1; no public exploit was identified at time of analysis, and KEV status was not provided.
Prototype pollution in the Highcharts JS charting library (6.1.0 up to 11.4.9, 12.0.0 up to 12.6.1, and 13.0.0 through 13.0.2) lets an attacker who controls a chart's series.keys array and the matching per-point data write arbitrary named properties onto Object.prototype using dot-separated paths such as '__proto__.polluted' or 'constructor.prototype.alsoPolluted'. No user interaction is required beyond rendering the chart, and because the injected properties are visible to all JavaScript on the page rather than only to the chart - reflected as scope-changed (S:C) in both the vendor CVSS 4.0 vector and the independently assessed CVSS 3.1 vector - concrete harm depends on what other page code later reads. Exploitation is contextual: series.keys is normally a static developer-defined configuration, so only applications that route untrusted input into both keys and point data are exposed, and the advisory links a live JSFiddle demonstration of the pollution (a public PoC reference exists; it is not verified as working exploit code). There is no CISA KEV entry and no confirmed active exploitation; the vuln.today decision label is 'this_week', a moderate context-dependent priority rather than an emergency.
Prototype pollution in Highcharts JS 13.0.0 through 13.0.2 lets attacker-controlled series point data write integer-keyed properties onto Object.prototype and the Object constructor, which then surface in out-of-range index reads and for...in enumeration of every object on the page. No user interaction is required beyond rendering a chart built from those point objects, and the injected properties persist after the chart is constructed; the practical consequence runs from broken rendering to whatever the consuming application does with attacker-supplied inherited values. The issue is fixed in 13.1.0, is not listed in CISA KEV, and no working exploit code is confirmed - the vendor advisory does publish a live JSFiddle demo for testing, and the current priority label is this_week rather than an emergency call.
Jenkins core 2.587 and earlier, along with LTS 2.580.1 and earlier, are covered by the 2026-10-28 Jenkins security advisory, and the EUVD record for this CVE points to advisory section SECURITY-4206; that section's text is not included in the material supplied here, so the specific defect, its trigger, and its exact permission prerequisites for CVE-2026-117625 cannot be confirmed from available data. What is confirmed for the advisory as a whole is that every listed issue requires an authenticated, non-anonymous Jenkins user holding a permission such as Overall/Read, Item/Configure, View/Configure, or Agent/Configure, and that several of the batch lead to remote code execution or stored cross-site scripting on the controller. No public exploit code or confirmed active exploitation is identified in the supplied sources, and the priority decision remains awaiting data, so treatment should be driven by the confirmed availability of the 2.588 / LTS 2.580.2 fix rather than by an exploitation signal.
Jenkins core 2.587 and earlier, along with LTS 2.580.1 and earlier, are affected by CVE-2026-117619, one of eight security issues addressed in the Jenkins advisory dated 2026-10-28 and fixed in Jenkins 2.588 and LTS 2.580.2. The per-CVE description for this specific identifier is not present in the supplied advisory excerpt, so neither the vulnerability class nor the precise attacker impact can be stated from the available data - only the affected scope and the fixed versions are confirmed. Every other entry in the same advisory requires an authenticated user holding specific Jenkins permissions (Overall/Read, Item/Configure, View/Configure, Agent/Configure, Item/Create) rather than anonymous access, which suggests a similar privilege prerequisite is likely here, but that remains unverified. No public exploit code and no CISA KEV entry are associated with this identifier in the supplied intelligence, and the priority decision is awaiting_data.
Arbitrary file read on the Jenkins controller affects Jenkins 2.587 and earlier and Jenkins LTS 2.580.1 and earlier when an authenticated user with both Item/Create and Item/Configure renames an item whose directory contains a symbolic link, causing the copy fallback to follow the link and disclose file contents. The direct impact is confidentiality loss (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N); disclosed secrets can enable a contingent escalation to remote code execution. No public exploit identified at time of analysis, and the supplied data contains no EPSS score or CISA KEV entry.
CVE-2026-117618 is one identifier in the Jenkins Security Advisory 2026-10-28 bundle, which fixes multiple Jenkins core vulnerabilities affecting Jenkins 2.587 and earlier and LTS 2.580.1 and earlier; the vendor-released patch is Jenkins 2.588 and LTS 2.580.2. The advisory excerpt available for this analysis enumerates SECURITY-4125/CVE-2026-117612 through SECURITY-4249/CVE-2026-117622 but does not include a description mapping SECURITY-4125 through SECURITY-4249 to the -117618 identifier, so the specific vulnerable component, attack vector, and required permissions for this CVE are unverified and must be read from the advisory page. No CISA KEV listing, no EPSS score, and no public exploit code were present in the supplied data, so exploitation status is no public exploit identified at time of analysis, and the vuln.today decision label remains awaiting_data. For the sibling issues in the same advisory, exploitation requires an authenticated foothold with configuration privileges (Overall/Read plus a non-anonymous account, Item/Configure, Agent/Configure, or Item/Create depending on the issue), and several of those siblings can lead to remote code execution on the controller.
Arbitrary file write on the Jenkins controller is possible in Jenkins 2.587 and earlier and LTS 2.580.1 and earlier when an authenticated user with Item/Configure permission archives artifacts concurrently, such as from parallel Pipeline branches. The extraction code checks for symbolic links only before creating parent directories and permits symlinks in artifacts to replace existing files or empty directories, leaving a race before the final write; successful exploitation can overwrite files outside the intended directory and lead to remote code execution. No public exploit was identified at time of analysis, and the vendor fixed the issue in Jenkins 2.588 and LTS 2.580.2.
Apache Kafka brokers that run SASL/OAUTHBEARER with the default DefaultJwtValidator and leave sasl.oauthbearer.jwks.endpoint.url unset silently fall back to a validator that performs no JWT signature, algorithm, or issuer checks, allowing unauthenticated remote attackers with listener reachability to forge tokens for arbitrary principals, including configured superusers, and gain full cluster access. The flaw is a residual of CVE-2026-33557 and only affects brokers in this specific OAUTHBEARER-without-JWKS-URL configuration with no custom verification key resolver; brokers that set the JWKS URL verify signatures and are not affected. No CISA KEV listing or public exploit code is identified in the available data, no public exploit identified at time of analysis, and no EPSS score is provided.
Integer underflow in Juniper Networks Session Smart Router's DhcpMessageDecoder allows an attacker on the adjacent network to cause information disclosure and denial of service by sending a malicious DHCP reply. The issue affects Session Smart Router deployments where the router processes DHCP replies as a client or relay on an attacker-reachable Layer 2 segment; the CVSS 3.1 vector is AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H, so no authentication or user interaction is required but exploitation is confined to local-segment presence. No public exploit code or active exploitation is identified in the provided data, and the priority label is this_week.
Authorization bypass in mongodb/laravel-mongodb can let an authenticated user with basic privileges read, change, or delete documents that an application intended to withhold when it relies on an absence-of-related-record relationship check. The flaw is a type-handling error in relationship query building (CWE-843) that silently compiles that check with an identifier of the wrong data type; exploitation is conditional on the application using this authorization pattern and on a triggering identifier type, matching the assessed CVSS:3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. No public exploit was identified at time of analysis, and the vendor references release 5.12.0.
Unauthenticated information disclosure in the Supsystic Contact Form WordPress plugin (all versions through 1.10.5) lets remote attackers retrieve sensitive data that the plugin embeds in the data it sends. The CVSS 3.1 score of 7.5 reflects network-only access with no privileges and no user interaction, high confidentiality impact, and no integrity or availability effect; vuln.today triage rates it this_week, i.e. moderate rather than emergency priority. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the precise endpoint, parameter, or output path that exposes the embedded data is not described in the available sources.
Unauthenticated remote file upload and direct retrieval weaknesses in HCL BigFix AEX allow attackers to place files on the server and then access or download uploaded content without proper authorization. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) shows the issue is reachable over the network at low complexity with no authentication or user interaction, and the supplied CPE identifies the affected product without a narrower version boundary. No CISA KEV entry or public exploit was identified at time of analysis, but the issue is assessed as a credible high-priority item to address this week rather than an emergency.
Remote code execution in HCL BigFix AEX is reachable over the network with low attack complexity, but the CVSS vector requires a high-privilege account (PR:H), so an attacker must already hold privileged access to the product before exploiting the code-injection flaw (CWE-94). The scope change (S:C) indicates that successful exploitation can affect resources beyond the vulnerable component, with high confidentiality, integrity, and availability impact. No public exploit has been identified at the time of analysis, and the vendor advisory KB0134281 is the primary reference; the vuln.today decision label is act_now.
Acronis Cyber Protect 17 on Linux and Windows before build 42587 can expose sensitive information and allow manipulation of protected resources through improper token validation, reachable over the network without authentication but requiring high attack complexity. Vendor CVSS is 7.4, and the this_week decision label makes this a moderate-priority remediation rather than an emergency. No public exploit code was identified at time of analysis.
Token forgery in Acronis Cyber Protect 17 before build 42587 can allow remote, unauthenticated attackers to bypass authentication or authorization, resulting in sensitive information disclosure and data manipulation on Linux and Windows installations. The CVSS 3.0 score is 7.4 with high attack complexity (AC:H), indicating non-trivial preconditions; no public exploit identified at time of analysis and no CISA KEV entry is present.
Remote, unauthenticated attackers can obtain exposed credentials from Dell PowerProtect Data Domain appliances running Feature Release 7.7.1.0 through 8.8, LTS2024 7.13.1.0 through 7.13.1.80, LTS2025 8.3.1.0 through 8.3.1.40, or LTS2026 8.6.1.0 through 8.6.1.20 because hard-coded cryptographic key material is present in the affected firmware. Exploitation requires network reachability to the appliance and results in access bounded by the privileges of the compromised user, not guaranteed administrative control. No public exploit code or CISA KEV entry is identified in the available data, but the 9.8 CVSS score and act_now priority reflect a genuine high-priority credential-exposure risk; the exact key-to-credential mechanism is not described.
Privilege escalation in Dell PowerProtect Data Domain Feature Release 7.7.1.0 through 8.8 allows an authenticated, low-privileged remote attacker to obtain high-impact confidentiality, integrity, and availability effects on the appliance. Dell has released a vendor fix in 8.9.0.0; no public exploit has been identified at time of analysis, and the issue warrants prompt remediation rather than emergency action.
AXIS Camera Station Pro and Camera Station 5 weakly encrypt database backups (CWE-326), so an attacker who obtains a backup file can attack it offline and recover the credentials stored inside. The exposure covers backups created before the fix and the extra recovery backup that Camera Station automatically creates when the update is applied; the CVSS 7.1 vector (AV:L/PR:L, UI:N) means local access to the backup artifacts and low privileges are required, not remote reachability. No public exploit code or confirmed active exploitation was identified at time of analysis, and updating alone does not remove already-exposed backups.
Information disclosure in the Animated Text Block WordPress plugin (versions up to and including 1.2.6) allows an authenticated user with Contributor-level access or higher to read the rendered content of any published post on the site. The 'animated-text' shortcode handler accepts an attacker-supplied post ID and, in its 'publish' branch, renders the post without any capability check and without verifying that the post type is the plugin's own custom post type or is otherwise viewable - so posts in non-public custom post types (public=false, show_in_rest=false) that WordPress normally hides from direct URLs and the REST API can be disclosed. Impact is confidentiality-only (no modification or denial of service), the target post must be in 'publish' status, and no public exploit code or PoC reference is present in the available sources; the vuln.today decision label is this_week.
CVE-2026-109411 is tracked through the Ubuntu vendor channel, which indicates the affected code is a package distributed by Ubuntu, but the supplied record carries no description, CVSS vector, CWE classification, or reference links, so the specific package, the vulnerable versions, and the resulting impact are all unverified. No public exploit code or proof-of-concept reference is present in the supplied data, and risk cannot be meaningfully quantified from the supplied data. The only prioritization signal available is the vuln.today decision label 'this_month', which places it below immediate-action items.
Member-only content gated by the MembershipWorks plugin for WordPress before 6.17 can be retrieved by unauthenticated visitors through the WordPress REST API, exposing posts and pages the plugin is meant to hide from non-members. The plugin's protected-content filter is only registered during normal front-end request handling, so REST responses return the raw rendered content instead of the stripped version; no authentication or user interaction is required, and only confidentiality of the gated content is affected (assessed CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 8.7). No public exploit code has been identified at time of analysis, and the practical impact depends entirely on whether the site actually uses MembershipWorks content protection; sites in that configuration should plan to update this week.
The CTFd Terraform Provider (ctfer-io/terraform-provider-ctfd) writes the ctfd_team.password attribute into Terraform state as a non-sensitive value in versions 0.1.5 through 2.8.1, so anyone who can read that state file obtains the CTFd team password directly, without needing the state encryption password or any further decryption step. The exposure is access-gated rather than anonymous: the attacker must already be able to read the state (a shared or compromised host, a state file committed to version control or leaked through CI logs, or an exposed remote backend), which is reflected in the assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N and a confidentiality-only impact limited to team passwords. The vendor addressed it in v2.8.2 by marking the schema attribute Sensitive, states that no workaround exists, and no public exploit code has been identified at time of analysis.
Missing OAuth token audience validation in AWS API MCP Server 1.3.0 through 1.5.x lets a local caller reach the server using a bearer token that the identity provider issued to a different application in the same tenant, and then run AWS operations with the AWS credentials configured on the host. The flaw is conditional: it only applies to deployments using the non-default streamable-http transport with OAuth authentication enabled against an operator-nominated identity provider, while the default stdio transport is unaffected. Resulting access is bounded by the permissions of the host's AWS credentials; no public exploit code has been identified at time of analysis, and version 1.6.0 fixes the issue and additionally requires operators to configure an expected token audience or client ID.
Asterisk's REST Interface (ARI) allows a caller holding only read-only credentials to invoke write-capable dialplan functions - most notably FILE() - through the setChannelVar operation, even when live_dangerously is set to no in asterisk.conf, so a supposedly low-privilege ARI user can write files on the PBX host. Affected releases are Asterisk 20.x through 20.20.0, 21.x through 21.12.2, 22.x through 22.10.0, 23.x through 23.4.0, plus Certified Asterisk 20.7-cert10 and 22.8-cert2 and earlier; exposure requires the Asterisk HTTP server to be enabled and reachable and the attacker to already hold valid read-only ARI credentials. No public exploit code was identified at time of analysis, and vendor patches are available in 20.20.1, 21.12.3, 22.10.1, 23.4.1, Certified 20.7-cert11 and Certified 22.8-cert3.
Improper output sanitization in Tanium Enforce 2.9, 2.10, and 3.0 allows a network-reachable attacker to craft malicious output that can lead to limited information disclosure and integrity impact when a legitimate user views or exports affected data (CVSS 7.1). The CVSS vector indicates no required privileges (PR:N) but user interaction (UI:R) is required, and whether injecting the payload itself requires prior authenticated access to Enforce is unverified; no public exploit identified at time of analysis. Tanium has released fixed builds in Enforce 2.9.736, 2.10.778, and 3.0.373, and the vuln.today priority engine rates remediation as 'this_week'.
Improper output sanitization in Tanium Comply allows a remote, unauthenticated attacker to introduce crafted content that is rendered or exported when an authorized operator views the affected output, with the scope change indicating impact beyond the attacker-controlled component, such as the operator's session or an exported file. Only Comply 2.32 before 2.32.263, 2.35 before 2.35.323, and 2.37 before 2.37.326 are affected; confidentiality, integrity, and availability impacts are Low, and the required user interaction is the main limiting factor. No public exploit was identified at the time of analysis, and patched builds are available from Tanium.
HCL Notes Client trusts TLS server certificates chained to eight eMudhra intermediate CAs whose private keys have been compromised, so an attacker positioned on the client's outbound network path can present forged certificates and man-in-the-middle TLS traffic. The flaw is remote and requires no credentials or user interaction (AV:N/PR:N/UI:N), but it is not exploitable from an arbitrary host: the attacker must first achieve an on-path position (AT:P) and the compromised intermediate must still be trusted in the client's chain. Successful abuse yields high confidentiality and integrity impact on the intercepted sessions; the source rates it CVSS 9.1 (4.0) with a vuln.today decision of act_now, and no public exploit code was identified at time of analysis.
HCL Domino Server's outbound TLS client trust accepts certificates chaining to eight eMudhra intermediate CAs whose private keys have been compromised, so an attacker holding a forged server certificate signed by one of those keys can impersonate outbound HTTPS/TLS destinations and intercept or modify Domino's outbound traffic. Affected builds are 2.0.2 FP8, 14.0 through 14.0 FP5, 14.5 and up to 14.5.1 FP1; the CVSS 4.0 base score is 9.1, and the independently assessed 3.1 vector is AV:N/AC:H/PR:N/UI:N with high confidentiality and integrity impact and no availability impact, reflecting that a man-in-the-middle position on the outbound connection path is a prerequisite. No public exploit code was identified at time of analysis, but HCL has issued a vendor fix and the vuln.today decision label is act_now, making this a near-term patching priority.
An out-of-bounds read in WatchGuard Fireware OS's FireCluster synchronization processing lets an attacker who already sits on the cluster interconnect - a compromised cluster peer or an on-path attacker on the sync link - repeatedly crash the cluster synchronization process with crafted traffic, producing a sustained denial of service. Only Fireboxes deployed in a FireCluster high-availability configuration are exposed; stand-alone Fireboxes are not reachable this way, and the CVSS 4.0 base score of 7.2 (HIGH) is driven almost entirely by high availability impact (VA:H) with only limited confidentiality/integrity effect (VC:L/VI:L) from the out-of-bounds read itself. Fixed builds are available from the vendor (12.12.4, 12.5.22 on the 12.0 LTS branch, and 2026.4 on the 2025.1 branch); no public exploit code has been identified at time of analysis and the flaw is not listed as actively exploited.
WatchGuard Fireware OS firewall deployments below 12.5.22, below 12.12.4, and 2025.1 before 2026.4 allow a remote, authenticated attacker with at least read-only Device Monitor privileges and management CLI access to submit a crafted diagnostic command that creates, truncates, or overwrites arbitrary files and modifies kernel parameters with root privileges. The impact is integrity and availability loss rather than confidentiality exposure, and written file content is limited to numeric values; no public exploit was identified at time of analysis.
Sensitive configuration data disclosure in WatchGuard Fireware OS stems from XPath injection in the management SSH authentication process, allowing a remote, unauthenticated attacker who can reach that interface to submit a crafted request and extract configuration data. Affected releases are Fireware OS 2025.1 before 2026.4 and 12.0 before 12.5.22 or 12.12.4; the vendor has released fixes, and no public exploit is identified at time of analysis, with no CISA KEV listing. Exposure is the key risk factor: appliances whose management SSH interface is reachable from untrusted networks are most at risk, while restricting that interface to trusted management networks substantially reduces exposure.
Unauthenticated visitors to Grav 1.7.53.3 through 1.7.53.5 can read stored Clockwork profiler records when the debugger is enabled with the Clockwork provider and Grav sits behind a same-host reverse proxy; those records can include submitted administrator login passwords unless debugger.censored is enabled, plus configuration credentials from system and plugin settings. The flaw is an authorization bypass in Debugger::isDebuggerRequestAuthorized() that trusts a loopback REMOTE_ADDR fallback, so a tokenless request arriving from the local proxy is accepted; direct-server deployments and sites with the debugger disabled are not exposed. It carries CVSS 4.0 8.7 and a this_week priority, making it a credible high-impact information-disclosure case whose real-world risk is strongly gated by deployment topology; no public exploit was identified at time of analysis.
An out-of-bounds write in NVIDIA PhysX (versions 0.0 through 0.4.1.2, all platforms) allows memory corruption that could lead to code execution, data tampering, denial of service, or information disclosure. The CVSS 3.1 vector (7.8, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confines the attack to a local path: no attacker authentication is required, but a legitimate user must open or otherwise process attacker-controlled PhysX content before the write can be triggered, so there is no unauthenticated remote trigger. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor-reported case is prioritized as a this-week item rather than an emergency.
The missing-authentication flaw in NVIDIA NeMo Agent Toolkit 1.0 through 1.8.0 leaves a critical toolkit function without a credential check, giving unauthenticated network attackers a path whose rated consequences include code execution, privilege escalation, data tampering, denial of service, and information disclosure. CVSS is 10.0 with AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, and the vuln.today priority label is act_now. No public exploit identified at time of analysis, and no CISA KEV entry appears in the supplied data; network reachability of the toolkit interface is the main practical exposure constraint, and upgrading past 1.8.0 is the vendor-directed remediation.
SQL injection (CWE-89) in NVIDIA NeMo Agent Toolkit versions 1.4 through 1.6 lets an attacker who can reach the toolkit's input path on the local system inject arbitrary SQL, with potential for data tampering, denial of service, and information disclosure. NVIDIA rates the flaw 8.4 (High) and the assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - unauthenticated with no user interaction, but local, so exploitation requires local reachability of the vulnerable query path rather than network access; that AV:L designation is atypical for SQL injection and is the main factor shaping real-world risk. No public exploit code was identified at time of analysis and the issue does not appear in CISA KEV; per the current decision signal this is a this-week priority rather than an emergency.
Server-side request forgery (SSRF) in NVIDIA TensorRT-LLM 1.3.0rc24 allows an attacker who can reach a local input vector to influence server-side requests and potentially disclose information. NVIDIA rates the issue CVSS 7.1 with a local attack vector (AV:L), no authentication required once that vector is reached, no user interaction, changed scope, and high confidentiality impact only. No public exploit code or active exploitation is identified in the available intelligence, and applicability to versions other than 1.3.0rc24 is not confirmed.
Server-side request forgery (CWE-918) in NVIDIA TensorRT-LLM, reported by NVIDIA at CVSS 7.1, allows an attacker positioned with local or adjacent access to the inference host to make the service issue requests to attacker-influenced destinations, yielding high confidentiality impact and possible data tampering under a scope change. No authentication and no user interaction are required once that local/adjacent access is obtained, and AC:L means no special timing or configuration hurdle is described. There is no public exploit identified at time of analysis and the CVE is not in CISA KEV; the EUVD record lists TensorRT-LLM 1.3.0rc24 as affected and the vuln.today decision label is this_week.
TensorRT-LLM 1.3.0rc24 can load a tokenizer from an attacker-influenced location during KvCacheAwareRouter initialization, allowing inclusion of functionality from an untrusted control sphere (CWE-829). Because the CVSS vector is AV:L with PR:N and UI:N, the untrusted tokenizer must be reachable inside the local loading path, but once it is, no credentials or user interaction are needed; successful exploitation can yield code execution, information disclosure, data tampering, and denial of service. NVIDIA reports the issue with a base score of 8.4, and no public exploit code or confirmed active exploitation was identified at time of analysis. Only deployments that actually use the KvCacheAwareRouter and load tokenizers from unverified sources sit in the exploitable path.
Account enumeration in Rolantis Agentis before 4.8 lets remote unauthenticated attackers infer whether accounts exist by observing differing responses from account-handling functionality. The flaw is a CWE-204 observable response discrepancy with low confidentiality impact and no integrity or availability impact, and it is fully remediated by upgrading to 4.8. No public exploit identified at time of analysis.
TLS certificate verification is disabled by default in Eclipse ioFog Operator 3.8.0 through 3.9.1 on the connections it makes to the Controller API and to an external OIDC issuer, so an unauthenticated on-path attacker can present any certificate and be trusted. That position lets the attacker capture the OAuth client secret in external mode, or the Controller bootstrap admin password in embedded mode with Controller HTTPS enabled, and supply the access token the operator stores for later Controller API calls. Exploitation is gated by the requirement to already sit in the traffic path (CVSS 4.0 AT:P), which is the main limiting factor; vendor priority is act_now, and no public exploit has been identified at time of analysis.
A path-scoped middleware bypass in @fastify/express 4.0.5 through 4.0.8 lets an unauthenticated remote attacker reach handlers protected by Express middleware such as authentication, authorization, or rate limiting. The flaw only manifests when Fastify is started with the non-default routerOptions.ignoreDuplicateSlashes: true and a request is sent with an absolute-form target (e.g. GET http://host/admin/dashboard), which the Fastify router normalizes and dispatches to the scoped handler while the Express layer no longer sees the scoped path. Exploitation is gated by that specific configuration plus reliance on path-scoped Express middleware; no public exploit code or CISA KEV entry was identified in the supplied data, though the vendor rates it CVSS 9.1 and priority guidance is act_now. Fixed in 4.0.9.
Eaton easyE4 firmware versions below 2.46 ships an insufficiently strong password policy (CWE-521), so an attacker who has already obtained a stored password hash - for example by way of CVE-2026-41020 - can mount an offline password-guessing attack and potentially recover the underlying user credentials. The weakness is not exploitable on its own: the vendor's CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.5) reflects the hash-disclosure prerequisite and the dependence on how strong the configured password actually is, and strong, high-entropy passwords resist offline cracking even under the weak policy. No public exploit code has been identified at time of analysis, and the exposure is limited to easyE4 devices that have not been updated to firmware 2.46 or later.
Service account impersonation in Octopus Server stems from inconsistent OIDC token issuer validation, allowing a token minted by a non-legitimate issuer to be accepted as if it came from a legitimate trusted issuer. Deployments are exposed only when OIDC is in use for at least one service account identity, and a attacker must additionally know or guess details of that specific identity and operate a rogue issuer that can mint a matching token - conditions that favour targeted attacks over opportunistic scanning. Vendor CVSS 4.0 score is 8.7; the assessed CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N, C:H/I:H/A:H) likewise reflects high complexity and high confidentiality, integrity and availability impact, and no public exploit has been identified at time of analysis.
Information disclosure in Hitachi HiRDB Server can be triggered by remote, unauthenticated attackers over the network, with high confidentiality impact and no integrity or availability impact (CVSS 7.5). The flaw is classified as an origin validation error (CWE-346) and affects HiRDB Server Version 10 before 10-12-01, HiRDB Server Version 9 through 09-66-22, HiRDB Server with Additional Function Version 9 through 09-66/V, HiRDB Server Version 9(32) through 09-66-22, and HiRDB Server with Additional Function Version 9(32) through 09-66-/V. EPSS is low at 0.21% (10th percentile), there is no CISA KEV confirmation, and no public exploit was identified at time of analysis; the vendor has released a patch.
Unauthenticated remote attackers can establish an RMCP+ session on Supermicro MBD-X12SPI baseboard management controllers running BMC firmware 1.07.20 by sending a request immediately followed by a specially crafted RAKP message, abusing incorrect ordering in the RAKP+ authentication handshake; a session established this way could then be used to execute commands. The flaw is rated CVSS 7.4 (AV:N/AC:H/PR:N/UI:N, high confidentiality and integrity impact, no availability impact) and requires network reachability to the BMC's RMCP+/IPMI 2.0 interface, typically UDP 623. EPSS is 0.45% (39th percentile), the CVE is not listed in CISA KEV and no public exploit has been identified at time of analysis; this is a genuine but second-tier priority rather than a drop-everything emergency.
Impersonation of Moxa OnCell G3150A-LTE Series devices still using factory hard-coded keys is possible for unauthenticated remote attackers who obtain the shared key material, compromising confidentiality and integrity of management communications. EUVD lists version 1.0.0 as affected, and exposure is bounded to units that have not regenerated their cryptographic keys and to attackers able to meet the specific attack precondition and passive user interaction reflected in the assessed vector. No public exploit identified at time of analysis; EPSS is 0.30% (23rd percentile) and the priority is monitor.
Improper certificate validation in Moxa MRC Client 1.0.0 through 4.2.0 allows an unauthenticated attacker who already holds an on-path position between the client and its MRC server to impersonate the trusted server and conduct a man-in-the-middle attack, compromising confidentiality and integrity but not availability. The attack requires that network position and passive user interaction, so it is not a mass-exploitation profile; no public exploit was identified at time of analysis and EPSS is 0.17% (7th percentile). The priority signal is this_week, consistent with a moderate-priority issue rather than an active-exploitation emergency.
Read-level project members in OpenPanel before 3.0.0 can retrieve plaintext integration secrets - Slack bot tokens, incoming-webhook URLs and webhook authorization headers - through the notification.rules tRPC query, which eager-loads integration rows and spreads them into the response without applying the redactIntegration step that integration.get and integration.list enforce. The flaw is access-gated: the attacker needs an existing authenticated account with bare project membership (the lowest role, which cannot create or edit integrations) on a project where a write/admin user has attached at least one integration to a notification rule, and a single query call with no user interaction then exposes those credentials for use against external systems. EPSS is 0.30% (23rd percentile) with no CISA KEV listing, and the vendor advisory contains a benign manual proof-of-concept walkthrough; it is a public PoC reference that is not verified as working exploit code.
OpenPanel before 3.0.0 leaks secrets into standard-output logs through two separate code paths, allowing anyone who can read application, container, CI or centralized logs to recover sensitive data. Database migration startup banners print the full DATABASE_URL and CLICKHOUSE_URL including user-info credentials and credential-like query parameters, and the email fallback path used when both SMTP_HOST and RESEND_API_KEY are unset serializes the recipient address, subject and full template data - which for the password-reset flow includes the reset-token URL. Exploitation is not remote against the service itself: it requires pre-existing read access to log stores plus, in the migration case, that the code-migration command was run, or, in the email case, the non-default double-unset provider configuration and a triggered email flow; no public exploit code is identified at time of analysis and EPSS is low (0.28%, 20th percentile), consistent with a moderate-priority information exposure rather than an emergency.
A local privilege escalation in Apple macOS allows an attacker who can already run code on the host to gain elevated privileges, affecting Macs running macOS versions prior to the fixed releases 26.7.2 (Tahoe), 27.2 (Golden Gate) and 15.8.2 (Sequoia). Apple describes the root cause as a logic issue in a protection mechanism, corrected with improved checks. Exploitation has not been observed and no working exploit code is publicly confirmed; EPSS is low at roughly 0.24% (15th percentile) and SSVC marks exploitation as none and non-automatable, though technical impact is total once local access is achieved. Priority is this_week rather than emergency-grade.
Password-protected private-key exports produced by the Erlang/Elixir `jose` library between 1.10.0 and 1.11.12 are encrypted with a hardcoded, drastically under-strength key-derivation step, so anyone who obtains such an exported blob can crack the export password offline at roughly 300 times less cost than modern guidance intends and recover the full private key. Only the password-based export path is affected (JOSE.JWK.to_der/2, jose_jwk:to_der/2, the PEM equivalents and their _file variants); the attack requires possession of the exported DER/PEM file and succeeds only where the export password is weak or moderate, since a long randomly generated password still resists 2048 PBKDF2 iterations. EPSS is very low (0.06%) and there is no KEV listing, but a public proof-of-concept script accompanies the upstream advisory; a public PoC reference exists and demonstrates parameter extraction plus dictionary recovery, though it is not verified here as working exploit code. The vendor fixed the parameters in 1.11.13, and the CVSS vector indicates no privileges are required (PR:N), with the practical gating factors being blob exposure and password strength rather than any network-reachable interface.
Unauthenticated screen-content disclosure in WolfVision Cynap Pro and Cynap Core Pro devices with vSolution Matrix enabled lets hosts on the same network segment view or capture the current presentation through an unencrypted RTSP/RTP stream. The issue affects versions below 1.78a and is limited to confidentiality; the vendor has released 1.78a, and no public exploit was identified at time of analysis. Exposure is bounded by the non-default Matrix feature requirement and network adjacency.
vLLM before 0.32.0 lets untrusted image bytes pick their own Pillow decoder: ImageMediaIO calls Image.open(BytesIO(data)) without an allowlist and the declared MIME label does not constrain format selection, so an EPS payload submitted as image/png is dispatched to the host's Ghostscript. On hosts whose Ghostscript is affected by CVE-2024-29510 this chains to command execution with the vLLM process's privileges, and on environments running Pillow 12.0.0 through 12.2.0 the same boundary reaches CVE-2026-59203, where a malformed EPS parks media-loading workers until the pool is exhausted. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (8.1 High), reflecting that reachability still depends on an image-capable endpoint, the deployment's API-key and network policy, and a vulnerable host dependency; the reported reproduction covered the loader-level command execution, while the HTTP request path was only source-traced. No public exploit code was identified at time of analysis, and CISA KEV does not list this CVE.
Use of a hard-coded cryptographic key in Johnson Controls Kantech EntraPass before 9.20 enables a padding oracle crypto attack. Exploitation requires local access and low-level privileges (AV:L/PR:L per the vendor CVSS 4.0 vector), so the attacker must already have authenticated or local foothold on the EntraPass system rather than operating as a remote unauthenticated adversary; impact is high across confidentiality, integrity and availability of the affected system. No CISA KEV entry, public exploit code, or EPSS score was provided, and the product's fixed 9.20 release resolves the condition.
Access control bypass in Syncplify Server! before 8.8.0 allows authenticated SFTP users to evade per-path permission overrides by addressing a protected directory with alternate capitalization or its 8.3 short name, enabling file uploads and downloads the override is meant to deny. The flaw is conditional on an existing deny override and on filesystem behavior that accepts alternate case or short names, such as Windows/NTFS; on strictly case-sensitive filesystems without short-name generation the technique is limited. No public exploit was identified at time of analysis, and the vendor has released 8.8.0 as the fix.
Hardcoded static AES key embedded in the TTLock Android app (versions before v9.8.260718) and its associated smart-lock firmware allows an attacker within Bluetooth Low Energy range to capture a pairing exchange and decrypt the per-pairing session key transported during it. With the recovered persistent session key the attacker can forge authenticated BLE commands to unlock the lock, enroll fingerprints or access codes, and carry out administrative actions without authentication or user interaction (CVSS 4.0 8.6, AV:A/AC:L/PR:N/UI:N, VC:H/VI:H). The exposure is bounded by physical proximity to the lock rather than internet reach, and a public PoC reference exists but is not verified as working exploit code; there is no CISA KEV confirmation of active exploitation.
MongoDB Shell (mongosh) versions prior to 2.14.0 bundle a Node.js runtime whose TLS root store includes recoverable eMudhra intermediate CA certificates, so an unauthenticated on-path attacker who can present a certificate chain under that CA could intercept and alter TLS connections when a victim initiates a mongosh TLS session. The issue is CWE-295 improper certificate validation and is rated CVSS 4.0 7.6 (High); exploitation requires a MITM network position plus victim-initiated interaction, and npm-based installs instead depend on the host Node.js runtime. The vendor fix is mongosh 2.14.0 bundling Node.js 24.22.1 or later, and no public exploit identified at time of analysis.
Improper certificate validation in the Erlang HTTP client hackney (1.24.0 through 4.8.x) lets an on-path attacker impersonate a server that an application has pinned to a private certificate authority. Because hackney adds its own {partial_chain, fun hackney_ssl:partial_chain/1} to every verify_peer configuration and OTP honours that callback over a caller-supplied cacerts/cacertfile trust store, a chain ending in any certifi-bundled public root can be accepted as the trust anchor; the attacker still needs a man-in-the-middle position and a publicly trusted certificate for the exact pinned hostname that satisfies the hostname check, so only non-default private-CA pinning deployments are exposed. No public exploit identified at time of analysis and no CISA KEV entry, though the issue is triaged as act_now and fixed in hackney 4.9.0.
Root-level SSH access to WolfVision vSolution Matrix appliances can be obtained by anyone holding the private key that matches the product's shared cryptographic trust configuration, allowing authentication as root on affected devices. Only devices configured as a vSolution Matrix main/master station with the file sharing feature enabled are in scope, so the exposed population is a non-default subset rather than every deployment; the CVSS 4.0 vector (9.2) marks PR:N and UI:N, meaning no legitimate credentials or victim interaction are required once the key is in hand, while AT:P reflects that the key must first be acquired. No public exploit code or confirmed active exploitation appears in the supplied intelligence, but the vuln.today decision label is act_now and the shared nature of the trust material means one recovered key can potentially be replayed against multiple affected master stations.
HAVELSAN Liman MYS releases from 2.3.4-1124 up to but not including 2.3.5-1131 contain a weak forgotten-password recovery mechanism (CWE-640) that lets a network attacker abuse the account-recovery workflow to take over a targeted account, with high confidentiality and integrity impact and no effect on availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, base 8.1) indicates the flaw is network-reachable and low complexity and needs no attacker credentials, but it is not fully autonomous because a victim must perform some recovery-related action (UI:R); the exact weakness in the recovery flow is not described in the available sources. No CISA KEV entry and no exploit code reference were provided, so no public exploit identified at time of analysis; TR-CERT rates it for remediation within this week.
Case-sensitivity defects in MISP Guard's feed-distribution policy checks allow an authenticated MISP event creator to slip events past configured TLP taxonomy, allowed-tag, blocked-attribute-category and blocked sharing-group rules simply by changing the letter case of a tag, category or UUID string, with the result that threat-intelligence data the operator meant to restrict is still forwarded to feed consumers. Only deployments running misp-guard 1.3 or earlier that actually rely on these allow/block policies are exposed, and the impact is confidentiality-only - no integrity or availability effect. No public exploit code was identified at time of analysis; the vendor has published an upstream fix commit (9868b1d9) that normalizes case on both sides of every affected comparison and adds regression tests reproducing the bypass.
Out-of-bounds reads in the SOEM EtherCAT master library (2.0.0 and earlier) let a malicious or compromised device on the same EtherCAT segment make the master read past the end of allocated buffers, disclosing memory contents or crashing the master process. No authentication or user interaction is required, but the attack surface is confined to the adjacent Layer-2 fieldbus segment - typically an isolated OT control network rather than anything internet-routable. No public exploit code or confirmed in-the-wild exploitation is identified in the available data, and the vuln.today decision label is this_week, reflecting a genuine but bounded industrial/OT priority rather than an internet-wide emergency.
CRLF injection in the Dnsmasq configuration path of Oray Pugongying X5 Pro 7.6.1 lets a user who already holds administrative access to the router's management interface inject newline-delimited Dnsmasq directives through the DHCP lease-time (rent_time) parameter, corrupting the device's DNS/DHCP behaviour and enabling configuration tampering and potential information disclosure. Exploitation is remote over the network with no user interaction, but the CVSS vector carries PR:H - an attacker must first obtain admin credentials, which is the primary limiting factor, so this is not reachable by an unauthenticated outsider. A public PoC reference (a Notion write-up titled 'Dnsmasq Directive Injection Through DHCP Lease Time') exists but is not verified as working exploit code; the vendor was contacted and did not respond, so no fixed version is available, and the disclosure is tracked for remediation this week.
Out-of-bounds read in Fuji Electric V-SFT can be triggered when a user opens a crafted V7 project file, potentially exposing information or enabling arbitrary code execution on the affected system. The flaw is local and requires user interaction-the victim must open the malicious file-and no privileges are required, so social engineering is the primary attack vector. This is a moderate-priority, not emergency, issue; no public exploit identified at time of analysis.
Opening a crafted V7 project file in Fuji Electric/Hakko V-SFT can cause an out-of-bounds read in VS6EditData!CDataRomErrorCheck::CheckSymbolMacroParam, potentially leading to information exposure or arbitrary code execution in the context of the user running the application. The issue is assessed as high severity (CVSS 4.0 8.4) with a local, user-assisted file-open path, and affected-product data uses wildcard CPE version fields rather than a specific version range. No CISA KEV designation is present in the supplied data, and no public exploit was identified at time of analysis; the independent assessment rates it this-week priority, not emergency-grade.
Opening a crafted V7 project file in Fuji Electric V-SFT can trigger an out-of-bounds read in the macro-command check path, leading to information disclosure or arbitrary code execution on the workstation running the product. The flaw is local to the host, requires no attacker privileges, and depends on the victim opening the malicious file, so exploitation is constrained by file delivery and user interaction rather than remote network access. No public exploit was identified at time of analysis, and the vendor and JVN advisories are the available sources for affected-version and update details.
Opening a crafted V7 project file in Fuji Electric's V-SFT screen-creation/engineering software can drive an out-of-bounds read in the VS6MemInIF!set_temp_type_default routine, exposing process memory and, per the vendor, potentially enabling arbitrary code execution on the workstation running the application. Rated 8.4 (CVSS 4.0, CWE-125) and tracked by JPCERT/CC, the issue is conditional rather than mass-exploitable: the attack vector is local and the victim must actively open an attacker-supplied project file, while no authentication or special privileges are required for the payload to be processed. No public exploit identified at time of analysis, no CISA KEV listing, and the vendor advisory plus JVN note are the primary sources for version and fix guidance.
Out-of-bounds read in Fuji Electric V-SFT's VS6ComFile!load_gr_item routine can expose memory contents or enable arbitrary code execution when an operator opens a crafted V7 file. The attack is local and requires user interaction: an attacker must deliver a malicious V7 file and convince a V-SFT user to open it. No public exploit identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV).
An out-of-bounds write in Fuji Electric's V-SFT screen-creation software (also published under Hakko Electronics) is triggered when a user opens a crafted V7 project file, allowing memory corruption that can disclose information or lead to arbitrary code execution on the engineering workstation running the tool. Exploitation is local and interaction-gated: the attacker must first deliver the malicious V7 file to a victim who then opens it in V-SFT, so there is no network-facing attack surface and no credentials are needed for the file itself to carry the payload. No public exploit code and no confirmed active exploitation (CISA KEV) are indicated in the available intelligence, but the JVN-published issue is rated high severity and prioritized for remediation this week.
Opening a crafted V7 project file in Fuji Electric V-SFT (the HMI screen-configuration and programming software, listed in the CPE as Fuji Electric / Hakko Electronics V-SFT) overflows a stack buffer and can result in information exposure or arbitrary code execution with the privileges of the user running the application. The attack is local rather than network-reachable and requires the victim to actively open the malicious file, so compromise depends on social engineering a legitimate V-SFT user; no authentication is required of the attacker. No public exploit code has been identified at time of analysis, and the vulnerability is tracked by JPCERT/CC under JVNVU96549652 with a priority of 'this_week' rather than emergency-level.
Improper Secure Boot signature verification in Yoosee GM8135S Camera 21.00.01.36 lets a local attacker who already holds high privileges get a manipulated firmware image accepted (CWE-347), undermining firmware trust and enabling tampering or persistence. The CVSS 4.0 base score is 8.4, but the attack path is local and requires existing privileged access, with no remote or unauthenticated vector described; the exact trigger is not detailed in the available sources. A public PoC reference exists; it is not verified as working exploit code, and no CISA KEV entry confirms active exploitation; the disclosure is prioritized this_week.
LDAP credential exposure in Snipe-IT 8.6.2 and earlier lets an on-path attacker capture service-account and end-user passwords in cleartext. Ldap::connectToLdap() called ldap_start_tls() and discarded the boolean result, so when TLS negotiation fails or a man-in-the-middle answers the StartTLS extended request with a 'Protocol error', the subsequent ldap_bind() sends credentials unencrypted while users see a normal, silent login. Only deployments with LDAP authentication enabled and TLS configured (ldap_enabled=1, ldap_tls=1) plus an attacker-reachable network path to the LDAP server are exposed; no public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, though the vendor advisory publishes the exact code path and trigger.
SiYuan 3.6.0 through 3.8.6 accepts and persists the networkServeTLS administrator setting but never enforces it, so the kernel port continues answering plain HTTP with full API access in cleartext while also serving HTTPS on the same port. An operator who enables the toggle believes kernel traffic is encrypted, yet a network-adjacent attacker can sniff the login flow - including the access auth code - and the session cookie, which is issued without the Secure attribute while HTTPS responses omit HSTS, allowing session hijack against the kernel API. Exploitation requires a network-adjacent sniffing position and the operator having enabled the setting, which is why the flaw is rated for adjacency and high complexity rather than internet-wide exposure; a public PoC reference exists describing the verification steps, and it is not confirmed as working exploit code. A vendor fix is available in v3.8.7.
rotki before 1.44.2 derives the encryption key for its premium cloud backup/sync feature as a single unsalted SHA-256 hash of the user password, so anyone who obtains an uploaded backup blob can run offline, GPU-parallel password guessing against it and decrypt the database it holds - exchange API keys, secrets, wallet addresses and transaction history. The attack is unauthenticated and requires no user interaction once the blob is in hand, and only users of the premium sync/backup feature are affected. There is no KEV entry and no public exploit identified at time of analysis, though the CVSS 4.0 score of 8.2 signals high confidentiality impact; the vendor addressed the issue in rotki 1.44.2.
CPython's ssl module validates TLS certificate chains that anchor to known-compromised eMudhra CA certificates, so anyone holding that CA's key material can impersonate arbitrary TLS servers to unpatched Python clients. Every Python application that relies on the default verification path (ssl.create_default_context() or an SSLContext without its own OCSP/CRL checking) is affected, which is CPython's default behaviour; the fix adds a hard-coded denylist of distrusted certificates enforced regardless of SSLContext policy. Exploitation is targeted rather than opportunistic, requiring the compromised CA key plus a man-in-the-middle or server-impersonation position against the victim's connection; no public exploit identified at time of analysis, and the vendor-tracked priority label is act_now.
MongoDB Compass versions prior to 1.53.1 ship an Electron runtime whose bundled TLS root store still contains the compromised, recoverable eMudhra intermediate CA certificates, so a party holding a certificate chained to those intermediates can be treated as trusted by the application. Because the attacker must also occupy a man-in-the-middle position on the network path and induce a user to initiate a Compass connection through it, impact is confidential and integrity-related (VC:H/VI:H) rather than an unauthenticated remote take-over. The vendor resolves the issue in Compass 1.53.1, which bundles Electron 44.9.1; no public exploit code or active exploitation has been reported, and the issue is prioritised as this week rather than an emergency.
Postiz (gitroomhq/postiz-app) before v2.25.1 allows any signed-in user to invoke arbitrary internal integration methods through the POST /integrations/function endpoint, using a connected channel's token as the first argument. By setting that token to a filesystem path, an attacker can read server files such as the application environment, exposing the session-signing secret, database address and third-party service credentials; a separate internal helper can terminate the backend process with one request. Self-registration is open by default, so an external attacker can obtain the required low-privilege account without any action by another user, and no public exploit code has been identified at time of analysis.
Account takeover in OpenReception's appointment booking software before 2.2.1: whoever holds a pending invite token can replay it during its thirty-minute validity window and receive a fresh passkey-registration bootstrap credential, letting them enrol their own passkey on the invited account and, for staff or tenant-admin invites, reach the tenant context tied to that account. The endpoint is reachable without authentication over the network and rated CVSS 7.4, although the attacker must first obtain the emailed token and act before the legitimate invitee completes passkey setup. No confirmed active exploitation (CISA KEV) is reported; the vendor advisory publishes reproduction steps as a public PoC reference, and the issue is fixed in version 2.2.1.
Host-header injection in OpenReception's confirmation-email path lets unauthenticated remote attackers redirect a pending invitee's one-time confirmation token to an attacker-controlled host and then claim that account before the legitimate invitee ever onboards. The unauthenticated POST /api/auth/resend-confirmation rotates a pending invitee's token and builds the emailed link from the request Host with no allowlist, so a single request carrying a spoofed Host and the victim's email address produces a genuine onboarding email whose only link points at the attacker. Because the account is claimed first and bound to an attacker-registered WebAuthn passkey, the attacker gains a full session in the invited role (staff or tenant admin), with read and potentially modify access to client and appointment data; a public proof-of-concept package is attached to the advisory and reported to demonstrate the flow end-to-end against the official image, though it is not independently verified as working exploit code. Exploitation requires the victim to click the poisoned link (UI:R) and depends on the front proxy forwarding an arbitrary Host, which the stock Caddy catch-all does.
Authenticated remote code execution in OpenCATS versions prior to 0.10.0 lets an administrator-level user with Settings-module access inject PHP syntax into config.php through the Professional License key field, producing persistent arbitrary code execution as the web server user. The flaw is gated by the PR:H metric in the CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H, base 7.2 High): the attacker must already hold an administrator account with permission to update the Professional License configuration, and config.php must be writable by the web server process for the write-based path to succeed. Successful exploitation gives full confidentiality, integrity and availability impact over candidate, contact, company, job order and user data, and the vendor states unauthenticated exploitation or exploitation by users without Settings access is not established; no public exploit code has been identified at time of analysis and the issue is fixed in v0.10.0.
MongoDB Database Tools builds prior to 100.20.0 (specifically 100.19.0, compiled with Golang 1.26.8) will accept TLS server certificates chaining to the eMudhra CA, which Go's crypto/x509 denylist only began rejecting in Golang 1.27.3. An attacker holding a man-in-the-middle position on the network path and a usable eMudhra-issued certificate for the targeted hostname could therefore intercept DB Tools connections to a MongoDB server and read or alter traffic; the victim must actively initiate the connection. No public exploit code or confirmed active exploitation was identified at the time of analysis, and the flaw is resolved in DB Tools 100.20.0.
Authenticated SQL injection in OpenCATS prior to 0.10.0 lets any logged-in user who can reach the home Calls DataGrid (home:CallsDataGrid) or activity DataGrid (activity:ActivityDataGrid) rewrite the date-filter SQL and read data beyond their intended scope, including user accounts, candidate records, contacts, company records, job orders and activity history. The flaw sits in the request-controlled period, startDate and endDate parameters, which are concatenated into SQL date comparisons in modules/home/dataGrids.php and modules/activity/dataGrids.php without validation or escaping; a valid OpenCATS login is required and unauthenticated exploitation is not established. The confidentiality impact dominates (the data exposure is the practical harm), and no public exploit code was identified at time of analysis; the vendor-released patch is OpenCATS 0.10.0.
AnkiMCP Server addon 0.20.0 and earlier ships a FastMCP Streamable HTTP listener enabled by default on 127.0.0.1:3141 with DNS-rebinding protection globally disabled, so a malicious web page that rebinds a hostname to loopback can complete MCP `initialize`, enumerate tools with `tools/list`, and dispatch `tools/call` against the victim's Anki collection without any bearer token, API key, session secret, or Host/Origin allowlist check. Because the flaw needs the victim to browse an attacker-controlled page while Anki and the listener are live, and depends on successful rebinding and timing (CVSS 3.1 AV:N/AC:H/PR:N/UI:R/S:C), the practical window is conditional rather than continuous; the vendor GHSA includes a reproduction harness that reaches real MCP tool dispatch with substituted Anki bridge responses, but it is not verified as working exploit code that modifies a real collection. There is no CISA KEV entry and no confirmed active exploitation at time of analysis; default impact is unauthorised read of the collection plus non-destructive note/deck creation and updates, since destructive tools stay hidden unless `enabled_destructive_tools` is opted into.
Unauthenticated attackers can leak password hashes, email addresses, and post metadata from WordPress sites running Bricks Theme 2.4.3 and earlier by injecting dynamic-data tags through the query_result REST endpoint. The flaw is remotely exploitable with no authentication or user interaction (CVSS 7.5, confidentiality-only impact), and the vendor has released Bricks 2.4.4 as the fix. No CISA KEV entry is present and no public exploit was identified at time of analysis, but the unauthenticated confidentiality impact makes this a high-priority update.
Stale authentication state in GraphQL Tools' legacy WebSocket executor lets a later caller inherit a previous caller's downstream identity: the closure-scoped executorConnectionParams object retains per-request extensions.connectionParams after cleanupWebsocket tears down the socket, and the retained keys are replayed in a subsequent connection_init payload. Only applications that reuse a single buildWSLegacyExecutor instance across different authorization contexts are exposed - most notably gateway, schema-stitching, or GraphQL Mesh deployments that pass per-user Authorization or tenant values through extensions.connectionParams; an anonymous or lower-privileged request that omits the sensitive key can then have its downstream subscription executed under the earlier user's token, though the credential itself is never disclosed. Applications that build a fresh executor per request, including the in-repository UrlLoader wrapper, are not affected; exploitation is remote and unauthenticated from the library's perspective but gated by the shared-executor architecture, and no public exploit code was identified at time of analysis.
Server-side request forgery in KServe lets any principal that holds namespace-scoped create or update rights on InferenceService custom resources point the model-serving controller at an attacker-chosen destination: the crafted `storageUri` is fetched by the `storage-initializer` init container, which issues arbitrary outbound HTTP/HTTPS requests from inside the cluster. The result is information disclosure rather than data corruption - successful abuse can expose the node's cloud IAM role credentials through instance-metadata endpoints or reach internal-only cluster services that the tenant namespace could not otherwise touch. Exploitation is access-gated, requiring the attacker to already hold those InferenceService RBAC permissions (CVSS PR:L, scope-changed, confidentiality-only), and no public exploit was identified at time of analysis; the vendor rates it this_week, not an emergency.
OAuth token revocation in WSO2 Identity Server fails to invalidate access and refresh tokens for accounts whose usernames contain mixed-case characters when the deployment pairs a case-insensitive user store with a case-sensitive identity database. An authenticated attacker (PR:L) who already holds a valid, unexpired token for such an account can keep using it for actions that should have been blocked after a revocation-triggering lifecycle event, bounded by the token's natural expiry. Affected deployments are a non-default configuration subset, the trigger requires that specific store/database mismatch plus a mixed-case username, and no public exploit has been identified at time of analysis; the input 7.4 score assumes AC:L, whereas the assessed vector uses AC:H, so real-world risk is materially lower than the headline number suggests.
Filesystem sandbox escape in Wasmtime's wasmtime-wasi crate allows a sandboxed guest on macOS or FreeBSD to move host directories accessible to the host process into its own sandbox and then read or write their contents, defeating the runtime's core isolation guarantee. Affected releases are 36.0.17 and earlier, 37.0.0 through 48.0.5, and 49.0.0 through 49.0.2; Linux and Windows hosts are explicitly not affected. Exploitation requires a guest already executing with write access to at least one sandbox directory, and no public exploit code has been identified at time of analysis - though the vendor notes the bug affects every published version as of the advisory and provides no workaround other than upgrading.
Coder deployments that run workspace agents on Google Compute Engine with GCP instance-identity authentication accept replayed GCE identity tokens because the POST /api/v2/workspaceagents/google-instance-identity endpoint never validated the token's audience claim, allowing an attacker holding an unexpired format=full token minted for a different relying party to exchange it for that workspace agent's session token. The resulting agent token stays valid until the workspace's next build, well past the identity token's roughly one-hour lifetime. Affected releases are those before 2.29.21 and the 2.30.0-2.34.11, 2.35.0-2.35.8, 2.36.0-2.36.6 and 2.37.0-2.37.3 ranges, fixed in 2.38.0 and the listed backports; the flaw is unauthenticated per the supplied vector (PR:N) but conditional, since the attacker must already possess a genuine, unexpired token from a VM backing an agent on the workspace's latest build, and no public exploit was identified at time of analysis. The vendor advisory credits independent reports from a customer security team and an external researcher.
n8n versions before 2.43.5 and 2.44.x before 2.44.1 allow an authenticated member who can create and run workflows to bypass project boundaries and list, read, modify, and delete Data Table rows in all projects by supplying a crafted workflow ID such as __proto__. The flaw is a prototype-pollution-style authorization bypass in the in-memory workflow owner-project cache, rated 8.7 with PR:L in the CVSS vector, so exploitation requires a member account and the Data Tables module. Vendor fixes are available in 2.43.5 and 2.44.1; no public exploit was identified at time of analysis, and KEV status was not provided.
Prototype pollution in the Highcharts JS charting library (6.1.0 up to 11.4.9, 12.0.0 up to 12.6.1, and 13.0.0 through 13.0.2) lets an attacker who controls a chart's series.keys array and the matching per-point data write arbitrary named properties onto Object.prototype using dot-separated paths such as '__proto__.polluted' or 'constructor.prototype.alsoPolluted'. No user interaction is required beyond rendering the chart, and because the injected properties are visible to all JavaScript on the page rather than only to the chart - reflected as scope-changed (S:C) in both the vendor CVSS 4.0 vector and the independently assessed CVSS 3.1 vector - concrete harm depends on what other page code later reads. Exploitation is contextual: series.keys is normally a static developer-defined configuration, so only applications that route untrusted input into both keys and point data are exposed, and the advisory links a live JSFiddle demonstration of the pollution (a public PoC reference exists; it is not verified as working exploit code). There is no CISA KEV entry and no confirmed active exploitation; the vuln.today decision label is 'this_week', a moderate context-dependent priority rather than an emergency.
Prototype pollution in Highcharts JS 13.0.0 through 13.0.2 lets attacker-controlled series point data write integer-keyed properties onto Object.prototype and the Object constructor, which then surface in out-of-range index reads and for...in enumeration of every object on the page. No user interaction is required beyond rendering a chart built from those point objects, and the injected properties persist after the chart is constructed; the practical consequence runs from broken rendering to whatever the consuming application does with attacker-supplied inherited values. The issue is fixed in 13.1.0, is not listed in CISA KEV, and no working exploit code is confirmed - the vendor advisory does publish a live JSFiddle demo for testing, and the current priority label is this_week rather than an emergency call.
Jenkins core 2.587 and earlier, along with LTS 2.580.1 and earlier, are covered by the 2026-10-28 Jenkins security advisory, and the EUVD record for this CVE points to advisory section SECURITY-4206; that section's text is not included in the material supplied here, so the specific defect, its trigger, and its exact permission prerequisites for CVE-2026-117625 cannot be confirmed from available data. What is confirmed for the advisory as a whole is that every listed issue requires an authenticated, non-anonymous Jenkins user holding a permission such as Overall/Read, Item/Configure, View/Configure, or Agent/Configure, and that several of the batch lead to remote code execution or stored cross-site scripting on the controller. No public exploit code or confirmed active exploitation is identified in the supplied sources, and the priority decision remains awaiting data, so treatment should be driven by the confirmed availability of the 2.588 / LTS 2.580.2 fix rather than by an exploitation signal.
Jenkins core 2.587 and earlier, along with LTS 2.580.1 and earlier, are affected by CVE-2026-117619, one of eight security issues addressed in the Jenkins advisory dated 2026-10-28 and fixed in Jenkins 2.588 and LTS 2.580.2. The per-CVE description for this specific identifier is not present in the supplied advisory excerpt, so neither the vulnerability class nor the precise attacker impact can be stated from the available data - only the affected scope and the fixed versions are confirmed. Every other entry in the same advisory requires an authenticated user holding specific Jenkins permissions (Overall/Read, Item/Configure, View/Configure, Agent/Configure, Item/Create) rather than anonymous access, which suggests a similar privilege prerequisite is likely here, but that remains unverified. No public exploit code and no CISA KEV entry are associated with this identifier in the supplied intelligence, and the priority decision is awaiting_data.
Arbitrary file read on the Jenkins controller affects Jenkins 2.587 and earlier and Jenkins LTS 2.580.1 and earlier when an authenticated user with both Item/Create and Item/Configure renames an item whose directory contains a symbolic link, causing the copy fallback to follow the link and disclose file contents. The direct impact is confidentiality loss (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N); disclosed secrets can enable a contingent escalation to remote code execution. No public exploit identified at time of analysis, and the supplied data contains no EPSS score or CISA KEV entry.
CVE-2026-117618 is one identifier in the Jenkins Security Advisory 2026-10-28 bundle, which fixes multiple Jenkins core vulnerabilities affecting Jenkins 2.587 and earlier and LTS 2.580.1 and earlier; the vendor-released patch is Jenkins 2.588 and LTS 2.580.2. The advisory excerpt available for this analysis enumerates SECURITY-4125/CVE-2026-117612 through SECURITY-4249/CVE-2026-117622 but does not include a description mapping SECURITY-4125 through SECURITY-4249 to the -117618 identifier, so the specific vulnerable component, attack vector, and required permissions for this CVE are unverified and must be read from the advisory page. No CISA KEV listing, no EPSS score, and no public exploit code were present in the supplied data, so exploitation status is no public exploit identified at time of analysis, and the vuln.today decision label remains awaiting_data. For the sibling issues in the same advisory, exploitation requires an authenticated foothold with configuration privileges (Overall/Read plus a non-anonymous account, Item/Configure, Agent/Configure, or Item/Create depending on the issue), and several of those siblings can lead to remote code execution on the controller.
Arbitrary file write on the Jenkins controller is possible in Jenkins 2.587 and earlier and LTS 2.580.1 and earlier when an authenticated user with Item/Configure permission archives artifacts concurrently, such as from parallel Pipeline branches. The extraction code checks for symbolic links only before creating parent directories and permits symlinks in artifacts to replace existing files or empty directories, leaving a race before the final write; successful exploitation can overwrite files outside the intended directory and lead to remote code execution. No public exploit was identified at time of analysis, and the vendor fixed the issue in Jenkins 2.588 and LTS 2.580.2.
Apache Kafka brokers that run SASL/OAUTHBEARER with the default DefaultJwtValidator and leave sasl.oauthbearer.jwks.endpoint.url unset silently fall back to a validator that performs no JWT signature, algorithm, or issuer checks, allowing unauthenticated remote attackers with listener reachability to forge tokens for arbitrary principals, including configured superusers, and gain full cluster access. The flaw is a residual of CVE-2026-33557 and only affects brokers in this specific OAUTHBEARER-without-JWKS-URL configuration with no custom verification key resolver; brokers that set the JWKS URL verify signatures and are not affected. No CISA KEV listing or public exploit code is identified in the available data, no public exploit identified at time of analysis, and no EPSS score is provided.
Integer underflow in Juniper Networks Session Smart Router's DhcpMessageDecoder allows an attacker on the adjacent network to cause information disclosure and denial of service by sending a malicious DHCP reply. The issue affects Session Smart Router deployments where the router processes DHCP replies as a client or relay on an attacker-reachable Layer 2 segment; the CVSS 3.1 vector is AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H, so no authentication or user interaction is required but exploitation is confined to local-segment presence. No public exploit code or active exploitation is identified in the provided data, and the priority label is this_week.
Authorization bypass in mongodb/laravel-mongodb can let an authenticated user with basic privileges read, change, or delete documents that an application intended to withhold when it relies on an absence-of-related-record relationship check. The flaw is a type-handling error in relationship query building (CWE-843) that silently compiles that check with an identifier of the wrong data type; exploitation is conditional on the application using this authorization pattern and on a triggering identifier type, matching the assessed CVSS:3.1 vector AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. No public exploit was identified at time of analysis, and the vendor references release 5.12.0.
Unauthenticated information disclosure in the Supsystic Contact Form WordPress plugin (all versions through 1.10.5) lets remote attackers retrieve sensitive data that the plugin embeds in the data it sends. The CVSS 3.1 score of 7.5 reflects network-only access with no privileges and no user interaction, high confidentiality impact, and no integrity or availability effect; vuln.today triage rates it this_week, i.e. moderate rather than emergency priority. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the precise endpoint, parameter, or output path that exposes the embedded data is not described in the available sources.
Unauthenticated remote file upload and direct retrieval weaknesses in HCL BigFix AEX allow attackers to place files on the server and then access or download uploaded content without proper authorization. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) shows the issue is reachable over the network at low complexity with no authentication or user interaction, and the supplied CPE identifies the affected product without a narrower version boundary. No CISA KEV entry or public exploit was identified at time of analysis, but the issue is assessed as a credible high-priority item to address this week rather than an emergency.
Remote code execution in HCL BigFix AEX is reachable over the network with low attack complexity, but the CVSS vector requires a high-privilege account (PR:H), so an attacker must already hold privileged access to the product before exploiting the code-injection flaw (CWE-94). The scope change (S:C) indicates that successful exploitation can affect resources beyond the vulnerable component, with high confidentiality, integrity, and availability impact. No public exploit has been identified at the time of analysis, and the vendor advisory KB0134281 is the primary reference; the vuln.today decision label is act_now.
Acronis Cyber Protect 17 on Linux and Windows before build 42587 can expose sensitive information and allow manipulation of protected resources through improper token validation, reachable over the network without authentication but requiring high attack complexity. Vendor CVSS is 7.4, and the this_week decision label makes this a moderate-priority remediation rather than an emergency. No public exploit code was identified at time of analysis.
Token forgery in Acronis Cyber Protect 17 before build 42587 can allow remote, unauthenticated attackers to bypass authentication or authorization, resulting in sensitive information disclosure and data manipulation on Linux and Windows installations. The CVSS 3.0 score is 7.4 with high attack complexity (AC:H), indicating non-trivial preconditions; no public exploit identified at time of analysis and no CISA KEV entry is present.
Remote, unauthenticated attackers can obtain exposed credentials from Dell PowerProtect Data Domain appliances running Feature Release 7.7.1.0 through 8.8, LTS2024 7.13.1.0 through 7.13.1.80, LTS2025 8.3.1.0 through 8.3.1.40, or LTS2026 8.6.1.0 through 8.6.1.20 because hard-coded cryptographic key material is present in the affected firmware. Exploitation requires network reachability to the appliance and results in access bounded by the privileges of the compromised user, not guaranteed administrative control. No public exploit code or CISA KEV entry is identified in the available data, but the 9.8 CVSS score and act_now priority reflect a genuine high-priority credential-exposure risk; the exact key-to-credential mechanism is not described.
Privilege escalation in Dell PowerProtect Data Domain Feature Release 7.7.1.0 through 8.8 allows an authenticated, low-privileged remote attacker to obtain high-impact confidentiality, integrity, and availability effects on the appliance. Dell has released a vendor fix in 8.9.0.0; no public exploit has been identified at time of analysis, and the issue warrants prompt remediation rather than emergency action.
AXIS Camera Station Pro and Camera Station 5 weakly encrypt database backups (CWE-326), so an attacker who obtains a backup file can attack it offline and recover the credentials stored inside. The exposure covers backups created before the fix and the extra recovery backup that Camera Station automatically creates when the update is applied; the CVSS 7.1 vector (AV:L/PR:L, UI:N) means local access to the backup artifacts and low privileges are required, not remote reachability. No public exploit code or confirmed active exploitation was identified at time of analysis, and updating alone does not remove already-exposed backups.
Information disclosure in the Animated Text Block WordPress plugin (versions up to and including 1.2.6) allows an authenticated user with Contributor-level access or higher to read the rendered content of any published post on the site. The 'animated-text' shortcode handler accepts an attacker-supplied post ID and, in its 'publish' branch, renders the post without any capability check and without verifying that the post type is the plugin's own custom post type or is otherwise viewable - so posts in non-public custom post types (public=false, show_in_rest=false) that WordPress normally hides from direct URLs and the REST API can be disclosed. Impact is confidentiality-only (no modification or denial of service), the target post must be in 'publish' status, and no public exploit code or PoC reference is present in the available sources; the vuln.today decision label is this_week.
CVE-2026-109411 is tracked through the Ubuntu vendor channel, which indicates the affected code is a package distributed by Ubuntu, but the supplied record carries no description, CVSS vector, CWE classification, or reference links, so the specific package, the vulnerable versions, and the resulting impact are all unverified. No public exploit code or proof-of-concept reference is present in the supplied data, and risk cannot be meaningfully quantified from the supplied data. The only prioritization signal available is the vuln.today decision label 'this_month', which places it below immediate-action items.
Member-only content gated by the MembershipWorks plugin for WordPress before 6.17 can be retrieved by unauthenticated visitors through the WordPress REST API, exposing posts and pages the plugin is meant to hide from non-members. The plugin's protected-content filter is only registered during normal front-end request handling, so REST responses return the raw rendered content instead of the stripped version; no authentication or user interaction is required, and only confidentiality of the gated content is affected (assessed CVSS:3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, 8.7). No public exploit code has been identified at time of analysis, and the practical impact depends entirely on whether the site actually uses MembershipWorks content protection; sites in that configuration should plan to update this week.
The CTFd Terraform Provider (ctfer-io/terraform-provider-ctfd) writes the ctfd_team.password attribute into Terraform state as a non-sensitive value in versions 0.1.5 through 2.8.1, so anyone who can read that state file obtains the CTFd team password directly, without needing the state encryption password or any further decryption step. The exposure is access-gated rather than anonymous: the attacker must already be able to read the state (a shared or compromised host, a state file committed to version control or leaked through CI logs, or an exposed remote backend), which is reflected in the assessed vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N and a confidentiality-only impact limited to team passwords. The vendor addressed it in v2.8.2 by marking the schema attribute Sensitive, states that no workaround exists, and no public exploit code has been identified at time of analysis.
Missing OAuth token audience validation in AWS API MCP Server 1.3.0 through 1.5.x lets a local caller reach the server using a bearer token that the identity provider issued to a different application in the same tenant, and then run AWS operations with the AWS credentials configured on the host. The flaw is conditional: it only applies to deployments using the non-default streamable-http transport with OAuth authentication enabled against an operator-nominated identity provider, while the default stdio transport is unaffected. Resulting access is bounded by the permissions of the host's AWS credentials; no public exploit code has been identified at time of analysis, and version 1.6.0 fixes the issue and additionally requires operators to configure an expected token audience or client ID.
Asterisk's REST Interface (ARI) allows a caller holding only read-only credentials to invoke write-capable dialplan functions - most notably FILE() - through the setChannelVar operation, even when live_dangerously is set to no in asterisk.conf, so a supposedly low-privilege ARI user can write files on the PBX host. Affected releases are Asterisk 20.x through 20.20.0, 21.x through 21.12.2, 22.x through 22.10.0, 23.x through 23.4.0, plus Certified Asterisk 20.7-cert10 and 22.8-cert2 and earlier; exposure requires the Asterisk HTTP server to be enabled and reachable and the attacker to already hold valid read-only ARI credentials. No public exploit code was identified at time of analysis, and vendor patches are available in 20.20.1, 21.12.3, 22.10.1, 23.4.1, Certified 20.7-cert11 and Certified 22.8-cert3.
Improper output sanitization in Tanium Enforce 2.9, 2.10, and 3.0 allows a network-reachable attacker to craft malicious output that can lead to limited information disclosure and integrity impact when a legitimate user views or exports affected data (CVSS 7.1). The CVSS vector indicates no required privileges (PR:N) but user interaction (UI:R) is required, and whether injecting the payload itself requires prior authenticated access to Enforce is unverified; no public exploit identified at time of analysis. Tanium has released fixed builds in Enforce 2.9.736, 2.10.778, and 3.0.373, and the vuln.today priority engine rates remediation as 'this_week'.
Improper output sanitization in Tanium Comply allows a remote, unauthenticated attacker to introduce crafted content that is rendered or exported when an authorized operator views the affected output, with the scope change indicating impact beyond the attacker-controlled component, such as the operator's session or an exported file. Only Comply 2.32 before 2.32.263, 2.35 before 2.35.323, and 2.37 before 2.37.326 are affected; confidentiality, integrity, and availability impacts are Low, and the required user interaction is the main limiting factor. No public exploit was identified at the time of analysis, and patched builds are available from Tanium.
HCL Notes Client trusts TLS server certificates chained to eight eMudhra intermediate CAs whose private keys have been compromised, so an attacker positioned on the client's outbound network path can present forged certificates and man-in-the-middle TLS traffic. The flaw is remote and requires no credentials or user interaction (AV:N/PR:N/UI:N), but it is not exploitable from an arbitrary host: the attacker must first achieve an on-path position (AT:P) and the compromised intermediate must still be trusted in the client's chain. Successful abuse yields high confidentiality and integrity impact on the intercepted sessions; the source rates it CVSS 9.1 (4.0) with a vuln.today decision of act_now, and no public exploit code was identified at time of analysis.
HCL Domino Server's outbound TLS client trust accepts certificates chaining to eight eMudhra intermediate CAs whose private keys have been compromised, so an attacker holding a forged server certificate signed by one of those keys can impersonate outbound HTTPS/TLS destinations and intercept or modify Domino's outbound traffic. Affected builds are 2.0.2 FP8, 14.0 through 14.0 FP5, 14.5 and up to 14.5.1 FP1; the CVSS 4.0 base score is 9.1, and the independently assessed 3.1 vector is AV:N/AC:H/PR:N/UI:N with high confidentiality and integrity impact and no availability impact, reflecting that a man-in-the-middle position on the outbound connection path is a prerequisite. No public exploit code was identified at time of analysis, but HCL has issued a vendor fix and the vuln.today decision label is act_now, making this a near-term patching priority.
An out-of-bounds read in WatchGuard Fireware OS's FireCluster synchronization processing lets an attacker who already sits on the cluster interconnect - a compromised cluster peer or an on-path attacker on the sync link - repeatedly crash the cluster synchronization process with crafted traffic, producing a sustained denial of service. Only Fireboxes deployed in a FireCluster high-availability configuration are exposed; stand-alone Fireboxes are not reachable this way, and the CVSS 4.0 base score of 7.2 (HIGH) is driven almost entirely by high availability impact (VA:H) with only limited confidentiality/integrity effect (VC:L/VI:L) from the out-of-bounds read itself. Fixed builds are available from the vendor (12.12.4, 12.5.22 on the 12.0 LTS branch, and 2026.4 on the 2025.1 branch); no public exploit code has been identified at time of analysis and the flaw is not listed as actively exploited.
WatchGuard Fireware OS firewall deployments below 12.5.22, below 12.12.4, and 2025.1 before 2026.4 allow a remote, authenticated attacker with at least read-only Device Monitor privileges and management CLI access to submit a crafted diagnostic command that creates, truncates, or overwrites arbitrary files and modifies kernel parameters with root privileges. The impact is integrity and availability loss rather than confidentiality exposure, and written file content is limited to numeric values; no public exploit was identified at time of analysis.
Sensitive configuration data disclosure in WatchGuard Fireware OS stems from XPath injection in the management SSH authentication process, allowing a remote, unauthenticated attacker who can reach that interface to submit a crafted request and extract configuration data. Affected releases are Fireware OS 2025.1 before 2026.4 and 12.0 before 12.5.22 or 12.12.4; the vendor has released fixes, and no public exploit is identified at time of analysis, with no CISA KEV listing. Exposure is the key risk factor: appliances whose management SSH interface is reachable from untrusted networks are most at risk, while restricting that interface to trusted management networks substantially reduces exposure.
Unauthenticated visitors to Grav 1.7.53.3 through 1.7.53.5 can read stored Clockwork profiler records when the debugger is enabled with the Clockwork provider and Grav sits behind a same-host reverse proxy; those records can include submitted administrator login passwords unless debugger.censored is enabled, plus configuration credentials from system and plugin settings. The flaw is an authorization bypass in Debugger::isDebuggerRequestAuthorized() that trusts a loopback REMOTE_ADDR fallback, so a tokenless request arriving from the local proxy is accepted; direct-server deployments and sites with the debugger disabled are not exposed. It carries CVSS 4.0 8.7 and a this_week priority, making it a credible high-impact information-disclosure case whose real-world risk is strongly gated by deployment topology; no public exploit was identified at time of analysis.
An out-of-bounds write in NVIDIA PhysX (versions 0.0 through 0.4.1.2, all platforms) allows memory corruption that could lead to code execution, data tampering, denial of service, or information disclosure. The CVSS 3.1 vector (7.8, AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confines the attack to a local path: no attacker authentication is required, but a legitimate user must open or otherwise process attacker-controlled PhysX content before the write can be triggered, so there is no unauthenticated remote trigger. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the vendor-reported case is prioritized as a this-week item rather than an emergency.
The missing-authentication flaw in NVIDIA NeMo Agent Toolkit 1.0 through 1.8.0 leaves a critical toolkit function without a credential check, giving unauthenticated network attackers a path whose rated consequences include code execution, privilege escalation, data tampering, denial of service, and information disclosure. CVSS is 10.0 with AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, and the vuln.today priority label is act_now. No public exploit identified at time of analysis, and no CISA KEV entry appears in the supplied data; network reachability of the toolkit interface is the main practical exposure constraint, and upgrading past 1.8.0 is the vendor-directed remediation.
SQL injection (CWE-89) in NVIDIA NeMo Agent Toolkit versions 1.4 through 1.6 lets an attacker who can reach the toolkit's input path on the local system inject arbitrary SQL, with potential for data tampering, denial of service, and information disclosure. NVIDIA rates the flaw 8.4 (High) and the assessed vector is CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - unauthenticated with no user interaction, but local, so exploitation requires local reachability of the vulnerable query path rather than network access; that AV:L designation is atypical for SQL injection and is the main factor shaping real-world risk. No public exploit code was identified at time of analysis and the issue does not appear in CISA KEV; per the current decision signal this is a this-week priority rather than an emergency.
Server-side request forgery (SSRF) in NVIDIA TensorRT-LLM 1.3.0rc24 allows an attacker who can reach a local input vector to influence server-side requests and potentially disclose information. NVIDIA rates the issue CVSS 7.1 with a local attack vector (AV:L), no authentication required once that vector is reached, no user interaction, changed scope, and high confidentiality impact only. No public exploit code or active exploitation is identified in the available intelligence, and applicability to versions other than 1.3.0rc24 is not confirmed.
Server-side request forgery (CWE-918) in NVIDIA TensorRT-LLM, reported by NVIDIA at CVSS 7.1, allows an attacker positioned with local or adjacent access to the inference host to make the service issue requests to attacker-influenced destinations, yielding high confidentiality impact and possible data tampering under a scope change. No authentication and no user interaction are required once that local/adjacent access is obtained, and AC:L means no special timing or configuration hurdle is described. There is no public exploit identified at time of analysis and the CVE is not in CISA KEV; the EUVD record lists TensorRT-LLM 1.3.0rc24 as affected and the vuln.today decision label is this_week.
TensorRT-LLM 1.3.0rc24 can load a tokenizer from an attacker-influenced location during KvCacheAwareRouter initialization, allowing inclusion of functionality from an untrusted control sphere (CWE-829). Because the CVSS vector is AV:L with PR:N and UI:N, the untrusted tokenizer must be reachable inside the local loading path, but once it is, no credentials or user interaction are needed; successful exploitation can yield code execution, information disclosure, data tampering, and denial of service. NVIDIA reports the issue with a base score of 8.4, and no public exploit code or confirmed active exploitation was identified at time of analysis. Only deployments that actually use the KvCacheAwareRouter and load tokenizers from unverified sources sit in the exploitable path.
Account enumeration in Rolantis Agentis before 4.8 lets remote unauthenticated attackers infer whether accounts exist by observing differing responses from account-handling functionality. The flaw is a CWE-204 observable response discrepancy with low confidentiality impact and no integrity or availability impact, and it is fully remediated by upgrading to 4.8. No public exploit identified at time of analysis.
TLS certificate verification is disabled by default in Eclipse ioFog Operator 3.8.0 through 3.9.1 on the connections it makes to the Controller API and to an external OIDC issuer, so an unauthenticated on-path attacker can present any certificate and be trusted. That position lets the attacker capture the OAuth client secret in external mode, or the Controller bootstrap admin password in embedded mode with Controller HTTPS enabled, and supply the access token the operator stores for later Controller API calls. Exploitation is gated by the requirement to already sit in the traffic path (CVSS 4.0 AT:P), which is the main limiting factor; vendor priority is act_now, and no public exploit has been identified at time of analysis.
A path-scoped middleware bypass in @fastify/express 4.0.5 through 4.0.8 lets an unauthenticated remote attacker reach handlers protected by Express middleware such as authentication, authorization, or rate limiting. The flaw only manifests when Fastify is started with the non-default routerOptions.ignoreDuplicateSlashes: true and a request is sent with an absolute-form target (e.g. GET http://host/admin/dashboard), which the Fastify router normalizes and dispatches to the scoped handler while the Express layer no longer sees the scoped path. Exploitation is gated by that specific configuration plus reliance on path-scoped Express middleware; no public exploit code or CISA KEV entry was identified in the supplied data, though the vendor rates it CVSS 9.1 and priority guidance is act_now. Fixed in 4.0.9.
Eaton easyE4 firmware versions below 2.46 ships an insufficiently strong password policy (CWE-521), so an attacker who has already obtained a stored password hash - for example by way of CVE-2026-41020 - can mount an offline password-guessing attack and potentially recover the underlying user credentials. The weakness is not exploitable on its own: the vendor's CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.5) reflects the hash-disclosure prerequisite and the dependence on how strong the configured password actually is, and strong, high-entropy passwords resist offline cracking even under the weak policy. No public exploit code has been identified at time of analysis, and the exposure is limited to easyE4 devices that have not been updated to firmware 2.46 or later.
Service account impersonation in Octopus Server stems from inconsistent OIDC token issuer validation, allowing a token minted by a non-legitimate issuer to be accepted as if it came from a legitimate trusted issuer. Deployments are exposed only when OIDC is in use for at least one service account identity, and a attacker must additionally know or guess details of that specific identity and operate a rogue issuer that can mint a matching token - conditions that favour targeted attacks over opportunistic scanning. Vendor CVSS 4.0 score is 8.7; the assessed CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N, C:H/I:H/A:H) likewise reflects high complexity and high confidentiality, integrity and availability impact, and no public exploit has been identified at time of analysis.
Information disclosure in Hitachi HiRDB Server can be triggered by remote, unauthenticated attackers over the network, with high confidentiality impact and no integrity or availability impact (CVSS 7.5). The flaw is classified as an origin validation error (CWE-346) and affects HiRDB Server Version 10 before 10-12-01, HiRDB Server Version 9 through 09-66-22, HiRDB Server with Additional Function Version 9 through 09-66/V, HiRDB Server Version 9(32) through 09-66-22, and HiRDB Server with Additional Function Version 9(32) through 09-66-/V. EPSS is low at 0.21% (10th percentile), there is no CISA KEV confirmation, and no public exploit was identified at time of analysis; the vendor has released a patch.
Unauthenticated remote attackers can establish an RMCP+ session on Supermicro MBD-X12SPI baseboard management controllers running BMC firmware 1.07.20 by sending a request immediately followed by a specially crafted RAKP message, abusing incorrect ordering in the RAKP+ authentication handshake; a session established this way could then be used to execute commands. The flaw is rated CVSS 7.4 (AV:N/AC:H/PR:N/UI:N, high confidentiality and integrity impact, no availability impact) and requires network reachability to the BMC's RMCP+/IPMI 2.0 interface, typically UDP 623. EPSS is 0.45% (39th percentile), the CVE is not listed in CISA KEV and no public exploit has been identified at time of analysis; this is a genuine but second-tier priority rather than a drop-everything emergency.
Impersonation of Moxa OnCell G3150A-LTE Series devices still using factory hard-coded keys is possible for unauthenticated remote attackers who obtain the shared key material, compromising confidentiality and integrity of management communications. EUVD lists version 1.0.0 as affected, and exposure is bounded to units that have not regenerated their cryptographic keys and to attackers able to meet the specific attack precondition and passive user interaction reflected in the assessed vector. No public exploit identified at time of analysis; EPSS is 0.30% (23rd percentile) and the priority is monitor.
Improper certificate validation in Moxa MRC Client 1.0.0 through 4.2.0 allows an unauthenticated attacker who already holds an on-path position between the client and its MRC server to impersonate the trusted server and conduct a man-in-the-middle attack, compromising confidentiality and integrity but not availability. The attack requires that network position and passive user interaction, so it is not a mass-exploitation profile; no public exploit was identified at time of analysis and EPSS is 0.17% (7th percentile). The priority signal is this_week, consistent with a moderate-priority issue rather than an active-exploitation emergency.
Read-level project members in OpenPanel before 3.0.0 can retrieve plaintext integration secrets - Slack bot tokens, incoming-webhook URLs and webhook authorization headers - through the notification.rules tRPC query, which eager-loads integration rows and spreads them into the response without applying the redactIntegration step that integration.get and integration.list enforce. The flaw is access-gated: the attacker needs an existing authenticated account with bare project membership (the lowest role, which cannot create or edit integrations) on a project where a write/admin user has attached at least one integration to a notification rule, and a single query call with no user interaction then exposes those credentials for use against external systems. EPSS is 0.30% (23rd percentile) with no CISA KEV listing, and the vendor advisory contains a benign manual proof-of-concept walkthrough; it is a public PoC reference that is not verified as working exploit code.
OpenPanel before 3.0.0 leaks secrets into standard-output logs through two separate code paths, allowing anyone who can read application, container, CI or centralized logs to recover sensitive data. Database migration startup banners print the full DATABASE_URL and CLICKHOUSE_URL including user-info credentials and credential-like query parameters, and the email fallback path used when both SMTP_HOST and RESEND_API_KEY are unset serializes the recipient address, subject and full template data - which for the password-reset flow includes the reset-token URL. Exploitation is not remote against the service itself: it requires pre-existing read access to log stores plus, in the migration case, that the code-migration command was run, or, in the email case, the non-default double-unset provider configuration and a triggered email flow; no public exploit code is identified at time of analysis and EPSS is low (0.28%, 20th percentile), consistent with a moderate-priority information exposure rather than an emergency.
A local privilege escalation in Apple macOS allows an attacker who can already run code on the host to gain elevated privileges, affecting Macs running macOS versions prior to the fixed releases 26.7.2 (Tahoe), 27.2 (Golden Gate) and 15.8.2 (Sequoia). Apple describes the root cause as a logic issue in a protection mechanism, corrected with improved checks. Exploitation has not been observed and no working exploit code is publicly confirmed; EPSS is low at roughly 0.24% (15th percentile) and SSVC marks exploitation as none and non-automatable, though technical impact is total once local access is achieved. Priority is this_week rather than emergency-grade.
Password-protected private-key exports produced by the Erlang/Elixir `jose` library between 1.10.0 and 1.11.12 are encrypted with a hardcoded, drastically under-strength key-derivation step, so anyone who obtains such an exported blob can crack the export password offline at roughly 300 times less cost than modern guidance intends and recover the full private key. Only the password-based export path is affected (JOSE.JWK.to_der/2, jose_jwk:to_der/2, the PEM equivalents and their _file variants); the attack requires possession of the exported DER/PEM file and succeeds only where the export password is weak or moderate, since a long randomly generated password still resists 2048 PBKDF2 iterations. EPSS is very low (0.06%) and there is no KEV listing, but a public proof-of-concept script accompanies the upstream advisory; a public PoC reference exists and demonstrates parameter extraction plus dictionary recovery, though it is not verified here as working exploit code. The vendor fixed the parameters in 1.11.13, and the CVSS vector indicates no privileges are required (PR:N), with the practical gating factors being blob exposure and password strength rather than any network-reachable interface.
Unauthenticated screen-content disclosure in WolfVision Cynap Pro and Cynap Core Pro devices with vSolution Matrix enabled lets hosts on the same network segment view or capture the current presentation through an unencrypted RTSP/RTP stream. The issue affects versions below 1.78a and is limited to confidentiality; the vendor has released 1.78a, and no public exploit was identified at time of analysis. Exposure is bounded by the non-default Matrix feature requirement and network adjacency.
vLLM before 0.32.0 lets untrusted image bytes pick their own Pillow decoder: ImageMediaIO calls Image.open(BytesIO(data)) without an allowlist and the declared MIME label does not constrain format selection, so an EPS payload submitted as image/png is dispatched to the host's Ghostscript. On hosts whose Ghostscript is affected by CVE-2024-29510 this chains to command execution with the vLLM process's privileges, and on environments running Pillow 12.0.0 through 12.2.0 the same boundary reaches CVE-2026-59203, where a malformed EPS parks media-loading workers until the pool is exhausted. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (8.1 High), reflecting that reachability still depends on an image-capable endpoint, the deployment's API-key and network policy, and a vulnerable host dependency; the reported reproduction covered the loader-level command execution, while the HTTP request path was only source-traced. No public exploit code was identified at time of analysis, and CISA KEV does not list this CVE.
Use of a hard-coded cryptographic key in Johnson Controls Kantech EntraPass before 9.20 enables a padding oracle crypto attack. Exploitation requires local access and low-level privileges (AV:L/PR:L per the vendor CVSS 4.0 vector), so the attacker must already have authenticated or local foothold on the EntraPass system rather than operating as a remote unauthenticated adversary; impact is high across confidentiality, integrity and availability of the affected system. No CISA KEV entry, public exploit code, or EPSS score was provided, and the product's fixed 9.20 release resolves the condition.
Access control bypass in Syncplify Server! before 8.8.0 allows authenticated SFTP users to evade per-path permission overrides by addressing a protected directory with alternate capitalization or its 8.3 short name, enabling file uploads and downloads the override is meant to deny. The flaw is conditional on an existing deny override and on filesystem behavior that accepts alternate case or short names, such as Windows/NTFS; on strictly case-sensitive filesystems without short-name generation the technique is limited. No public exploit was identified at time of analysis, and the vendor has released 8.8.0 as the fix.
Hardcoded static AES key embedded in the TTLock Android app (versions before v9.8.260718) and its associated smart-lock firmware allows an attacker within Bluetooth Low Energy range to capture a pairing exchange and decrypt the per-pairing session key transported during it. With the recovered persistent session key the attacker can forge authenticated BLE commands to unlock the lock, enroll fingerprints or access codes, and carry out administrative actions without authentication or user interaction (CVSS 4.0 8.6, AV:A/AC:L/PR:N/UI:N, VC:H/VI:H). The exposure is bounded by physical proximity to the lock rather than internet reach, and a public PoC reference exists but is not verified as working exploit code; there is no CISA KEV confirmation of active exploitation.
MongoDB Shell (mongosh) versions prior to 2.14.0 bundle a Node.js runtime whose TLS root store includes recoverable eMudhra intermediate CA certificates, so an unauthenticated on-path attacker who can present a certificate chain under that CA could intercept and alter TLS connections when a victim initiates a mongosh TLS session. The issue is CWE-295 improper certificate validation and is rated CVSS 4.0 7.6 (High); exploitation requires a MITM network position plus victim-initiated interaction, and npm-based installs instead depend on the host Node.js runtime. The vendor fix is mongosh 2.14.0 bundling Node.js 24.22.1 or later, and no public exploit identified at time of analysis.
Improper certificate validation in the Erlang HTTP client hackney (1.24.0 through 4.8.x) lets an on-path attacker impersonate a server that an application has pinned to a private certificate authority. Because hackney adds its own {partial_chain, fun hackney_ssl:partial_chain/1} to every verify_peer configuration and OTP honours that callback over a caller-supplied cacerts/cacertfile trust store, a chain ending in any certifi-bundled public root can be accepted as the trust anchor; the attacker still needs a man-in-the-middle position and a publicly trusted certificate for the exact pinned hostname that satisfies the hostname check, so only non-default private-CA pinning deployments are exposed. No public exploit identified at time of analysis and no CISA KEV entry, though the issue is triaged as act_now and fixed in hackney 4.9.0.
Root-level SSH access to WolfVision vSolution Matrix appliances can be obtained by anyone holding the private key that matches the product's shared cryptographic trust configuration, allowing authentication as root on affected devices. Only devices configured as a vSolution Matrix main/master station with the file sharing feature enabled are in scope, so the exposed population is a non-default subset rather than every deployment; the CVSS 4.0 vector (9.2) marks PR:N and UI:N, meaning no legitimate credentials or victim interaction are required once the key is in hand, while AT:P reflects that the key must first be acquired. No public exploit code or confirmed active exploitation appears in the supplied intelligence, but the vuln.today decision label is act_now and the shared nature of the trust material means one recovered key can potentially be replayed against multiple affected master stations.
HAVELSAN Liman MYS releases from 2.3.4-1124 up to but not including 2.3.5-1131 contain a weak forgotten-password recovery mechanism (CWE-640) that lets a network attacker abuse the account-recovery workflow to take over a targeted account, with high confidentiality and integrity impact and no effect on availability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, base 8.1) indicates the flaw is network-reachable and low complexity and needs no attacker credentials, but it is not fully autonomous because a victim must perform some recovery-related action (UI:R); the exact weakness in the recovery flow is not described in the available sources. No CISA KEV entry and no exploit code reference were provided, so no public exploit identified at time of analysis; TR-CERT rates it for remediation within this week.
Case-sensitivity defects in MISP Guard's feed-distribution policy checks allow an authenticated MISP event creator to slip events past configured TLP taxonomy, allowed-tag, blocked-attribute-category and blocked sharing-group rules simply by changing the letter case of a tag, category or UUID string, with the result that threat-intelligence data the operator meant to restrict is still forwarded to feed consumers. Only deployments running misp-guard 1.3 or earlier that actually rely on these allow/block policies are exposed, and the impact is confidentiality-only - no integrity or availability effect. No public exploit code was identified at time of analysis; the vendor has published an upstream fix commit (9868b1d9) that normalizes case on both sides of every affected comparison and adds regression tests reproducing the bypass.
Out-of-bounds reads in the SOEM EtherCAT master library (2.0.0 and earlier) let a malicious or compromised device on the same EtherCAT segment make the master read past the end of allocated buffers, disclosing memory contents or crashing the master process. No authentication or user interaction is required, but the attack surface is confined to the adjacent Layer-2 fieldbus segment - typically an isolated OT control network rather than anything internet-routable. No public exploit code or confirmed in-the-wild exploitation is identified in the available data, and the vuln.today decision label is this_week, reflecting a genuine but bounded industrial/OT priority rather than an internet-wide emergency.
CRLF injection in the Dnsmasq configuration path of Oray Pugongying X5 Pro 7.6.1 lets a user who already holds administrative access to the router's management interface inject newline-delimited Dnsmasq directives through the DHCP lease-time (rent_time) parameter, corrupting the device's DNS/DHCP behaviour and enabling configuration tampering and potential information disclosure. Exploitation is remote over the network with no user interaction, but the CVSS vector carries PR:H - an attacker must first obtain admin credentials, which is the primary limiting factor, so this is not reachable by an unauthenticated outsider. A public PoC reference (a Notion write-up titled 'Dnsmasq Directive Injection Through DHCP Lease Time') exists but is not verified as working exploit code; the vendor was contacted and did not respond, so no fixed version is available, and the disclosure is tracked for remediation this week.
Out-of-bounds read in Fuji Electric V-SFT can be triggered when a user opens a crafted V7 project file, potentially exposing information or enabling arbitrary code execution on the affected system. The flaw is local and requires user interaction-the victim must open the malicious file-and no privileges are required, so social engineering is the primary attack vector. This is a moderate-priority, not emergency, issue; no public exploit identified at time of analysis.
Opening a crafted V7 project file in Fuji Electric/Hakko V-SFT can cause an out-of-bounds read in VS6EditData!CDataRomErrorCheck::CheckSymbolMacroParam, potentially leading to information exposure or arbitrary code execution in the context of the user running the application. The issue is assessed as high severity (CVSS 4.0 8.4) with a local, user-assisted file-open path, and affected-product data uses wildcard CPE version fields rather than a specific version range. No CISA KEV designation is present in the supplied data, and no public exploit was identified at time of analysis; the independent assessment rates it this-week priority, not emergency-grade.
Opening a crafted V7 project file in Fuji Electric V-SFT can trigger an out-of-bounds read in the macro-command check path, leading to information disclosure or arbitrary code execution on the workstation running the product. The flaw is local to the host, requires no attacker privileges, and depends on the victim opening the malicious file, so exploitation is constrained by file delivery and user interaction rather than remote network access. No public exploit was identified at time of analysis, and the vendor and JVN advisories are the available sources for affected-version and update details.
Opening a crafted V7 project file in Fuji Electric's V-SFT screen-creation/engineering software can drive an out-of-bounds read in the VS6MemInIF!set_temp_type_default routine, exposing process memory and, per the vendor, potentially enabling arbitrary code execution on the workstation running the application. Rated 8.4 (CVSS 4.0, CWE-125) and tracked by JPCERT/CC, the issue is conditional rather than mass-exploitable: the attack vector is local and the victim must actively open an attacker-supplied project file, while no authentication or special privileges are required for the payload to be processed. No public exploit identified at time of analysis, no CISA KEV listing, and the vendor advisory plus JVN note are the primary sources for version and fix guidance.
Out-of-bounds read in Fuji Electric V-SFT's VS6ComFile!load_gr_item routine can expose memory contents or enable arbitrary code execution when an operator opens a crafted V7 file. The attack is local and requires user interaction: an attacker must deliver a malicious V7 file and convince a V-SFT user to open it. No public exploit identified at time of analysis, and the issue is not confirmed as actively exploited (CISA KEV).
An out-of-bounds write in Fuji Electric's V-SFT screen-creation software (also published under Hakko Electronics) is triggered when a user opens a crafted V7 project file, allowing memory corruption that can disclose information or lead to arbitrary code execution on the engineering workstation running the tool. Exploitation is local and interaction-gated: the attacker must first deliver the malicious V7 file to a victim who then opens it in V-SFT, so there is no network-facing attack surface and no credentials are needed for the file itself to carry the payload. No public exploit code and no confirmed active exploitation (CISA KEV) are indicated in the available intelligence, but the JVN-published issue is rated high severity and prioritized for remediation this week.
Opening a crafted V7 project file in Fuji Electric V-SFT (the HMI screen-configuration and programming software, listed in the CPE as Fuji Electric / Hakko Electronics V-SFT) overflows a stack buffer and can result in information exposure or arbitrary code execution with the privileges of the user running the application. The attack is local rather than network-reachable and requires the victim to actively open the malicious file, so compromise depends on social engineering a legitimate V-SFT user; no authentication is required of the attacker. No public exploit code has been identified at time of analysis, and the vulnerability is tracked by JPCERT/CC under JVNVU96549652 with a priority of 'this_week' rather than emergency-level.
Improper Secure Boot signature verification in Yoosee GM8135S Camera 21.00.01.36 lets a local attacker who already holds high privileges get a manipulated firmware image accepted (CWE-347), undermining firmware trust and enabling tampering or persistence. The CVSS 4.0 base score is 8.4, but the attack path is local and requires existing privileged access, with no remote or unauthenticated vector described; the exact trigger is not detailed in the available sources. A public PoC reference exists; it is not verified as working exploit code, and no CISA KEV entry confirms active exploitation; the disclosure is prioritized this_week.
LDAP credential exposure in Snipe-IT 8.6.2 and earlier lets an on-path attacker capture service-account and end-user passwords in cleartext. Ldap::connectToLdap() called ldap_start_tls() and discarded the boolean result, so when TLS negotiation fails or a man-in-the-middle answers the StartTLS extended request with a 'Protocol error', the subsequent ldap_bind() sends credentials unencrypted while users see a normal, silent login. Only deployments with LDAP authentication enabled and TLS configured (ldap_enabled=1, ldap_tls=1) plus an attacker-reachable network path to the LDAP server are exposed; no public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, though the vendor advisory publishes the exact code path and trigger.
SiYuan 3.6.0 through 3.8.6 accepts and persists the networkServeTLS administrator setting but never enforces it, so the kernel port continues answering plain HTTP with full API access in cleartext while also serving HTTPS on the same port. An operator who enables the toggle believes kernel traffic is encrypted, yet a network-adjacent attacker can sniff the login flow - including the access auth code - and the session cookie, which is issued without the Secure attribute while HTTPS responses omit HSTS, allowing session hijack against the kernel API. Exploitation requires a network-adjacent sniffing position and the operator having enabled the setting, which is why the flaw is rated for adjacency and high complexity rather than internet-wide exposure; a public PoC reference exists describing the verification steps, and it is not confirmed as working exploit code. A vendor fix is available in v3.8.7.
rotki before 1.44.2 derives the encryption key for its premium cloud backup/sync feature as a single unsalted SHA-256 hash of the user password, so anyone who obtains an uploaded backup blob can run offline, GPU-parallel password guessing against it and decrypt the database it holds - exchange API keys, secrets, wallet addresses and transaction history. The attack is unauthenticated and requires no user interaction once the blob is in hand, and only users of the premium sync/backup feature are affected. There is no KEV entry and no public exploit identified at time of analysis, though the CVSS 4.0 score of 8.2 signals high confidentiality impact; the vendor addressed the issue in rotki 1.44.2.
CPython's ssl module validates TLS certificate chains that anchor to known-compromised eMudhra CA certificates, so anyone holding that CA's key material can impersonate arbitrary TLS servers to unpatched Python clients. Every Python application that relies on the default verification path (ssl.create_default_context() or an SSLContext without its own OCSP/CRL checking) is affected, which is CPython's default behaviour; the fix adds a hard-coded denylist of distrusted certificates enforced regardless of SSLContext policy. Exploitation is targeted rather than opportunistic, requiring the compromised CA key plus a man-in-the-middle or server-impersonation position against the victim's connection; no public exploit identified at time of analysis, and the vendor-tracked priority label is act_now.
MongoDB Compass versions prior to 1.53.1 ship an Electron runtime whose bundled TLS root store still contains the compromised, recoverable eMudhra intermediate CA certificates, so a party holding a certificate chained to those intermediates can be treated as trusted by the application. Because the attacker must also occupy a man-in-the-middle position on the network path and induce a user to initiate a Compass connection through it, impact is confidential and integrity-related (VC:H/VI:H) rather than an unauthenticated remote take-over. The vendor resolves the issue in Compass 1.53.1, which bundles Electron 44.9.1; no public exploit code or active exploitation has been reported, and the issue is prioritised as this week rather than an emergency.
Postiz (gitroomhq/postiz-app) before v2.25.1 allows any signed-in user to invoke arbitrary internal integration methods through the POST /integrations/function endpoint, using a connected channel's token as the first argument. By setting that token to a filesystem path, an attacker can read server files such as the application environment, exposing the session-signing secret, database address and third-party service credentials; a separate internal helper can terminate the backend process with one request. Self-registration is open by default, so an external attacker can obtain the required low-privilege account without any action by another user, and no public exploit code has been identified at time of analysis.
Account takeover in OpenReception's appointment booking software before 2.2.1: whoever holds a pending invite token can replay it during its thirty-minute validity window and receive a fresh passkey-registration bootstrap credential, letting them enrol their own passkey on the invited account and, for staff or tenant-admin invites, reach the tenant context tied to that account. The endpoint is reachable without authentication over the network and rated CVSS 7.4, although the attacker must first obtain the emailed token and act before the legitimate invitee completes passkey setup. No confirmed active exploitation (CISA KEV) is reported; the vendor advisory publishes reproduction steps as a public PoC reference, and the issue is fixed in version 2.2.1.
Host-header injection in OpenReception's confirmation-email path lets unauthenticated remote attackers redirect a pending invitee's one-time confirmation token to an attacker-controlled host and then claim that account before the legitimate invitee ever onboards. The unauthenticated POST /api/auth/resend-confirmation rotates a pending invitee's token and builds the emailed link from the request Host with no allowlist, so a single request carrying a spoofed Host and the victim's email address produces a genuine onboarding email whose only link points at the attacker. Because the account is claimed first and bound to an attacker-registered WebAuthn passkey, the attacker gains a full session in the invited role (staff or tenant admin), with read and potentially modify access to client and appointment data; a public proof-of-concept package is attached to the advisory and reported to demonstrate the flow end-to-end against the official image, though it is not independently verified as working exploit code. Exploitation requires the victim to click the poisoned link (UI:R) and depends on the front proxy forwarding an arbitrary Host, which the stock Caddy catch-all does.