Loading story…
A critical vulnerability tracked as CVE-2026-69098 affects Cinnamon's Kotaemon through version 0.12.0, allowing unauthenticated remote code execution through the Gradio-exposed /check_connection endpoint. The flaw arises because attacker-supplied YAML or JSON is deserialized with insecure settings, letting a request include a __type__ field that instantiates arbitrary Python classes on the server.
Public reporting says the issue can be exploited without credentials, API keys, or user interaction by abusing reachable event-handler endpoints such as /check_connection and /create_llm. Attackers can reportedly set __type__ to functions such as subprocess.check_output and pass arbitrary arguments to execute operating system commands with the application's privileges, creating risks of file access, database or code modification, and service disruption; the issue is classified as CWE-502 and has been rated critical, with one report assigning a CVSS 3.1 score of 10.0.
Track how attackers are adapting to this technology.
2 events from the most recent confirmed update back to the earliest known activity.
The insecure deserialization vulnerability in Cinnamon's Kotaemon through version 0.12.0 was newly received as CVE-2026-69098. The CVE description states that crafted YAML or JSON input with a __type__ field can be abused to instantiate arbitrary Python classes and achieve unauthenticated remote code execution.
A GitHub issue disclosed a critical unauthenticated remote code execution flaw in Kotaemon 0.12.0, caused by publicly reachable Gradio endpoints and unsafe deserialization in the /check_connection endpoint. The write-up described how attackers could execute OS commands without credentials or user interaction.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
2 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A critical vulnerability in the MajorDoMo home automation platform, tracked as **`CVE-2026-27174`**, allows unauthenticated remote code execution on internet-facing servers. The flaw stems from improper authentication handling in **`/admin.php`**, where requests continue to be processed after a redirect, combined with unsafe use of PHP **`eval()`** on attacker-controlled input in an internal AJAX console/debugging component. Researchers reported that a single crafted HTTP GET request can reach the internal handler and execute arbitrary PHP code without valid credentials. Successful exploitation can give attackers full server compromise, including the ability to run system commands, read sensitive files, steal credentials, and deploy persistent web shells. Because MajorDoMo is often used to manage cameras, sensors, locks, and other building or home automation systems, a breach can also expose connected IoT environments and support lateral movement into internal networks. Public detection content, including a **Nuclei** template, is already available, raising the risk of rapid exploitation, and defenders have been urged to apply the vendor patch, restrict admin access to trusted networks, place the interface behind a VPN or authenticated reverse proxy, disable the console feature where possible, audit logs, and rotate secrets.
Jun 29, 2026
BMC Control-M deployments are affected by two newly disclosed vulnerabilities that expose `Control-M/Server` and related components to serious remote attacks. **CVE-2026-10539** is a critical unauthenticated command injection flaw in Control-M/Server communication commands that can let a remote attacker execute unauthorized commands and potentially fully compromise a server. The issue affects `Control-M/Server` versions `9.0.20.x` through `9.0.21.200`, and possibly earlier unsupported releases, and is rated `CVSS 4.0 9.5` / `CVSS 3.1 9.0`. A second issue, **CVE-2026-10538**, is a high-severity improper deserialization vulnerability in out-of-support `Control-M/Server` and `Control-M/Enterprise Manager` `9.0.20.x` components, particularly in messaging consumer functionality that processes user-controlled serialized data. An authenticated attacker could remotely trigger unintended server-side behavior through crafted serialized content; the flaw is rated `CVSS 4.0 8.9` / `CVSS 3.1 8.0`. Organizations running affected Control-M versions have been advised to upgrade to supported releases, apply vendor patches, harden deserialization controls, restrict access to exposed services, and monitor for suspicious command execution or messaging activity.
Jul 3, 2026
Active exploitation has been observed against an Apache ActiveMQ remote code execution chain involving the Jolokia management API. VulnCheck reported canary-network hits tied to `CVE-2026-34197`, which was added to CISA's Known Exploited Vulnerabilities catalog, and said attackers are also using an unauthenticated variant that chains `CVE-2024-32114` with `CVE-2026-34197` to achieve zero-credential RCE. According to the reporting, `CVE-2024-32114` removes authentication from the Jolokia endpoint in ActiveMQ versions `6.0.0` through `6.1.1`, exposing the management interface to unauthenticated abuse. Technical details published by Horizon3.ai describe the RCE path through the Jolokia API, while VulnCheck said observed payloads invoked `addNetworkConnector` through Jolokia during exploitation. One captured payload referenced a private IP address, indicating the attacker activity may have reused a lab or proof-of-concept configuration, but the exploitation itself was confirmed in the wild. The combined reporting indicates that exposed ActiveMQ instances with vulnerable Jolokia configurations face immediate risk of unauthenticated remote compromise.
Jun 29, 2026