Authenticated code execution in Plex Media Server before 1.43.3.10861 is a genuine but privilege-gated code-execution flaw: an attacker who first obtains admin-level access to the server's management interface can leverage the TranscoderH264Options preference, which is appended verbatim to x264's option string on every transcode, or write a malicious .so file that is loaded and executed at startup without signature, execute-bit, or symbol checks. This affects servers running versions prior to 1.43.3.10861; no public exploit was identified at time of analysis, and the supplied CVSS 4.0 score is 8.6 with PR:H, consistent with our independent CVSS 3.1 assessment requiring high privileges (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Because Plex admin is often the single server-owner account, the realistic attack path is credential compromise or exposure of the admin interface to untrusted networks; execution then occurs on the next transcode or after a server restart.
Improper neutralization of URL values in Plex Media Server's 'searchOne' parameter allows a remote attacker to invoke other plugins' functions and supply their own arguments, affecting all releases before 1.43.3.10861. The flaw is scored 6.9 (medium) under CVSS 4.0 (AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N), and an independent assessment agrees on a network-reachable, low-complexity request-forgery/parameter-injection class issue with only LOW confidentiality and integrity impact and no availability impact: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. No public exploit code was identified at time of analysis (a third-party writeup is referenced in the source list, but that is not confirmation of weaponization), and the vector's PR:N claim should be validated in practice because Plex APIs commonly require a server token and real-world exposure depends on whether the server or its API is reachable beyond localhost.
Server-side request forgery in Plex Media Server before 1.43.3.10861 allows any authenticated user - including a low-trust account invited only to a shared library - to coerce the server into issuing HTTP requests to arbitrary internal or external addresses through the path parameter of the '/video/:/transcode/universal' endpoint. The attacker gains no code execution and the assessed impact is confidentiality-only and limited (CVSS 4.3, C:L/I:N/A:N), but the flaw is a useful internal-network reconnaissance and pivot primitive on internet-facing or flat-network deployments. No public exploit identified at time of analysis; exploitation requires a valid authenticated session and a server running a version prior to 1.43.3.10861.
Server-side request forgery in Plex Media Server before 1.43.3.10861 allows a low-privileged, token-bearing caller to force the server to POST to an arbitrary destination by putting a full URL in the 'protocol' parameter of the '/player/timeline' endpoint. Because any X-Plex-Token value is accepted, the authentication barrier is effectively trivial, but the assessed impact is limited to a blind outbound request (confidentiality-low, no integrity or availability effect) against hosts reachable by the Plex process. No CISA KEV entry and no confirmed exploitation have been reported, and no public exploit code was identified at time of analysis; the practical risk is a genuine but low-priority SSRF that matters most for internet- or DMZ-exposed servers that can reach sensitive internal services.
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.
OS command injection in the frictionless-py framework through 5.20.0rc1 lets unauthenticated remote attackers execute arbitrary operating system commands in the victim's security context when the victim runs the `frictionless explore` console command against an attacker-supplied Data Package. The flaw is reachable because resource path values from an untrusted datapackage.json are concatenated unsanitized into a shell invocation (`vd {paths}` via os.system), so shell metacharacters placed in a path are interpreted by the shell rather than treated as a filename. Exploitation requires victim interaction (CVSS UI:A) - the user must deliberately explore the malicious package - and publicly available exploit code exists, including a proof-of-concept repository; there is no data provided indicating confirmed active exploitation, and the assessed CVSS:3.1 vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (vendor CVSS:4.0 8.6, PR:N/UI:A), so impact is high on confidentiality, integrity and availability of the user's environment but gate-controlled by the social-engineering step.
Unauthenticated blind SQL injection in ClipBucket v5 (before 5.5.3-#182) allows remote attackers to extract sensitive database contents-including user credentials, email addresses, and administrator password hashes-via the photo search endpoint's unsanitized query parameter. Publicly available exploit code exists (HackMD writeup), and the vendor has released a patch (PR #874 / commit 7fd0af6f) that applies mysql_clean() to the vulnerable input. Because the vulnerability requires no authentication or user interaction and the assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) confirms high confidentiality impact, this is a genuine priority for immediate remediation; successful exploitation can lead to account takeover after offline cracking of admin hashes.
SQL injection in the Rule Management Search Reports feature of ManageEngine OpManager and Firewall Analyzer 12.8.669 and earlier allows a remote, authenticated low-privilege user to inject arbitrary SQL through a search parameter, giving them database read and write capability with high confidentiality, integrity, and availability impact (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is rated CVSS 8.8 and affects on-premises ITOM deployments exposing the web console; exploitation requires prior possession of valid credentials at any privilege tier, so it is not a pre-authentication flaw. At time of analysis there is no public exploit identified and no confirmed active exploitation, but the vendor has released a patch in version 12.8.670, making upgrade the decisive remediation step.
Account takeover in Klever-Go's KleverUpdateAccountPermission built-in (all versions prior to 1.7.20) allows an attacker-controlled smart contract to replace a victim account's entire permission set without any victim key or signature. The handler authorizes updates using the attacker-supplied vmInput.RecipientAddr instead of the authenticated vmInput.CallerAddr, and because the default self-signer created by createDefaultOwnerPermission satisfies the contractHasValidPermission check, a contract can name any permissioned victim as recipient and install attacker-supplied Owner permissions - enabling asset theft or permanent lockout of the victim. The CVSS 4.0 score is 8.7 with a low-privilege vector (PR:L), reflecting that the attacker must be able to deploy or control a contract that can issue an indirect built-in call; accounts without stored permissions and the native transaction path are not affected. Exploitation requires no user interaction, and no public exploit code or confirmed active exploitation was identified at time of analysis; this is nevertheless a genuine high-priority vulnerability given its unauthenticated-from-the-victim's-perspective account takeover impact on a production blockchain.
Maliciously crafted on-chain account names processed by Klever-Go prior to 1.7.20 are spliced into Elasticsearch _bulk request bodies without JSON escaping, allowing an attacker who can submit a SetAccountName transaction to inject forged bulk actions that create, overwrite, or delete documents in any index the indexer can write to. Because the name is stored in consensus account state, the poisoned value is replayed by new and historical indexers, and no access to the indexing host or the Elasticsearch port is required. Severity is rated 8.4 (CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:L; our independent assessment CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H), exploitation requires an authenticated low-privilege on-chain account plus a deployment that actually runs the Elasticsearch indexer, and the issue is fixed in 1.7.20; no public exploit identified at time of analysis, though the upstream fix ships a regression test that reproduces the advisory's injection construction.
Tauri's automatic CSP nonce injection - a hardening feature meant to restrict script execution inside the app webview - is rendered completely ineffective when the application's own script-src directive lists the data: or blob: scheme sources, because CSP Level 3 keeps scheme sources active regardless of a nonce being present. An attacker who can place markup or script into webview content in such an application can therefore execute arbitrary script without ever knowing the nonce, enabling script execution, data theft, or privilege abuse through the embedded webview; Tauri applications that retain the default hardened CSP without data: or blob: in script-src are not affected. The issue is rated CVSS 8.3 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) but is gated by a non-default developer configuration choice plus a separate injection vector within the app, and no public exploit was identified at time of analysis.
Path traversal in ABB Mint Workbench I through version 5876 allows any local user to reach files outside the intended restricted directory, giving high confidentiality impact on the vulnerable host and on a subsequent system while leaving integrity and availability untouched. Exploitation is gated by local access - the CVSS vector specifies AV:L with PR:N and UI:N - so exposure is confined to engineering workstations and commissioning laptops running the affected build rather than servers or internet-facing systems. No public exploit code and no confirmed active exploitation have been identified at time of analysis; ABB has published vendor advisory 9AKK108473A3188.
An authentication bypass in the EthPress - Web3 Login WordPress plugin, affecting all versions up to and including 2.3.5, allows unauthenticated remote attackers to log in as any WordPress user with a linked Ethereum wallet address - including administrators - simply by supplying that user's public wallet address together with an arbitrary, well-formed (but invalid) signature, resulting in full site takeover. The root cause is a missing return statement in verify_login() that lets execution fall through to the cookie-setting login routine even when signature verification fails; no public exploit code has been identified at time of analysis, and the assessment rates it 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), with the 'high' attack complexity reflecting the need to discover a valid linked wallet address rather than any authentication barrier. Because exploitation is unauthenticated and requires no user interaction, any site where at least one account (especially an administrator) has linked a wallet should be treated as exposed until patched or the plugin is disabled.
Use-after-free in librsvg during rendering of crafted SVG documents with nested XInclude directives and duplicate entity declarations allows unauthenticated local attackers to crash or potentially execute code in applications that use the library. Tracked as CVE-2026-96889 and reported by Red Hat, the flaw affects librsvg as shipped in Red Hat Enterprise Linux 6, 7, 8, 9, and 10. Exploitation requires user interaction (UI:R) because a victim must open, preview, or thumbnail a malicious SVG; the CVSS 3.1 score is 7.8. No public exploit code was identified at time of analysis, and independent assessment indicates that arbitrary code execution is unproven-only denial of service or crash is reliably reachable.
Denial of service in Wire's Swift runtime (the SPM/CocoaPods 'Wire' product, implemented by wire-runtime-swift) lets an unauthenticated remote attacker abort a decoding process with a single 10-byte protobuf payload; all released Swift runtime versions through 6.4.0 and Wire 7 alphas through 7.0.0-alpha03 are affected. An unknown START_GROUP field wrapping a LENGTH_DELIMITED field whose varint decodes to a negative Int32 (for example -128) slips past a bounds check in ReadBuffer.readData(count:) that only validates the upper bound, and the negative count reaches Foundation's Data(bytes:count:), which traps with SIGTRAP instead of throwing the documented, catchable ProtoDecoder.Error. Publicly available exploit code exists (the vendor advisory ships a complete proof of concept), but there is no indication of active exploitation; the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5) reflects a low-complexity remote availability impact confined to Swift applications that actually feed untrusted protobuf bytes to Wire's decoder.
Denial of service in JLine3's built-in grep command (org.jline:jline-builtins) lets anyone who can supply a search pattern hang a worker thread indefinitely via catastrophic regular-expression backtracking. The builtin - reachable in applications that embed JLine3 and expose the shell to remote or interactive users - rewrites non-line-regexp patterns as .*pattern.* before compiling them with Java's backtracking regex engine, so a short input such as (a+)+b tested against non-matching text causes exponential CPU consumption (CWE-1333; CVSS 3.1 base 7.5 upstream, while the assessed vector requires low privileges, PR:L). Impact is availability-only (C:N/I:N/A:H) with no confidentiality or integrity loss; publicly available exploit code exists in the form of the advisory's two-line PoC, but the issue is not listed in CISA KEV and no confirmed active exploitation has been reported. Vendor-fixed releases are available: 3.30.15 on the 3.x line and 4.3.1 on the 4.x line.
Unauthenticated remote denial of service in Klever-Go (all versions before 1.7.20) allows any client that can reach the node's REST/WebSocket API to exhaust its memory and goroutines through the default-open /subscribe endpoint, and because that API runs in-process with the node, the resulting OOM-kill also takes down P2P and consensus participation. No API key, account, stake, or funds are required (vector PR:N), and publicly available exploit code exists: the vendor advisory ships working PoCs against unmodified production code showing a single 8 MiB WebSocket frame expanding server heap by roughly 32 MiB, 300 concurrent connections accepted despite a configured global cap of 100, and 200,000 attacker-supplied address strings growing the hub's subscription map 1:1 with no cap. The assessed severity is CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), and real-world priority is bounded mainly by Klever-Go's limited node footprint rather than by any weakness in the finding itself.
Improper enforcement of the marketplace settlement workflow in Klever-Go prior to 1.7.20 lets an authenticated seller settle a resting-bid NFT auction through the Claim seller-accept branch while leaving the claimed order loadable with a future EndTime and stale CurrentBid/CurrentBidder values. A later bidder can then submit a higher bid, be debited, and trigger a refund to the previous bidder even though the NFT has already been delivered, while Claim and CancelOrder both reject that bidder because IsClaimed is true - leaving them unable to obtain the NFT or recover their funds. The flaw is purely an integrity/business-logic issue (CWE-841, assessed CVSS:3.1 7.1, AV:N/AC:L/PR:L/UI:N with no confidentiality or availability impact, matching the vendor's 7.1 CVSS 4.0 rating); no public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor fix is available in 1.7.20.
Catastrophic regex backtracking in the JLine3 `nano` editor's regex search mode allows an authenticated user to hang the editor session thread at high CPU, producing a denial of service. The flaw affects applications that embed `org.jline:jline-builtins` and expose the nano editor: `jline-builtins` 3.0.0 through 3.30.14 and 4.0.0 through 4.3.0 are impacted (CWE-1333, CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). A proof-of-concept reproduction, using a buffer of repeated 'a' characters and the pattern `(a+)+b`, is documented in the vendor advisory, and vendor-released patches exist in 3.30.15 and 4.3.1; no confirmed active exploitation (CISA KEV) or public exploit code beyond the advisory PoC has been reported. Practical severity depends on deployment: in a single-user local terminal the user only hangs their own session, whereas remote multi-user services that share worker threads can lose a server thread indefinitely.
Unauthenticated attackers can execute registered shortcodes server-side and read unpublished recipe content on WordPress sites with comments enabled that use the WP Recipe Maker plugin before 10.8.2. The vulnerability occurs because comment content is shortcode-expanded during structured metadata generation without stripping shortcodes, allowing any available shortcode to run. Publicly available exploit code exists, and the CVSS 3.1 score is 6.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N), indicating network-reachable, low-complexity exploitation with no authentication or user interaction and low confidentiality/integrity impact limited to shortcode capabilities and disclosure of unpublished recipes.
Cross-site request forgery in REDAXO CMS 5.21.1 and earlier lets a remote, unauthenticated attacker (CVSS PR:N with UI:R) lure a logged-in backend administrator into silently triggering an addon update or downgrade from the REDAXO package server via a single forged request to index.php?page=install/packages&rex-api-call=install_package_update. The attacker must know or guess a valid addonkey and target file id, and the admin must have an active session and visit an attacker-controlled page, so this is a genuine but conditional-risk flaw rather than a drop-everything emergency; absent a supply-chain compromise of a redaxo.org package or a vulnerable prior version to downgrade to, the practical impact is limited to forced or unwanted addon installs and site disruption. No active exploitation in CISA KEV has been reported, and no public exploit identified at time of analysis beyond the minimal image-tag proof-of-concept published in the vendor advisory.
Denial of service in python-hyper/hpack prior to 4.2.0 allows unauthenticated remote attackers to force run-away computation by supplying malformed HTTP/2 header input containing a variable-length integer encoded as a long run of 0xFF octets; the pre-fix decoder imposes no upper bound on the integer length, producing O(n^2) decoding work that effectively blocks the processing path. The library is a core HPACK header-compression dependency of Python HTTP/2 stacks (h2/hyper), so any internet-facing or otherwise reachable Python HTTP/2 server or client that decodes attacker-influenced headers is exposed, though impact is limited to availability of the affected worker with no confidentiality or integrity effect. No KEV entry or public exploit code was identified at time of analysis, and risk is bounded: the vendor-released fix in hpack 4.2.0 caps variable integer decoding to uint32, and a documented input-sanitization workaround exists.
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.
Arbitrary shortcode execution in the WordPress plugin Ninja Tables before 5.2.17 lets an unauthenticated visitor execute arbitrary shortcodes and permanently break a public page by submitting an ordinary form entry, provided the site is running a non-default configuration in which user-submitted rows are rendered with shortcode expansion. Affected sites require no authentication and no victim interaction (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L, score 5.6); default installations do not expand shortcodes in non-administrator-authored rows and are therefore not exposed, which is why the vendor rated attack complexity as High. Publicly available exploit code exists via the WPScan advisory, but there is no indication of confirmed actively exploited (CISA KEV) status, so priority is bounded by the configuration prerequisite.
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.
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.
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.
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.
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.
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.
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.
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'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.
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.
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.