Blind SQL injection in Google SecOps (Chronicle SOAR) versions before 6.3.85 lets an authenticated user abuse a crafted request parameter in a legacy dashboard widget API to run arbitrary blind SQL queries against the backend database. CVSS 4.0 rates it 9.4 (critical) with a low-privilege network vector; no public exploit is identified at time of analysis and it is not listed in CISA KEV. Because the platform is a Google Cloud-managed SaaS, the fix was deployed by the vendor and no customer action is required.
Arbitrary native code execution in the jahlives openssl_encrypt Python package (all versions before 1.4.0) arises from its Whirlpool hash routine loading .so extension modules via a broad glob pattern without any integrity check. An attacker who can drop a file matching 'whirlpool*py313*.so' into a site-packages directory gets their code executed in-process the moment the hashing module is imported. Reported by VulnCheck; a vendor patch (1.4.0) exists, and there is no public exploit identified at time of analysis.
Sandbox escape in the openssl_encrypt Python library (jahlives) before 1.4.0 allows attacker-supplied plugins to run without any isolation because the default process-isolation mode silently fails to enforce its sandbox restrictions. An attacker able to supply or influence a plugin gains unrestricted filesystem, network, subprocess, and full Python-module access equivalent to arbitrary code execution. Reported by VulnCheck with a vendor patch available; no public exploit code or CISA KEV listing is identified at time of analysis (CVSS 4.0 base 9.3).
Arbitrary code execution in jahlives openssl_encrypt before 1.4.0 stems from an inconsistent sandbox: the runtime PluginImportGuard and the static AST analyzer enforce two different blocklists, so an attacker who slips past the AST's DANGEROUS_MODULES check can still import high-risk modules at runtime. By using string obfuscation or encoding to hide imports of sys, shutil, multiprocessing, importlib, or pickle, a supplied plugin escapes the sandbox and runs on the host. Reported by VulnCheck with a vendor patch available; no public exploit has been identified at time of analysis and it is not listed in CISA KEV.
Authentication bypass in the jahlives openssl_encrypt library (all versions before 1.4.0) lets remote unauthenticated attackers fully control the key-management API because verify_api_token treats any non-empty Bearer string as valid. An attacker can upload attacker-controlled public keys, enumerate every stored key, and revoke keys belonging to arbitrary users, undermining the confidentiality and integrity guarantees the tool is meant to provide. The flaw is vendor-confirmed with a patch available and was reported by VulnCheck; no public exploit identified at time of analysis, though the trivial nature makes weaponization simple.
Authentication brute-force protection can be bypassed in jahlives openssl_encrypt before 1.4.0 because the TOTP rate limiter is held in per-process in-memory state (a class-level defaultdict) rather than shared storage. In multi-worker or multi-instance deployments each worker enforces its own independent counters, and all lockout state evaporates on restart, so an attacker can parallelize or restart-reset their way through TOTP guesses. No public exploit is identified at time of analysis, and it is not listed in CISA KEV; a vendor patch exists in 1.4.0.
Arbitrary file read and deletion in SiYuan kernel before v3.7.4 arises from an unvalidated id parameter in the database_clean MCP tool, letting an authenticated MCP client traverse the filesystem to copy any process-readable file into the history directory and then delete the original. This is the MCP-facing twin of a flaw previously fixed on the HTTP API path (GHSA-7hm9-v7vf-7g4w), meaning a known-bad code pattern survived in a second caller. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis and not listed in CISA KEV.
Sandbox escape in the openssl_encrypt Python library (jahlives) before 1.4.0 lets attacker-supplied plugin code break out of the IsolatedPluginExecutor and run arbitrary OS commands. The restricted exec() environment still leaks live Python type objects, so an attacker walks the class hierarchy to reach system primitives despite the intended sandbox. Rated CVSS 4.0 9.3 (critical) and reported by VulnCheck; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Stored/reflected cross-site scripting in Discourse before 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0 lets an unauthenticated attacker execute arbitrary JavaScript in a visitor's browser by supplying a crafted color_scheme_id or dark_scheme_id cookie. Because the cookie is rendered into a color-scheme tag without HTML escaping, an attacker can break out of the attribute context and inject markup that defeats Discourse's nonce-based Content Security Policy. A vendor patch exists and the flaw carries a critical CVSS of 9.3, but no public exploit has been identified at time of analysis and it is not listed in CISA KEV.
Cryptographic shared-secret disclosure in the openssl_encrypt Python library (maintainer 'jahlives') before 1.4.0 lets an attacker reconstruct the KEM shared secret and decrypt all protected ciphertext once they obtain only 16 bytes of the private key. The flaw lives in pqc.py, where any post-quantum KEM decapsulation failure silently falls back to a 'simulation mode' that derives a deterministic secret from those 16 key bytes plus attacker-visible encapsulated-key data, rather than raising an error. Reported by VulnCheck; there is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Sandbox escape leading to remote code execution affects openssl_encrypt (the jahlives Python package) in all versions before 1.4.0, where the DangerousPatternVisitor AST analyzer fails to catch dunder-based attribute traversal. Because the library's security model is to safely execute untrusted plugin code, an attacker who can supply a plugin can chain __class__, __bases__, __subclasses__() and __globals__ to reach restricted functions and run arbitrary OS commands, fully defeating the sandbox. Reported by VulnCheck with a vendor patch available; no public exploit or CISA KEV listing was identified at time of analysis.
Sensitive-token exposure in openssl_encrypt (the jahlives Python package, pip 'openssl-encrypt') before 1.4.0 stems from the keyserver and telemetry server accepting refresh tokens as GET query parameters. Because URLs are routinely written to server access logs, proxy/CDN logs, browser history, and forwarded in HTTP Referer headers, any party with access to those artifacts can harvest a valid refresh token and mint new access tokens, effectively bypassing authentication. Reported by VulnCheck; no public exploit identified at time of analysis and it is not on CISA KEV.
Broken access control in OpnForm's editable-submission feature lets unauthenticated attackers derive any submission's secret because the Hashids library is used with an empty default salt over sequential database row IDs. Since the hash of a sequential integer becomes trivially predictable, an attacker can enumerate submissions to read other respondents' full answer data via the submission-fetch endpoint or overwrite existing submissions through the answer endpoint. Reported by VulnCheck and patched in v2.0.2; there is no public exploit identified at time of analysis, but the flaw is remotely and trivially reproducible against affected default installs.
SQL injection in Page Builder CK for Joomla (versions before 3.6.5) lets attackers manipulate database queries through the extension's styles model, exposing the underlying database to unauthorized read and write. The flaw is exploitable remotely without authentication per the CVSS 4.0 vector (AV:N/PR:N/UI:N), with the frontend attack surface closed in 3.6.4 and the backend surface closed in 3.6.5. No public exploit identified at time of analysis, but the CWE-89 root cause and the reported 9.3 severity make this a high-priority patch for affected Joomla sites.
Authentication bypass in the openssl_encrypt Python library (versions before 1.4.0) lets attackers who can tamper with ciphertext in transit defeat integrity protection, because a failed AES-GCM authenticated decryption in pqc.py silently falls back to unauthenticated AES-CTR. Reported by VulnCheck and carrying a CVSS 4.0 base score of 9.3, the flaw enables undetected bit-flipping and ciphertext manipulation. No public exploit identified at time of analysis, but a vendor patch is available.
Authentication bypass in FakeFish (openshift-metal3/fakefish), a Redfish BMC emulator used to bridge metal3/Ironic provisioning to KubeVirt virtual machines, lets any authenticated cluster user manage VMs they do not own. Because FakeFish forwards inbound Redfish credentials to backend scripts but the KubeVirt backend authenticates via a mounted KUBECONFIG and ignores those credentials entirely, no meaningful authorization occurs; an attacker can power target VMs on and off and mount arbitrary virtual CD/ISO images. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the flaw is trivial to trigger given the missing authentication check.
Weak cryptographic key derivation in the openssl_encrypt Python library (all versions before 1.4.0) stems from its key-normalization routines invoking HKDF with no salt and a static info parameter, making derived keys deterministic for identical inputs. This reduces effective entropy and weakens resistance to multi-target (batch) attacks, letting an adversary who collects ciphertexts or derived-key material amortize cryptanalytic effort across many victims. No public exploit identified at time of analysis; the flaw was reported by VulnCheck and a vendor patch is available in 1.4.0.
Secret disclosure affects the openssl_encrypt Python library (all versions before 1.4.0), where PublicKeyBundle.from_dict() constructs key bundles from untrusted serialized data without validating the embedded self-signature, and to_identity() then promotes that unverified bundle into a usable Identity. An application that deserializes an attacker-supplied bundle and encrypts to it - without an intervening verify_signature() call - will encrypt secrets to an attacker-controlled public key, allowing the attacker to decrypt them. Reported by VulnCheck and fixed in 1.4.0; no public exploit has been identified at time of analysis.
Schema validation bypass in the openssl_encrypt Python package (by developer 'jahlives') before version 1.4.0 lets attackers slip malformed or malicious metadata past all JSON schema checks. Because validation fails open when the optional jsonschema library is absent - and because unknown metadata format versions are silently skipped - an attacker who controls the runtime environment or the supplied metadata can process unvalidated data. Reported by VulnCheck and carrying a CVSS 4.0 base score of 9.3; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Integrity-protection bypass in the jahlives openssl_encrypt Python library (all versions before 1.4.0) lets an attacker who can influence the process environment silently disable HMAC authentication in the CamelliaCipher code path. When the PYTEST_CURRENT_TEST environment variable is present, the library skips generating and verifying HMAC tags, so ciphertext is produced and accepted without integrity protection, enabling undetected tampering of encrypted data. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis and it is not listed in CISA KEV.
Unauthenticated access to a phone-number lookup endpoint in ShopSmart Loyalty for WooCommerce (versions ≤1.0.0) exposes customer PII - name, email address, and loyalty account balance - to any caller who supplies a valid phone number. Rooted in CWE-639 (Authorization Bypass Through User-Controlled Key), the plugin performs no ownership or identity check before returning profile data. A public exploit exists via WPScan; the SSVC framework flags the attack as automatable, enabling systematic bulk harvesting of customer records across affected WooCommerce stores.
Audit-trail corruption and a security-control race condition in the Python library openssl_encrypt (by jahlives) before version 1.4.0 undermine its module-hiding defenses. The restore_hidden_modules() function logs module counts after clearing them, so it always records zero restored modules and produces misleading audit logs (CWE-117), while a separate time-of-check/time-of-use race between module hiding and import-hook installation lets a concurrent thread re-import modules that were meant to be blocked. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis and it is not on CISA KEV.
Authentication bypass in MemOS (MemTensor), a memory operating system for LLMs and AI agents, lets an unauthenticated remote attacker impersonate a trusted internal principal with full 'all' scopes. When AUTH_ENABLED=true but the undocumented INTERNAL_SERVICE_SECRET variable is left unset, a null-versus-null comparison in the internal-request check fails open, exposing admin API-key management and all data endpoints. Rated CVSS 4.0 9.3 (critical) by VulnCheck; no public exploit identified at time of analysis, though the flaw is trivially reproducible from the disclosed source.
Unauthenticated information disclosure in SiYuan before 3.7.4 exposes Go net/http/pprof debug endpoints (heap, goroutine, and related dumps) to any remote client whenever the application is not started with --mode set exactly to prod. Because non-prod is the effective default, attackers can query /debug/pprof/heap to scrape live process memory and recover secrets such as the AccessAuthCode and configured AI provider API keys. Reported by VulnCheck with a vendor patch available; no public exploit identified at time of analysis.
SQL injection in Stud.IP (an open-source learning management system widely used in German-speaking higher education) affects the 6.0.x branch before 6.0.3 and the 5.4.x branch before 5.4.12, where unsanitized input reaching store() persistence functions lets a remote attacker read and manipulate database contents and, per the researcher's write-up, escalate to arbitrary code execution. The flaw carries a CVSS 9.1 (C:H/I:H) rating with a public technical write-up available from the reporting researcher; there is no public exploit identified as weaponized and no CISA KEV listing at time of analysis. Organizations running the affected LMS branches should treat this as high priority given the confidentiality and integrity impact combined with the RCE claim.
Command and SQL injection in Red Hat Advanced Cluster Management for Kubernetes 2 (acm-search-v2-rhel9) lets a privileged tenant escalate to arbitrary code execution inside the cluster's PostgreSQL pod. An authenticated hub administrator or Search Custom Resource editor can supply an unsanitized WORK_MEM value that is passed into both a bash script and an SQL query, breaking out of the intended data plane. No public exploit is identified at time of analysis and the flaw is not on CISA KEV, but the CVSS 9.1 rating reflects full confidentiality, integrity, and availability loss with a scope change.
Stack buffer overflow in COVESA Open1722 through version 0.9.2 enables unauthenticated remote attackers to corrupt stack memory and achieve arbitrary code execution or denial of service by sending a single crafted UDP datagram containing more than 15 ACF-CAN messages. The root cause is an unbounded write index in the avtp_to_can() function, which increments unconditionally past the end of a fixed 15-slot stack array without comparing against the caller-supplied size. Exploitation requires no authentication because the ACF-CAN listener accepts packets from any sender matching a hardcoded stream identifier transmitted in plaintext; no public exploit code or active exploitation confirmed by CISA KEV has been identified at time of analysis.
Unauthenticated database backup disclosure in JetBrains YouTrack before 2025.3.156085, 2026.1.13913, and 2026.2.18112 allows a remote attacker to abuse a shared draft signature to download full database backups without any credentials. Because backups typically contain issue data, user records, and secrets, this is a high-impact confidentiality exposure. No public exploit has been identified at time of analysis and it is not listed in CISA KEV, but the CVSS 9.1 rating and trivial network exploitability make it a priority patch.
Privilege escalation in the Trueview T18061 WiFi 3MP Robot Pan-Tilt Security Camera (firmware Version 1.0) stems from an embedded RSA private key, letting a nearby attacker who recovers or reuses that key gain elevated access to the device. The flaw is classified under CWE-321 (use of a hard-coded cryptographic key), meaning every unit of this model likely shares the same secret key material. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV; EPSS data was not provided.
Improper access control via path traversal in Mahara's ePortfolio system allows others to reach artefacts (uploaded files/content) they should not see when the file path to an artefact embedded in a page is manipulated. It affects Mahara releases before 25.04.5 and before 26.04.0 and is fixed in those versions. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the impact is unauthorized disclosure of user-owned content rather than server compromise.
Financial fraud via integer overflow in QuantumNous New API (an LLM gateway and AI asset-management platform) lets a low-privileged account with a positive balance or active subscription manipulate user-controlled billing multipliers so that a computed charge wraps into account credit and can drain upstream provider funds. The flaw sits in quota settlement math (common/quota_math.go and related paths) across image, video, audio, and token-count fields, and is fixed in 1.0.0-rc.18. There is no public exploit identified at time of analysis, but the upstream fix commits and GHSA advisory publicly disclose the vulnerable code paths.
Privilege escalation via token disclosure affects QuantumNous New API, an open-source LLM gateway and AI asset management platform, in all versions prior to 1.0.0-rc.7. The admin user-list and user-lookup endpoints (e.g. GET /api/user/) serialize the full User model with only Omit("password"), so User.AccessToken is returned in the access_token field, letting an authenticated administrator harvest the root user's bearer token and pivot to root-only system-configuration APIs. No public exploit identified at time of analysis and it is not in CISA KEV; the fix is confirmed in release 1.0.0-rc.7 (GHSA-6x2c-phff-wx57).
Arbitrary command execution in the conflibot GitHub Action (versions before 1.2.1) lets any user who opens a pull request run shell commands on the workflow runner. conflibot builds git commands via string interpolation and executes them through a shell, and one interpolated value is the attacker-controlled PR head branch name (head.ref); a branch name containing shell metacharacters is executed as code. Under the documented pull_request_target configuration the runner holds a write-scoped GITHUB_TOKEN and repository secrets, so this is a critical CI/CD supply-chain exposure (CVSS 9.1). There is no public exploit identified at time of analysis, but the technique is well understood and the trigger is trivial.
Credential exposure in Logsign SIEM (versions 6.4.97 up to but not including 6.4.114) allows a high-privilege authenticated user to retrieve embedded sensitive data such as stored integration or log-source credentials. The issue was reported by Turkey's national CERT (TR-CERT, advisory TR-26-0847) and carries a vendor CVSS of 9.0; a fixed release (6.4.114) is available and no public exploit has been identified at time of analysis. Because a SIEM aggregates credentials for many connected systems, recovered secrets can enable pivoting well beyond the SIEM itself.
Remote code execution in WordPress exposes sites to full server compromise when an Author-level (or higher) authenticated user uploads a specially crafted PostScript file that is subsequently processed by Imagick and Ghostscript. The vulnerability, classified as CWE-434 (Unrestricted Upload of File with Dangerous Type), leverages Ghostscript's Turing-complete PostScript interpreter to execute arbitrary OS-level commands under the web server's process identity. No public exploit has been identified at time of analysis, but the low privilege bar - requiring only an Author account - and WordPress's massive global deployment footprint make this a high-priority remediation item for any self-hosted installation running Imagick with Ghostscript.
Arbitrary file read and write in HP Web Jetadmin (WJA) is achievable by unauthenticated remote actors via a DLL hijacking mechanism, carrying a CVSS 4.0 score of 8.9. The flaw exposes full confidentiality, integrity, and availability of the WJA host - an attacker can exfiltrate sensitive configuration and credential files or overwrite system files to achieve persistent access. Proof-of-concept exploit code exists (CVSS 4.0 E:P), elevating real-world risk, though active exploitation has not been confirmed by CISA KEV at time of analysis.
Remote code execution in Roundcube Webmail (before 1.6.18 and 1.7.x before 1.7.3) is achievable by authenticated remote attackers through the cmd_learn driver of the markasjunk plugin, which passes unsanitized placeholder replacement values derived from user-controlled email content directly to OS command invocations (CWE-78). Exploitation is strictly limited to instances where the markasjunk plugin is installed and configured with the cmd_learn driver - a non-default, operator-configured setup - meaning the broader Roundcube population is unaffected. Vendor-released patches exist for both the 1.6.x and 1.7.x branches; no public exploit has been identified at time of analysis, and the CVE is not listed in the CISA KEV catalog.
Remote code execution is achievable in T-Systems International GmbH ImageMaster version 9.14.2.8.1 through an unrestricted file upload flaw in the 'add attachments' feature of the document creation workflow. A remote attacker can upload a malicious executable file (e.g., a webshell) and subsequently trigger its server-side execution, achieving full system compromise. A proof-of-concept exploit is publicly available per SSVC data and a GitHub repository linked in references; however, no CISA KEV listing has been recorded and EPSS exploitation probability is notably low at 0.59% (45th percentile), indicating limited observed in-the-wild activity at time of analysis.
Arbitrary file upload in 2100 Technology's Official Document Management System (all versions before 5.0.105) enables authenticated remote attackers to upload and execute web shell backdoors, achieving full arbitrary code execution on the underlying server. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L) confirms network-accessible exploitation requiring only a low-privileged account, with total impact across confidentiality, integrity, and availability. No public exploit code or active exploitation has been identified at time of analysis, and a vendor patch is available.
LDAP filter injection in Roundcube Webmail arises from unescaped substitution variables (`%u`, `%fu`, `%d`) embedded directly into LDAP `search_filter` configuration strings, affecting all 1.6.x releases before 1.6.18 and 1.7.x releases before 1.7.3. An authenticated user whose login credentials contain crafted LDAP metacharacters can manipulate server-side directory queries, potentially disclosing LDAP directory contents or escalating privileges by subverting group membership lookups. No active exploitation has been identified at time of analysis (SSVC: Exploitation none), though the low attack complexity and network accessibility warrant prompt patching for any LDAP-backed deployment.
Integer overflow in Apple's image processing subsystem across iOS, iPadOS, and macOS Tahoe allows arbitrary code execution when a user processes a maliciously crafted image. Affected platforms include iOS and iPadOS prior to 26.6.1 and macOS Tahoe prior to 26.6.2, with Apple releasing out-of-band point releases indicating urgency. No public exploit has been identified at time of analysis, but the CVSS 8.8 score and SSVC total technical impact rating place this among high-priority patching targets given Apple's massive consumer and enterprise device footprint.
Memory corruption in Apple's web content rendering engine affects iOS, iPadOS, and macOS Tahoe, enabling high-impact device compromise when a user processes maliciously crafted web content. All iOS and iPadOS versions prior to 18.7.10 and 26.6.1, and macOS Tahoe versions prior to 26.6.2, are confirmed affected per Apple security advisories and EUVD-2026-60510. Apple has released patched builds across all affected branches; no public exploit code or CISA KEV listing has been identified at time of analysis.
Local privilege escalation in Zephyr RTOS (versions 4.0.0-4.4.1 with CONFIG_USERSPACE enabled) allows an unprivileged user-mode thread to execute arbitrary code in kernel supervisor mode by supplying forged struct device pointers with attacker-controlled API function tables to the flash_copy() system call. The syscall verifier z_vrfy_flash_copy() validated the output buffer but omitted the K_SYSCALL_DRIVER_FLASH object validation for src_dev and dst_dev that every sibling flash syscall enforces - a unique gap in the trust boundary that the kernel implementation blindly dereferences in supervisor context. No public exploit or active exploitation has been identified at time of analysis; a vendor-released patch is confirmed in commit 1b1ecdc4 and available in Zephyr 4.4.2.
Privilege escalation in Red Hat Advanced Cluster Management for Kubernetes 2 allows any attacker with local pod execution under the `search-serviceaccount` service account to impersonate `system:masters` and gain full cluster-admin control. The `search-serviceaccount` RBAC bindings grant cluster-wide `impersonate` permissions on users and groups - a grossly over-privileged configuration that collapses the entire cluster's security boundary if any pod running under this account is compromised. No public exploit has been identified at time of analysis and this CVE is not in CISA KEV, but the CVSS scope change (S:C) and full CIA triad impact (C:H/I:H/A:H) accurately reflect the catastrophic blast radius of successful exploitation.
Command injection in Glances system monitoring (versions 4.5.2 through 4.5.5) allows a local attacker with process-execution rights to bypass the action-template sanitizer by embedding pipe characters in process argv, which is exposed as a Python list that the incomplete `_sanitize_mustache_dict()` function passes to the Mustache renderer without sanitization. This is a confirmed incomplete fix of CVE-2026-32608: the original sanitizer checked only top-level string values in the render dictionary, leaving nested containers unchecked, and the Chevron renderer does not escape `|`, so the character reaches `secure_popen` and spawns an attacker-controlled subprocess. Vendor-released patch v4.5.6 introduces recursive sanitization; no public exploit has been identified at time of analysis.
Path traversal in Evidently UI's dataset materialization endpoint exposes arbitrary host filesystem files to unauthenticated remote attackers. The filename parameter in the materialization API is unsanitized, enabling directory traversal sequences or absolute paths to escape the workspace directory; the materialized file is then retrievable via the download endpoint. No active exploitation has been confirmed (not listed in CISA KEV), and no patched version has been identified at time of analysis - all known versions remain vulnerable per the wildcard CPE.
Unauthorized file download in Typemill before 2.26.0 is achievable by unauthenticated remote attackers through a path-equivalence authorization bypass in the media file download controller. The role-based restriction map is consulted using the raw, unnormalized URL-supplied filename, while the PHP filesystem layer transparently resolves path-equivalent forms - dot-slash prefixes, double slashes, and percent-encoded separators - to the actual protected file, producing an authorization mismatch that allows restricted media to be served without credentials. No public exploit code has been identified at time of analysis, but the attack requires no authentication, no user interaction, and no special client capabilities beyond a standard HTTP request.
Out-of-bounds heap read in TIER IV Nebula's Vlp32Decoder::unpack() function through version 1.2.0 enables unauthenticated remote attackers to inject fabricated LiDAR point data into autonomous vehicle perception pipelines by sending short malformed UDP datagrams to the Velodyne sensor port. Unlike other Nebula sensor drivers, the VLP-32 UDP listener enforces no sender-address restrictions, making any network-reachable host a valid attacker origin without spoofing. Fabricated points derived from adjacent heap memory contents are silently published into downstream PointCloud2 messages consumed by Autoware nodes, creating a sensor-integrity risk with direct safety implications; no public exploit code and no CISA KEV listing are identified at time of analysis.
Unthrottled brute-force against SiYuan's Publish Service Basic Auth allows remote unauthenticated attackers to enumerate passwords against named publish-viewer accounts and gain read access to published notes and notebooks. All SiYuan releases before 3.7.4 are affected wherever the Publish Service is enabled and network-accessible on its default TCP port 6808. No public exploit code has been identified at time of analysis, but the attack is trivially automatable using any standard HTTP client given the complete absence of rate limiting, per-account lockout, or exponential backoff in the vulnerable code path.
Unauthenticated access to JimuReport's report folder template listing endpoint exposes all report definitions, share tokens, embedded SQL statements, and live query data to any remote attacker. The CWE-306 root cause - missing authentication for a critical function - means the disclosure requires no credentials, no user interaction, and no special tooling. With a CVSS 4.0 score of 8.7 and a network-accessible, zero-complexity attack path, this represents a high-priority information disclosure risk for any JimuReport deployment reachable from an untrusted network. No public exploit or CISA KEV listing has been identified at time of analysis, though the vulnerability is fully disclosed via VulnCheck advisory and a public GitHub issue.