Authenticated remote code execution in OpenC3 COSMOS (Ruby gem 'openc3' versions 5.1.0 through 7.2.1) lets any logged-in user, including one with only low-tier permissions, execute arbitrary Ruby and Python code on the COSMOS server and its per-target decom microservices. COSMOS reads configuration from a user-writable overlay (targets_modified/) before its read-only targets/ tree and then executes that content - rendering it as ERB, eval-ing GENERIC_READ/WRITE_CONVERSION blocks, or require-ing Script Runner procedure files - so an attacker who can write to the overlay via the screen-save or storage-upload endpoints achieves code execution as the openc3 user, which holds Redis and object-store credentials and sits on the internal service network. A working proof-of-concept is published in the vendor GitHub advisory, and the vendor has released 7.3.0 as the fix; no confirmed active exploitation (CISA KEV) has been reported. Reachability is limited on default single-host installs because the shipped docker-compose binds Traefik to 127.0.0.1:2900, so exploitation is realistic on multi-user deployments that expose the web port.
Authenticated code execution on the GitLab server is possible in GitLab CE/EE 19.2 through 19.4.0, where an integer overflow triggered while compiling a specially crafted regular expression in a CI/CD configuration can be leveraged to run arbitrary code with the privileges of the GitLab application. The attacker must hold a GitLab account with enough project privileges to create or modify CI/CD configuration (typically Developer or higher on a project), and exploitation only occurs 'under certain conditions,' so it is not universally triggerable; the vendor-assessed vector is PR:L with scope change, and our independent assessment raises attack complexity to High (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H). Publicly available exploit code exists - a HackerOne report accompanies the fix - but there is no confirmed active exploitation (no CISA KEV listing), and instances already on 19.2.7, 19.3.3, or 19.4.1 or later are not exposed.
Authenticated users who can define or modify a CI/CD configuration can achieve remote code execution on GitLab CE/EE servers by submitting a specially crafted regular expression that triggers a double free during server-side parsing. All versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 are affected; the vendor scores the issue 9.9, while our assessment retains full confidentiality and integrity impact but raises attack complexity to high because the vulnerable path is state-dependent and double-free corruption is inherently unreliable to exploit. Publicly available exploit code exists (a HackerOne report is referenced), and patches are available in 19.2.7, 19.3.3, and 19.4.1; there is no CISA KEV confirmation of active exploitation.
Cross-tenant authorization bypass combined with pre-authentication denial of service in Moquette Broker 0.18.0 and earlier lets unauthenticated remote MQTT clients read and write other tenants' topics and repeatedly wedge or exhaust the broker. The critical flaw is wildcard injection through pattern-based ACLs that substitute %c/%u with an unvalidated clientId, so a client connecting with clientId '+' turns a rule such as sensor/%c/# into the filter sensor/+/#; from the same unauthenticated position an attacker can also trigger a $share/grp SUBSCRIBE StringIndexOutOfBoundsException, a StackOverflowError on deeply nested topics, an ACL NPE, unauthorized Will-message publishes, and unbounded subscription/retained/interceptor state that causes memory or disk exhaustion. Publicly available exploit code exists in the form of source-only PoCs (JDK 17) for the pattern-ACL bypass, the shared-subscription crash, and the H2 metadata collision; the vendor-released fix is 0.18.1, and no CISA KEV entry or confirmed in-the-wild exploitation was provided. Score of 9.6 reflects scope change with high confidentiality and integrity impact, gated on a multi-tenant pattern-ACL configuration for the worst outcome.
Unauthenticated remote code execution in IBM Concert 1.0.0 through 3.0.0 lets any attacker who can reach the service send specially crafted input that is incorporated into operating-system commands, executing arbitrary commands with the privileges of the Concert application. The vulnerability is rated CVSS 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication, no user interaction, and no special conditions are required - only network reachability of an unpatched instance. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, so exploitation appears opportunistic-dependent rather than confirmed in the wild, but IBM has published a vendor fix, so the priority is to patch exposed instances before exploit code or scanning activity emerges.
Stored cross-site scripting in SunEditor prior to 2.47.11 allows an attacker-supplied editor payload to survive the library's built-in sanitizer and execute JavaScript in a victim's browser origin. The sanitizer in src/lib/core.js fails to consistently reject namespaced or custom HTML elements, so an event-handler attribute (for example an on-click handler) can be retained on a crafted element; when a downstream application stores content from one user and renders it to another, the handler fires on victim interaction. Exploitation therefore requires a multi-user rendering workflow plus victim interaction with the crafted element, and there is no public exploit identified at time of analysis; the 10.0 base score carried in some feeds is substantially overstated relative to the independent assessment (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N), which reflects a bounded stored-XSS impact rather than unauthenticated, no-interaction compromise.
ManageEngine Applications Manager builds 182200 and below embed a static Google Cloud service-account private key inside the shipped installer, so anyone who downloads that installer artifact can extract the credential without authenticating to the product and then impersonate the service account directly against Google Cloud APIs. The vendor scores this CVSS 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) because the leaked key grants high confidentiality and integrity impact on associated cloud resources and the scope changes beyond the Applications Manager instance itself, with no authentication or user interaction required. Exploitation depends on the installer being obtainable and the referenced service account remaining active with meaningful IAM permissions; no public exploit code has been identified at time of analysis and there is no CISA KEV listing, but the credential is static rather than runtime-dependent, which makes the exposure durable rather than conditional.
Missing authorization checks in the Red Hat Ansible Automation Platform 2 automation-controller allow an authenticated organization workflow-admin - a delegated, non-superuser role - to escalate into the control plane by copying a WorkflowJobTemplate and then launching jobs pinned to instance groups they hold no use_role on. The deep-copy permission sanitizer re-validates only the inventory, unified_job_template, and credentials of each cloned node, silently carrying over instance_groups, execution_environment, and labels, so the copier becomes administrator of a workflow that executes attacker-influenced automation in the control-plane execution context (CVSS 9.9, scope changed, high confidentiality, integrity, and availability impact). Exploitation is confirmed to require only a normal multi-tenant deployment plus workflow-admin rights; no public exploit code has been identified at time of analysis and there is no CISA KEV entry, and no vendor-released patch version was confirmed in the available intelligence.
SQL injection in the third-party Socialwall course-format plugin for Moodle (versions 3.0 through 3.3) lets remote attackers inject crafted SQL through a plugin HTTP endpoint, granting high confidentiality and integrity impact on the Moodle database. The vendor-supplied CVSS of 9.8 assumes no authentication, but our assessment lowers this to a PR:L vector (CVSS 3.1: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N, 8.8) because plugin endpoints in Moodle typically require a valid authenticated session - a limiting factor that remains unconfirmed from available metadata. Exploitation is not confirmed actively exploited (no CISA KEV listing), and while a public Medium write-up describes the SQLi, no public exploit code has been confirmed at time of analysis; note that the CVE description's claim of arbitrary code execution is broader than the assessed confidentiality/integrity-only impact.
Authenticated users who hold permission to create or modify a project within a single organization can execute arbitrary commands on the Ansible Automation Platform 2 automation-controller task pod by setting the Project scm_url to a value beginning with a dash, for example '--upload-pack=<command>:x'. The automation-controller's git SCM module passes that URL verbatim as a positional argument to 'git ls-remote' without a '--' end-of-options separator, so git treats it as the --upload-pack option and executes the attacker's command via a shell, with output reflected through the project update stdout endpoint, enabling cross-tenant compromise and in-cluster lateral movement (CVSS 3.1 9.9, scope changed). Exploitation needs valid platform credentials and the git project type but no admin or cross-organization rights, and no public exploit code has been identified at time of analysis.
Privilege escalation and remote code execution on managed hosts is possible in Red Hat Ansible Automation Platform 2 because the automation-controller exposes the provisioning-callback secret (host_config_key) to anyone holding only read-level view_jobtemplate permission and accepts a client-supplied X-Forwarded-For header as proof of caller identity when the gateway proxy allow-list is empty. An attacker who reads the secret from the job template API representation or the activity stream and spoofs X-Forwarded-For to match any host in the target job template's inventory can launch that template against arbitrary managed hosts using the template's stored credentials; CVSS 3.1 base score is 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), no public exploit code was identified at time of analysis, and the decisive enabler is a non-default deployment condition - an empty proxy allow-list combined with provisioning callbacks actually being in use.
Authenticated OS command injection in Zoho ManageEngine OpManager MSP 12.8.709 and below allows an attacker holding any valid low-privilege console account to execute arbitrary operating system commands on the server through the Notification Profile module, with no user interaction required. Exploitation yields full compromise of confidentiality, integrity and availability of the OpManager host, which for an MSP deployment typically means access to monitored customer infrastructure. The vendor rates the issue 9.9 (scope-changed); our independent assessment places it at high severity with unchanged scope, and no public exploit code has been identified at time of analysis, so the practical risk is concentrated in environments where operator or tenant accounts are widely provisioned or reusable.
Use-after-free in IBM Concert 1.0.0 through 3.0.0 lets an attacker who can influence program input or execution flow corrupt heap memory, crash the application, or potentially hijack control flow for code execution. No public exploit code and no confirmed active exploitation were identified at time of analysis, and IBM has published a vendor fix (advisory node 7288830). The vendor-published vector claims unauthenticated network exploitation at 9.8, but our assessment scores the issue AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H: the practical attack is high-complexity, requires an authenticated position to supply the malicious input, and the specific trigger surface is unconfirmed, so real-world severity is materially lower than the published base score suggests.
Authentication bypass in Apache Tomcat allows unauthenticated remote attackers to reach WebSocket endpoints that are supposed to be protected by container-managed security constraints, simply by referencing the endpoint under an alternate name so the constraint is never matched. Exploitation requires only that the application expose one or more WebSocket endpoints and rely on container-level (web.xml security-constraint) authentication or authorization rules to guard them; no credentials, no user interaction, and no non-default configuration beyond that are needed, and per the CVSS vector (PR:N) the attack is unauthenticated and network-reachable. Affected lines are Tomcat 11.0.0-M1 through 11.0.25, 10.1.0-M1 through 10.1.59, 9.0.0.M1 through 9.0.121, plus end-of-support 8.5.0-8.5.100 and 7.0.43-7.0.109; no public exploit code has been identified at time of analysis and Apache has released fixed versions 11.0.26, 10.1.60 and 9.0.122.
Symlink-based path traversal in the `tar` source plugin of Apache BuildStream (versions up to and including 2.8.0, running on Python < 3.12) lets a malicious source tarball write arbitrary files on the host with the privileges of the user running BuildStream, resulting in full confidentiality, integrity, and availability impact to that user's environment. The vendor-published CVSS 3.1 base score is 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), but the assessed vector adds UI:R: exploitation requires the victim to fetch and extract an attacker-controlled or otherwise untrusted source tarball, and it is not exploitable against projects that use only trusted, tracked sources, since SHA256 hash pinning of tracked tarballs prevents MITM substitution. No public exploit code and no confirmed active exploitation were identified at time of analysis (CISA SSVC exploitation: none; EPSS 0.19%, 10th percentile); the vendor-released patch is BuildStream 2.8.1, and hosts running Python >= 3.12 with BuildStream >= 2.3.0 are already protected because the Python `tarfile` extraction filter blocks the symlink escape.
Heap-based buffer overflow in Google Chrome builds earlier than 154.0.8037.57 allows unauthenticated remote attackers to corrupt memory when a victim loads attacker-controlled web content, with a CVSS base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) reflecting scope change and potential high confidentiality, integrity, and availability impact. Exploitation requires user interaction - visiting a malicious site, a compromised page, or a malicious ad - and full host compromise would most likely require chaining this renderer-process overflow with a separate sandbox-escape bug rather than this flaw alone. Risk signals conflict in the usual browser-bug pattern: EPSS is only 0.29% (19th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis, while Chrome's silent auto-update rapidly shrinks the vulnerable population and a vendor patch is already available.
An out-of-bounds memory write in Google Chrome allows an unauthenticated, remote attacker to corrupt memory and potentially execute arbitrary code or crash the browser when a victim opens a crafted web page, as reflected by the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H (9.6, scope-changed). The flaw is classified as CWE-787 (out-of-bounds write) and is addressed by the vendor's stable channel update for desktop, with the fix credits originating from the Ubuntu vendor reporting channel, meaning downstream Chromium packages are also in scope. At time of analysis there is no public exploit identified, no CISA KEV listing, and no EPSS data provided; however, because browser memory-corruption bugs of this class are historically attractive to exploit developers, this remains a high-priority patching item despite the absence of exploitation telemetry.
Use-after-free memory corruption in Google Chrome desktop builds prior to 154.0.8037.57 allows a remote, unauthenticated attacker to trigger heap memory corruption in the browser by convincing a victim to load attacker-controlled web content - a single page navigation is sufficient (UI:R, PR:N, AV:N). The flaw is rated CVSS 9.6 with a scope change (S:C), indicating the corruption can affect resources beyond the initially vulnerable component; no authentication, prior privileges, or non-default configuration is required, though exploitation hinges entirely on user interaction with a malicious or compromised page. Google has already shipped a fixed build (154.0.8037.57) on the stable channel, and no public exploit code or confirmed active exploitation was identified at time of analysis, making this a genuine high-priority patch-and-update item rather than an emergency zero-day response.
Out-of-bounds memory write in Google Chrome allows remote attackers to corrupt memory in a victim's browser by having them load attacker-controlled web content, rated CVSS 3.1 base 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H). No authentication or non-default configuration is required, but exploitation depends on user interaction (the victim must visit or load the malicious page) and on running an unpatched build predating the September 2026 stable-channel fix; exact affected versions are not confirmed in the available data. The scope-change component suggests impact extending beyond the initially affected component - the classic profile of a renderer-process compromise crossing Chrome's process boundary - and while a vendor patch is available, no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis.
CVE-2026-95277 is currently an effectively empty record: no description, CVSS score, CVSS vector, CWE mapping, affected product, version range, or CPE data has been published, and the only intelligence signal is attribution to the Ubuntu vendor reporting channel. Because the vulnerability class, attack vector, authentication requirements, and impacted component are all unknown, risk cannot be meaningfully assessed from the available data and no exploit status can be confirmed - there is no public exploit identified at time of analysis, and the entry is not listed as confirmed actively exploited (CISA KEV). Organizations should treat this identifier as a placeholder to be re-triaged once Ubuntu publishes a corresponding security notice (USN) or the upstream CVE record is populated.
Risk cannot be meaningfully assessed from the supplied data: CVE-2026-95283 is recorded only as a vendor-reported entry from Ubuntu, with the description marked '[Unknown description]' and no CVSS score, CVSS vector, CWE, CPE, or affected source package provided. Because the impacted component, deployment mode, and attack surface are all unidentified, no statement can be made about what an attacker could achieve, which versions are affected, or what preconditions (authentication, user interaction, configuration) would be required. There is no KEV listing and no public exploit code identified at time of analysis, so the entry should be treated as an unassessed tracking record rather than a confirmed exploitable issue.
Risk cannot be meaningfully assessed for CVE-2026-95299 because the vulnerability record contains no description, no CVSS score or vector, no CWE mapping, and no CPE/product identifiers; the only attributable data point is that the issue was reported by the vendor Ubuntu. Consequently the affected component, the attack surface, and any prerequisite conditions remain unknown, and no public exploit has been identified at time of analysis. Analysts should treat this identifier as unresolved rather than low-risk: an empty record frequently reflects a placeholder or embargoed entry that is populated later, so the absence of detail is not evidence of low severity.
A use-after-free in Google Chrome desktop can be triggered when a victim renders attacker-controlled web content, allowing memory corruption that may lead to code execution or disclosure of sensitive in-process data. Affected are Chrome desktop builds on Windows, macOS, and Linux prior to the September 2026 stable channel update; the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6) requires no authentication or privileges but does require the victim to open or load a malicious or compromised page, and the S:C metric indicates the attack can affect a component beyond the one that is corrupted. Vendor-released patch available; no public exploit identified at time of analysis, and the reporting originator is Ubuntu.
Use-after-free memory corruption in Google Chrome's desktop stable channel lets remote, unauthenticated attackers achieve high-integrity/high-availability impact against a victim who simply renders attacker-controlled web content - the attacker must first convince the user to visit a malicious or compromised page (or load a malicious ad/iframe), which is why the assessed vector carries UI:R despite PR:N. Per our independent assessment, a practical exploit must win a heap-grooming race to reclaim the freed object and, because of the scope change (S:C), chain a further sandbox escape to fully realize the 9.6 severity, so exploitation is possible but not trivial. A vendor fix is available in the referenced Chrome stable channel update, and no public exploit code has been identified at time of analysis; the specific vulnerable component and exact fixed build are not disclosed in the available data.
Heap-based buffer overflow (CWE-122) in Google Chrome's stable channel, addressed in the September 2026 desktop stable-channel update, lets remote, unauthenticated attackers corrupt heap memory in a vulnerable build and potentially escape the browser's renderer sandbox for full confidentiality, integrity, and availability impact (CVSS 3.1 base 9.6, S:C). Exploitation requires the victim to interact with attacker-controlled web content - typically visiting a malicious page or rendering a hostile ad - so the practical window depends on how quickly users and Linux distributions apply the update. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV; details remain limited because the referenced Chromium issue tracker entry is access-restricted.
Google Chrome on the desktop stable channel carries a vendor-patched security defect tracked as CVE-2026-95347, disclosed through Google's Chrome Releases stable-channel update in September 2026. The actual impact is currently undetermined: no description, CVSS score or vector, CWE classification, or affected version range has been published, so the vulnerability class, whether attackers must be authenticated, and whether user interaction (such as visiting a crafted page) is required cannot be confirmed from available data. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis, and no EPSS probability or SSVC decision data exists to refine the risk; this should be treated as a patch-priority item pending the details in the vendor advisory.
Use-after-free memory corruption in Google Chrome allows remote attackers to corrupt memory and potentially execute code beyond the browser's normal security boundaries when a victim loads attacker-controlled web content. The flaw carries a CVSS 9.6 with vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, meaning no authentication is required, the attack is network-delivered, and the scope change plus full confidentiality, integrity, and availability impact indicate a flaw that can affect resources beyond the vulnerable component - consistent with a renderer sandbox escape. Exploitation requires the victim to visit a malicious page or render a malicious embedded resource such as an ad or iframe; at time of analysis there is no public exploit identified, but the vendor has released a patched stable-channel build and defenders should treat untrusted browsing on unpatched Chrome as high risk.
Heap-based buffer overflow in Google Chrome desktop (stable channel) allows a remote, unauthenticated attacker to corrupt heap memory when a victim renders attacker-controlled web content such as a malicious page, iframe, or ad, yielding high impact to confidentiality, integrity, and availability with a changed scope that suggests effects can extend beyond the initially affected component. Exploitation requires user interaction (UI:R) - the victim must load the hostile content - but needs no credentials (PR:N), is network-reachable (AV:N) and low complexity (AC:L), making actively browsing, unpatched endpoints the realistic exposure. No public exploit has been identified at time of analysis; the referenced Chrome stable channel advisory and Chromium issue 551573368 confirm a vendor fix, and the independent assessment rates this a genuine high priority at CVSS 9.6.
Risk cannot be meaningfully assessed from the available data. CVE-2026-95281 is tracked in the Ubuntu security database, which establishes only that it affects software shipped as a package within the Ubuntu distribution; the upstream project, the vulnerable component, and the affected Ubuntu releases are all unspecified. No description, CVSS vector, CWE, CPE, KEV status, or exploit data was provided, and no public exploit has been identified at time of analysis, so the attack vector, privilege requirements, and user-interaction prerequisites remain unknown and must be sourced from the corresponding Ubuntu Security Notice or the NVD entry.
Ubuntu Linux is the only product implicated by the available reporting for CVE-2026-95311, a record attributed to the Ubuntu vendor security team, but the vulnerability description is unpublished and no CVSS score or vector, CWE classification, CPE identifier, EPSS estimate, or CISA KEV entry accompanies it, so the affected component, version range, and attack vector cannot be stated. No public exploit code has been identified at time of analysis, and there is no evidence of confirmed active exploitation. Risk cannot be meaningfully assessed from the provided data; the only actionable intelligence is the vendor attribution, which indicates Canonical is coordinating the record and that the Ubuntu Security Notices feed and the upstream advisory should be monitored for the eventual disclosure.
The affected product and the nature of the security impact for CVE-2026-95325 cannot be established from the intelligence available at time of analysis. The only signal present is that the entry was reported by the vendor source 'ubuntu', with no description, CVSS score or vector, CWE mapping, CPE identifiers, references, EPSS score, or KEV status supplied; the independent assessment accordingly classifies this as a data-void entry with no analyzable signals. No public exploit identified at time of analysis, and there is no basis to characterize the attack vector, authentication requirements, or affected versions.
CVE-2026-95318 is currently an unenriched record that cannot be meaningfully risk-assessed: the only attributable data point is that it was reported by vendor:ubuntu, with no description, no CPE strings, no CWE, no CVSS score or vector, and no references supplied. There is no confirmation of what component, package, or Ubuntu release is affected, whether exploitation requires authentication or user interaction, or what the resulting impact would be. Neither confirmed active exploitation (CISA KEV) nor publicly available exploit code exists in the available data, so the exploitation status is best described as no public exploit identified at time of analysis. This analysis should be treated as provisional and re-run once Ubuntu Security Notices or NVD enrichment supply a description, affected version range, and CVSS vector.
Unspecified security defects in Google Chrome desktop builds are addressed by a September 2026 stable-channel update, meaning only users running outdated installations remain exposed. The exact vulnerability class, attack vector, and privilege requirements are not disclosed in the available data, so the primary applicability condition is simply that the victim runs an unpatched Chrome desktop build and loads attacker-influenced web content, which implies user interaction (browsing) as a limiting factor. There is no CVSS score or vector, no CWE mapping, no EPSS probability, no CISA KEV listing, and no public exploit code identified at time of analysis, so no quantitative severity or exploitation-probability framework can be applied to this record.
OS command injection in Plesk allows any authenticated low-privilege panel account - customer, reseller, or subscription level - to run arbitrary operating-system commands with root privileges, turning what is normally a tightly scoped hosting login into full control of the managed server. The flaw is remotely reachable over the network at low complexity with no user interaction (CVSS 4.0 base 9.4; independently assessed as CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H), and the scope change plus high confidentiality, integrity, and availability impact reflect a complete host compromise rather than a single-tenant breach. No public exploit code has been identified at time of analysis and the CVE is not listed as confirmed actively exploited (CISA KEV), but the low bar of a single valid non-admin session keeps the practical risk high; the specific vulnerable panel function and the exact affected Plesk versions are not stated in the available data and must be confirmed against the vendor advisory.
Argument injection in WP Toolkit for cPanel 6.11.2-10794 and earlier allows a remote authenticated (low-privileged, PR:L per the CVSS vector) customer account to read arbitrary files and execute arbitrary code, with the impact extending beyond the attacker's own account into other tenants hosted on the same cPanel server. Any standard shared-hosting customer login - including a self-registered or compromised account - is sufficient, requiring no user interaction and no elevated privileges, though the extension must be installed, enabled, and reachable on a version at or below 6.11.2-10794. There is no public exploit identified at time of analysis and the issue does not appear on CISA KEV; the defining risk amplifier is the multi-tenant scope change (S:C) rather than mass internet-wide exploitation.
Remote stack-based buffer overflow in the Device Discovery Service of FAST FAC1203R Gigabit Edition 2.0.4 routers allows unauthenticated attackers to execute arbitrary code via a crafted message processed by the copy_msg_element function. A public proof-of-concept exploit has been published, and the vendor has not released a patch. While the CVSS vector indicates network exploitable (AV:N), the discovery service is typically limited to the LAN broadcast domain, so attackers most likely need adjacent network access rather than internet routing.
Any holder of a valid low-privileged cPanel account can escalate to root and execute arbitrary code on the underlying host, because a privileged cPanel operation is executed with unnecessary root privileges (CWE-250). The flaw is remotely reachable over the network with low attack complexity and no user interaction, but it does require an authenticated account (CVSS 4.0 vector PR:L) - a trivial barrier on shared hosting where accounts are commonly sold or self-provisioned, and a meaningful one on locked-down single-tenant deployments. It carries a 9.4 CVSS 4.0 score and is rated a genuine high-priority issue rather than a high-score/low-real-risk case, though no public exploit code and no confirmed active exploitation were identified at time of analysis; no EPSS estimate was available in the supplied intelligence.
Unauthenticated file upload in Laravel-Mediable 7.0.0 and 7.0.1 lets a remote attacker upload a .pht file that passes MediaUploader::verifyExtension() and File::sanitizeFileName(), which is then written to disk and executed as PHP when requested on Apache servers configured with the Debian/Ubuntu default FilesMatch handler, resulting in remote code execution as the web server process. The flaw is an incomplete fix for CVE-2026-49972: the forbidden_extensions list added in config/mediable.php blocks phpt but omits pht, an Apache-recognized PHP extension. Vendor-released patch 7.0.2 closes the gap; no public exploit code was identified at time of analysis, but exploitation is trivial where the upload endpoint is reachable and unauthenticated, so the issue warrants high priority despite the platform-specific precondition.
Moquette MQTT brokers prior to 0.18.1 can start up with authentication and authorization silently disabled whenever a configured authenticator_class or authorizator_class fails to load, so any remote client - including anonymous MQTT clients, since the broker is anonymous by default - can read and write every topic the broker handles while the operator believes access controls are active. The flaw is not directly attacker-triggered: it requires a deployment that both intends to enforce auth and has a broken class-load (misspelled class name, missing dependency, constructor failure, or classpath problem), which is why the independent assessment rates it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N even though the end-state is a full confidentiality and integrity break; the vendor's CVSS 4.0 vector is 9.3. No public exploit for this fail-open condition was identified at time of analysis, and no CISA KEV entry is present; version 0.18.1 fixes the issue by aborting startup instead of falling back to permissive defaults.
Code injection in orval's opt-in @orval/hono generator (all versions before 8.29.0) lets an attacker who controls an OpenAPI document plant an apostrophe in a static path segment and break out of the single-quoted route literal, injecting arbitrary JavaScript that runs whenever the generated TypeScript module is imported or built. This is a build-time supply-chain style flaw rather than a runtime flaw in a network service: the affected party must run orval code generation against an untrusted spec and then import the generated output, and the CVSS v4.0 score of 9.3 reflects high confidentiality, integrity and availability impact on the build/developer environment. Exploitation is not confirmed in the wild (no CISA KEV entry) and no public exploit code was identified at time of analysis, though the upstream patch and the exact vulnerable code path are publicly documented.
Code generation in orval before 8.29.0 writes the raw OpenAPI operationId into a single-quoted object literal inside generated TanStack Query mutator metadata, so a crafted operationId can break out of the string and inject arbitrary JavaScript that executes when the generated query or mutation hooks are called. Practical exploitation requires a developer or CI pipeline to run orval codegen against an OpenAPI document whose operationId is attacker-controlled and then to execute the generated hooks - a conditional path that hinges on the trust boundary of the ingested spec, even though PR:N appears in the vector; the independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects this required victim interaction, while the headline CVSS 4.0 score of 9.3 (UI:N) overstates how freely the flaw triggers. No public exploit code and no CISA KEV entry were identified at time of analysis, and no EPSS score was provided; a vendor patch is available (orval 8.29.0).
Unauthenticated remote attackers can bypass client-certificate trust in Temporal's s2s-proxy 0.1.16 through 0.2.2 by presenting a self-signed certificate and key to a mux or TCP TLS server listener, because the proxy runs Go's RequireAnyClientCert mode whenever skipCAVerification is false and therefore never validates the presented chain against the configured CA. A successful handshake yields a yamux-multiplexed, peer-authenticated channel on which the attacker can call every RPC the proxy's aclPolicy allows, exercising the proxy's own Temporal credentials against the cross-cluster replication API without supplying any trusted certificate, private key, or Temporal credential. No CISA KEV active-exploitation signal is present and no public exploit identified at time of analysis, but the defect carries a 9.3 CVSS 4.0 score and the vendor has published an upstream fix (PR #296 plus associated commits).
Stored cross-site scripting in IBM Financial Transaction Manager (FTM) for Red Hat OpenShift allows an attacker with adjacent-network positioning to plant script inside stored network acknowledgement data, which then executes in the browsers of authenticated FTM operators and can lead to session hijacking and unauthorised operator-level payment actions. The flaw sits in the NetworkAcknowledgement React component (NetworkAcknowledgement.jsx:42), which renders stored acknowledgement content without adequate output encoding. The vendor rates it 9.3, while the assessed vector is CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N, where the requirement that a legitimate operator open the affected view is the practical limiting factor; no public exploit code and no confirmed active exploitation were identified at time of analysis, but the payments context and scope change keep the impact ceiling high.
Unauthenticated SQL injection in the WordPress/WooCommerce plugin Product Filter by WBW (versions 3.1.7 and earlier) lets any remote visitor inject SQL through the plugin's public-facing product-filter functionality and read arbitrary data from the site's database, with no login and no victim interaction required. The reporting source (Patchstack) and ENISA EUVD both classify this as a high-severity SQLi, while the assessed vector constrains the impact to confidentiality only (C:H/I:N/A:N) rather than the scope-change-plus-availability model that produces the 9.3 headline score, so the practical effect is large-scale data disclosure rather than remote code execution or denial of service. No public exploit code has been identified and there is no evidence of active exploitation at time of analysis; exploitation depends solely on whether the affected plugin is installed, active, and reachable on a standard WordPress deployment.
Code injection in the Orval OpenAPI client generator (@orval/core before 8.28.0) lets an attacker who controls a multipart schema property name in a supplied OpenAPI document smuggle a `${...}` template-literal expression into the generated client, which then executes as live JavaScript with the privileges of the process that builds or runs that client. The vendor rates this CVSS 4.0 9.3 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H), while our independent assessment scores it CVSS 3.1 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) because exploitation is not reachable over a network service directly - it requires a developer to generate and then execute a client from an attacker-influenced spec, which is meaningful user interaction. This is a build-time/tooling supply-chain flaw: only organizations that feed untrusted, third-party, or externally sourced OpenAPI documents into Orval and then run the generated code are exposed. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, though a vendor patch and the upstream fix commits are public, so weaponization of the technique is plausible for anyone who reads the advisory.
Code injection in orval before 8.29.0 lets an attacker who controls or influences the OpenAPI specification being processed smuggle executable JavaScript into the generated client: media-type (Content-Type) keys are written into single-quoted string literals without escaping, so punctuation in a crafted key terminates the literal and injects arbitrary statements into the emitted code. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H) makes this an unauthenticated remote code-injection flaw at 9.3, but exploitation in practice is gated by the victim actually running orval over the malicious spec and then invoking the generated fetch operation or mock resolver - our independent assessment therefore applies UI:R (CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), and teams that only generate clients from their own trusted specifications are not realistically exposed. No public exploit code or confirmed active exploitation has been identified at time of analysis, and the vendor has released a fix in orval 8.29.0.
Code injection in the Orval OpenAPI client generator's @orval/effect package (versions 8.14.0 through 8.28.1) lets an attacker who can influence an OpenAPI schema embed arbitrary JavaScript expressions in the generated validation module, which execute at module scope as soon as that generated code is built or imported. The injection point is the schema `default` value, which the effect generator rewrites into a template literal so that `${...}` syntax (or a literal backtick) re-arms interpolation, with numeric constraints such as minimum/maximum/multipleOf similarly emitted as unquoted expressions; exploitation is remote and does not require prior credentials per the vendor vector (PR:N), but it does require the victim to run the generator against an untrusted or third-party spec and then build or import the output, giving injected code the developer's build-time privileges. No public exploit code has been identified at time of analysis and the issue is patched upstream, so real-world urgency is lower than the vendor's CVSS 4.0 score of 9.3 suggests - this is a build-time/developer-tooling flaw rather than a network-facing service exposure (independent assessment: CVSS 3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, reflecting the victim interaction the vendor rating understates).
Remote code execution affects LightLLM deployments through version 1.2.0 that run the KV-transfer worker with the non-default '--pd_trans_mode nccl' option, which exposes an unauthenticated RPyC ThreadedServer control channel on the network. An attacker with network reachability can send a malicious pickled object to that channel, triggering unsafe deserialization and executing arbitrary code with the privileges of the LightLLM service account (CVSS 9.3; PR:N/UI:N). The vulnerability is not known to be actively exploited and no public exploit code has been identified at time of analysis, though the non-default configuration limits exposure to deployments that explicitly enable NCCL-based prefill/decode disaggregation.
RabbitMQ brokers that use the OAuth2 plugin can silently fall back to disabled TLS certificate verification when no CA bundle can be located, allowing an attacker already positioned as a network man-in-the-middle to forge the JWKS response and inject arbitrary JWTs that the broker will accept as authentic. The flaw affects RabbitMQ server versions prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, and exploitation requires four conditions to align: the OAuth2 plugin must be in use, no cacertfile may be configured, the host or container's OS CA bundle must be empty or unreadable, and the attacker must hold a MitM position on the path to the identity provider's JWKS endpoint. Unauthenticated remote attackers are the relevant threat actor per the CVSS vector (PR:N), but the precondition stack and the required network position make this a heavily gated authentication-bypass rather than a blanket internet-exploitable critical; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Code injection in the Orval OpenAPI-to-TypeScript client generator (@orval/core) before 8.30.0 lets an attacker who controls the default value of a date or date-time field in an OpenAPI schema splice arbitrary JavaScript into generated factory code, which then executes with the privileges of whatever process consumes the generated client. Exploitation is not remote against a deployed service: it requires the non-default factoryMethods and useDates options to be enabled, a developer running codegen against a spec the attacker can influence, and the resulting factory client being executed, giving an assessed CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (the advisory lists 9.2 under CVSS 4.0). No public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); the vendor has shipped a fix in 8.30.0.