Skip to content

Security Sense

AI Threat Intelligence

  • About
  • Blog
  • Privacy Policy

CVE-2026-114625: Critical SQL Injection in Arista VeloCloud Orchestrator

Posted on November 3, 2026 by Kyle

Overview

CVE-2026-114625 is a critical SQL injection vulnerability affecting Arista VeloCloud Orchestrator (VCO) on-prem deployments. This flaw allows any authenticated user to escalate privileges to a “superuser operator,” accessing internal functionality not intended for remote exposure. The vulnerability is actively being exploited, posing a severe risk to the confidentiality, integrity, and availability of affected systems.

Technical Analysis

  • Vulnerability: SQL Injection (CWE-89).
  • Impact: Allows authenticated users to gain “superuser operator” privileges, access privileged internal functionality, and compromise confidentiality, integrity, and availability of the VCO host and managed data.
  • Attack Vector: Remote, authenticated user (CVSS AV:N, PR:L).
  • Affected Products (on-prem only):
    • Arista VeloCloud Orchestrator versions >= 5.2.0 < 5.2.3.18
    • Arista VeloCloud Orchestrator versions >= 6.1.0 < 6.1.3.10
    • Arista VeloCloud Orchestrator versions >= 6.4.0 < 6.4.2.12
  • CVSS 3.1 Score: 9.9 (CRITICAL) – CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
  • Note: Hosted and Dedicated versions of VCO were impacted but have already been patched by Arista.

Detection

  • Monitor web server access logs for unusual requests containing SQL injection payloads (e.g., UNION SELECT, SLEEP(), WAITFOR DELAY, ' OR 1=1 --).
  • Look for repeated authentication attempts or successful logins followed by rapid privilege escalation or access to unusual administrative endpoints.
  • Analyze application logs for SQL errors or unexpected database query executions, especially from authenticated user sessions.
  • Monitor for changes in user privileges or the creation of new highly privileged accounts within the VeloCloud Orchestrator.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

VeloCloud Orchestrator – SQL Injection Pattern in URI

title: VeloCloud Orchestrator - SQL Injection Pattern in URI
id: 9a2b1c3d-4e5f-6a7b-8c9d-0e1f2a3b4c5d
status: experimental
description: Detects common SQL injection patterns within the URI or query parameters of web requests, potentially targeting Arista VeloCloud Orchestrator.
logsource:
  category: webserver
detection:
  selection_keywords:
    cs-uri-query|contains:
      - 'union select'
      - 'sleep('
      - 'waitfor delay'
      - ''' or ''1''=''1'
      - 'information_schema'
      - 'pg_sleep('
      - 'benchmark('
      - 'xp_cmdshell'
    cs-uri-stem|contains:
      - 'union select'
      - 'sleep('
      - 'waitfor delay'
      - ''' or ''1''='
      - 'information_schema'
      - 'pg_sleep('
      - 'benchmark('
      - 'xp_cmdshell'
  condition: selection_keywords
level: high

Mitigations

  1. Immediately apply available security patches from Arista. Refer to Arista Security Advisory 24838-security-advisory-0199 for specific versions.
    • For 5.2.x series, upgrade to 5.2.3.18 or later.
    • For 6.1.x series, upgrade to 6.1.3.10 or later.
    • For 6.4.x series, upgrade to 6.4.2.12 or later.
  2. Implement robust input validation and parameterized queries for all user-supplied input to prevent SQL injection.
  3. Enforce the principle of least privilege for all users, especially those with access to the VCO interface.
  4. Regularly review and audit user accounts and their assigned privileges within the VeloCloud Orchestrator.
  5. Deploy a Web Application Firewall (WAF) to help detect and block common SQL injection attack patterns.

References

  • https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199
  • https://nvd.nist.gov/vuln/detail/CVE-2026-114625
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-114625

Indicators of Compromise

Type Value Description
IP Address 38.54.50.151 Potential malicious IP identified as an indicator of compromise (via https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199)
IP Address 74.82.197.86 Potential malicious IP identified as an indicator of compromise (via https://www.arista.com/en/support/advisories-notices/security-advisory/24838-security-advisory-0199)

MITRE ATT&CK

  • T1190 — Exploit Public-Facing Application
  • T1078.003 — Local Accounts
  • T1133 — External Remote Services
  • T1082 — System Information Discovery
  • T1071 — Application Layer Protocol
  • T1595.002 — Vulnerability Scanning
  • T1505.003 — Web Shell
  • T1548 — Abuse Elevation Control Mechanism
  • T1210 — Exploitation of Remote Services
  • T1098 — Account Manipulation
  • T1078 — Valid Accounts
  • T1068 — Exploitation for Privilege Escalation
  • T1046 — Network Service Discovery
🤖 AI Attribution
Generated by gemini-2.5-flash ·
2,135 input / 1,391 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged active exploitation, arista, critical, sql injection, velocloud orchestrator, vulnerability, zero-dayLeave a comment

CVE-2026-110447: Collabora Online Built-in CODE Server OS Command Injection

Posted on November 3, 2026 by Kyle

Overview

CVE-2026-110447 is a critical OS command injection vulnerability affecting the Collabora Online Built-in CODE Server, specifically when deployed as a Nextcloud app. This flaw enables remote code execution, allowing attackers to execute arbitrary commands on the underlying system. It is currently being exploited in the wild, making immediate patching crucial for affected Nextcloud instances.

Technical Analysis

The vulnerability, CWE-78 (Improper Neutralization of Special Elements used in an OS Command), resides in the proxy.php component of the Collabora Online Built-in CODE Server (richdocumentscode) Nextcloud app.
* It affects versions prior to 26.4.303.
* Exploitation occurs when the CODE server is not actively running, such as immediately after a system restart or if the service has crashed.
* Attackers can inject arbitrary OS commands, leading to remote code execution (RCE) on the host system.
* This vulnerability specifically impacts Nextcloud deployments utilizing the Built-in CODE Server and does not affect standalone Collabora Online servers.
* Active exploitation has been observed in the wild, with XMRIG malware linked to post-exploitation activities.

Detection

  • Monitor web server access logs for requests to /index.php/apps/richdocumentscode/proxy.php containing suspicious command injection patterns (e.g., |, &, ;, $(...), ` followed by OS commands).
  • Look for unusual process spawns originating from the web server process (e.g., apache, nginx, php-fpm) that execute shell commands (sh, bash, cmd.exe, powershell.exe) or known malware binaries like XMRIG.
  • Monitor for unexpected outbound network connections from the web server to known C2 infrastructure or cryptocurrency mining pools.
  • Review system logs for errors related to the CODE server not running, which could indicate a vulnerable state.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Collabora Online CODE Server RCE Process Spawn

title: Collabora Online CODE Server RCE Process Spawn
id: c8f1e2d3-b4a5-6c7d-8e9f-0a1b2c3d4e5f
status: experimental
description: Detects suspicious process creation by web server processes, indicative of successful OS command injection in Collabora Online Built-in CODE Server (CVE-2026-110447).
logsource:
  product: linux
  service: auditd
detection:
  selection:
    ParentImage|endswith:
      - '/usr/sbin/apache2'
      - '/usr/sbin/httpd'
      - '/usr/bin/php-fpm'
      - '/usr/bin/nginx'
    Image|endswith:
      - '/bin/sh'
      - '/bin/bash'
      - '/usr/bin/wget'
      - '/usr/bin/curl'
      - '/usr/bin/python'
      - '/usr/bin/perl'
      - '/usr/local/bin/xmrig'
  condition: selection
level: critical

Collabora Online CODE Server Command Injection Attempt

title: Collabora Online CODE Server Command Injection Attempt
id: f0e1d2c3-a4b5-6d7e-8f9a-0b1c2d3e4f50
status: experimental
description: Detects patterns in web access logs indicative of OS command injection attempts against Collabora Online Built-in CODE Server (CVE-2026-110447).
logsource:
  category: webserver
  service: ['apache', 'nginx']
detection:
  selection:
    c-uri|contains:
      - '/index.php/apps/richdocumentscode/proxy.php'
      - '|'
      - '&'
      - ';'
      - '$('
      - '`'
      - 'cat /etc/passwd'
      - 'id'
      - 'whoami'
      - 'wget'
      - 'curl'
      - 'nc -e'
      - 'bash -i'
      - 'php -r'
  condition: selection
level: high

Mitigations

  1. Immediately update the Collabora Online Built-in CODE Server (richdocumentscode) Nextcloud app to version 26.4.303 or later.
  2. Ensure the CODE server service is configured for automatic restart and is actively running to reduce the window of vulnerability.
  3. Implement strict egress filtering to prevent unauthorized outbound connections from web servers, especially to cryptocurrency mining pools or unknown IP addresses.
  4. Apply the principle of least privilege to the web server user and associated processes to limit the impact of successful exploitation.
  5. Regularly back up critical data and test restoration procedures.

References

  • https://github.com/CollaboraOnline/richdocumentscode/issues/354
  • https://help.nextcloud.com/t/to-collabora-built-in-user-update-asap/250516
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-110447

Indicators of Compromise

Type Value Description
SHA256 19cd1fe4e501fbdf6e52a7249a7bd375ea3039feed596f56691fb7f353acc23f XMRIG · confidence 100% · first seen 2026-10-23
SHA256 2a6e2516b103c2f313d280e2e5954db9111515e401e603ebb6d4b47a65b086fb XMRIG · confidence 100% · first seen 2026-10-23
SHA256 4230d003e25b12be26130c9d941ef0b809dc7da2a25ecbf8d15a0c369730ebd0 XMRIG · confidence 100% · first seen 2026-10-23
SHA256 5220cce8158699825c206529746ad1cbb20d930eff244017f8c3f913b83a3d86 XMRIG · confidence 100% · first seen 2026-10-23
SHA256 9aade612521dab5600f59b0660e19fb8392a42570408673e824f3bbd2532c85b XMRIG · confidence 100% · first seen 2026-10-23
SHA256 c5bd9b66d5535c2dffa253cb6dd665d20208db58793fd176d4773093546f50df XMRIG · confidence 100% · first seen 2026-10-23
SHA256 e15d2363b9e4552250f230c62188cb299ff2570c9ba9589fbc3e190df84768ba XMRIG · confidence 100% · first seen 2026-10-23
IP Address 103.194.186.118 XMRIG · confidence 95% · first seen 2026-10-23
IP Address 212.83.185.19 XMRIG · confidence 95% · first seen 2026-10-23
URL http://212.83.185.19/bottom-xe.png XMRIG · confidence 100% · first seen 2026-10-23
URL http://212.83.185.19/footerd.png XMRIG · confidence 100% · first seen 2026-10-23
URL http://cqzbr8a4.requestrepo.com XMRIG · confidence 90% · first seen 2026-10-23

MITRE ATT&CK

  • T1190 — Exploit Public-Facing Application
  • T1059.004 — Unix Shell
  • T1496 — Resource Hijacking
🤖 AI Attribution
Generated by gemini-2.5-flash ·
2,000 input / 1,471 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged collabora, command-injection, critical, linux, nextcloud, rce, vulnerability, webappLeave a comment

CVE-2026-110936: Siemens Software Center DLL Side-Loading Vulnerability Actively Exploited

Posted on November 3, 2026 by Kyle

Overview

CVE-2026-110936 is an uncontrolled search path element vulnerability affecting Siemens Software Center. An authenticated local attacker can exploit this by placing a specially crafted DLL in a directory searched by the application, leading to arbitrary code execution. This vulnerability is actively being exploited in the wild, making immediate patching crucial for affected organizations.

Technical Analysis

The vulnerability, classified as CWE-427 (Uncontrolled Search Path Element), resides in how Siemens Software Center loads dynamic-link libraries. The application searches an uncontrolled path, allowing an attacker to introduce a malicious DLL. When the Siemens Software Center application is subsequently executed, it loads the attacker’s DLL instead of a legitimate one, resulting in arbitrary code execution with the privileges of the affected application.

  • Vulnerability Type: Uncontrolled Search Path Element (CWE-427)
  • Affected Products: Siemens Software Center, all versions prior to V4.0.9.8
  • Attack Vector: Local, authenticated attacker (AV:L, PR:H)
  • Impact: Arbitrary code execution (C:H, I:H, A:H)
  • CVSS 3.1 Score: 6.7 (Medium)
    • Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Detection

Defenders should focus on monitoring for unusual process execution patterns originating from the Siemens Software Center application, as well as suspicious file modifications in relevant directories.

  • Process Creation Monitoring: Look for SiemensSoftwareCenter.exe spawning unusual child processes, especially command shells (cmd.exe), scripting interpreters (powershell.exe, wscript.exe, cscript.exe), or other unexpected executables.
  • DLL Load Monitoring: Monitor for SiemensSoftwareCenter.exe loading DLLs from non-standard or user-writable directories (e.g., user profile directories, temporary folders) rather than system or application installation paths.
  • File System Monitoring: Detect creation or modification of new DLL files in directories that SiemensSoftwareCenter.exe is known to search, particularly if these files are written by processes other than legitimate installers or update mechanisms.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Siemens Software Center Spawning Shell

title: Siemens Software Center Spawning Shell
id: 9283740e-1a2b-4c3d-5e6f-789012345678
status: experimental
description: Detects suspicious child process creation by Siemens Software Center, indicative of arbitrary code execution via DLL side-loading (CVE-2026-110936).
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    ParentImage|endswith: '\\SiemensSoftwareCenter.exe'
    Image|endswith:
      - '\\cmd.exe'
      - '\\powershell.exe'
      - '\\wscript.exe'
      - '\\cscript.exe'
  condition: selection
level: high

Mitigations

Prioritize patching and implement robust access controls to limit the potential impact of this vulnerability.

  1. Patch Immediately: Update Siemens Software Center to version V4.0.9.8 or later. Refer to the official Siemens advisory for specific update instructions.
  2. Least Privilege: Ensure that users operating Siemens Software Center do so with the absolute minimum necessary privileges. This limits the impact of arbitrary code execution.
  3. Restrict Write Access: Implement strict file system permissions to prevent unauthorized users from writing files, especially DLLs, into directories within the application’s search path.

References

  • https://nvd.nist.gov/vuln/detail/CVE-2026-110936
  • https://cert-portal.siemens.com/productcert/html/ssa-580366.html
  • https://productcert.siemens.com/news/2026/10/19/active-exploitation-of-cve-2026-110936-in-siemens-software-center/
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-110936
  • https://ltna.com.au/cyber
  • https://socprime.com/blog/cve-2026-110936-analysis/

Indicators of Compromise

Type Value Description
SHA256 3fdcc7d7d049a89711fb31fb236940a1c5a09d899143ffd20c3c41fb1f2cf491 Hash of the malicious DLL file archive.dll (via https://productcert.siemens.com/news/2026/10/19/active-exploitation-of-cve-2026-110936-in-siemens-software-center/)
SHA256 f4d7c5321bb0d1bda439304a753bcf9b467b98ca53c7e9493b9c2c3451092e4a Hash of the malware bundle AllMyBasic.msi (via https://productcert.siemens.com/news/2026/10/19/active-exploitation-of-cve-2026-110936-in-siemens-software-center/)
IP Address 2.27.248.127 Distribution channel of the malware bundle AllMyBasic.msi (via https://productcert.siemens.com/news/2026/10/19/active-exploitation-of-cve-2026-110936-in-siemens-software-center/)
IP Address 96.62.218.59 Payload hosting / Command and control server (via https://productcert.siemens.com/news/2026/10/19/active-exploitation-of-cve-2026-110936-in-siemens-software-center/)
Domain wizardexpensive.com Payload hosting / Command and control domain (via https://productcert.siemens.com/news/2026/10/19/active-exploitation-of-cve-2026-110936-in-siemens-software-center/)

MITRE ATT&CK

  • T1574.001 — DLL
  • T1059 — Command and Scripting Interpreter
  • T1053.005 — Scheduled Task
  • T1036.005 — Match Legitimate Resource Name or Location
  • T1204.002 — Malicious File
  • T1566.002 — Spearphishing Link
  • T1082 — System Information Discovery
  • T1218.007 — Msiexec
  • T1140 — Deobfuscate/Decode Files or Information
  • T1083 — File and Directory Discovery
  • T1059.001 — PowerShell
  • T1547.001 — Registry Run Keys / Startup Folder
  • T1562.001 — Disable or Modify Tools
  • T1078 — Valid Accounts
  • T1027 — Obfuscated Files or Information
  • T1486 — Data Encrypted for Impact
  • T1218.010 — Regsvr32
  • T1518.001 — Security Software Discovery
  • T1059.003 — Windows Command Shell
  • T1071.001 — Web Protocols
  • T1574.002 — DLL Side-Loading
  • T1105 — Ingress Tool Transfer
🤖 AI Attribution
Generated by gemini-2.5-flash ·
2,160 input / 1,322 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged actively exploited, cve, dll-side-loading, industrial software, medium, romulus, siemens, vulnerability, windowsLeave a comment

CVE-2026-96652: Plex Media Server SSRF Vulnerability Exploited for Cryptomining

Posted on November 3, 2026 by Kyle

Overview

CVE-2026-96652 is a Server-Side Request Forgery (SSRF) vulnerability affecting Plex Media Server. This flaw enables an attacker with any valid X-Plex-Token to coerce the server into making POST requests to an attacker-controlled destination. The vulnerability is actively exploited, frequently as part of a chain with other Plex vulnerabilities (CVE-2026-96654, CVE-2026-96655, CVE-2026-96656) to facilitate the deployment of cryptominers and other malicious payloads.

Technical Analysis

Plex Media Server versions prior to 1.43.3.10861 are vulnerable to SSRF. The vulnerability resides in the /player/timeline endpoint, where an attacker can supply a full URL within the protocol parameter. This forces the Plex server to initiate a POST request to the specified external destination.

  • Vulnerability Type: Server-Side Request Forgery (SSRF) – CWE-918.
  • Affected Versions: Plex Media Server before 1.43.3.10861.
  • Attack Vector: Network (AV:N).
  • Prerequisites: An attacker requires low privileges (PR:L), specifically any X-Plex-Token value, to exploit this vulnerability. No user interaction (UI:N) is required.
  • Impact: The direct impact is limited to information disclosure (C:L, I:N, A:N) according to CVSS 3.1 base score 4.3 (MEDIUM). However, in observed exploitation, this SSRF is chained with other vulnerabilities to achieve remote code execution and deploy cryptominers.

Detection

Defenders should monitor web server logs and process activity for indicators of exploitation or post-exploitation activity.

  • Web Server Logs: Look for POST requests to /player/timeline where the protocol parameter in the URI contains an external URL (e.g., http://, https://).
  • Network Traffic: Monitor Plex Media Server instances for outbound connections to unusual or suspicious IP addresses and domains, especially on non-standard ports, which could indicate C2 or cryptomining pool communication.
  • Process Creation: Detect unusual process spawns originating from the Plex Media Server process, particularly executables associated with cryptominers (e.g., xmrig.exe) or proxy tools.
  • Resource Utilization: Monitor CPU and memory usage on Plex Media Server hosts for spikes indicative of cryptomining activity.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Plex Media Server SSRF Attempt via Player Timeline

title: Plex Media Server SSRF Attempt via Player Timeline
id: 902b11e2-a7d3-4e8c-84d3-066c1f10a76a
status: experimental
description: Detects attempts to exploit CVE-2026-96652 by monitoring web server logs for POST requests to /player/timeline with an external URL in the 'protocol' parameter.
logsource:
  product: webserver
detection:
  selection:
    cs-uri-stem: '/player/timeline'
    cs-method: 'POST'
    c-uri|contains: 'protocol='
    c-uri|contains|all:
      - '://'
      - 'protocol='
  condition: selection
level: high

Plex Media Server Spawning XMRig Cryptominer

title: Plex Media Server Spawning XMRig Cryptominer
id: 7f1e7a2b-c0d4-4f5a-8b3d-1e1c7d0a9b8c
status: experimental
description: Detects the Plex Media Server process spawning known cryptominer executables like XMRig, indicative of post-exploitation activity.
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    ParentImage|contains: 'Plex Media Server.exe'
    Image|contains: 'xmrig'
  condition: selection
level: critical

Mitigations

Prioritize patching and implement network segmentation to limit potential impact.

  1. Patch Immediately: Upgrade Plex Media Server to version 1.43.3.10861 or later to address CVE-2026-96652 and related vulnerabilities.
  2. Network Segmentation: Isolate Plex Media Server instances on a dedicated network segment with strict egress filtering to prevent unauthorized outbound connections.
  3. Monitor Outbound Traffic: Implement network monitoring to detect and alert on suspicious outbound connections from Plex Media Server hosts.
  4. Endpoint Detection and Response (EDR): Ensure EDR solutions are deployed and configured to monitor for unusual process creation, file modifications, and resource utilization on servers hosting Plex Media Server.
  5. Review Access Controls: Regularly review and enforce least privilege principles for accounts and tokens used with Plex Media Server.

References

  • https://nvd.nist.gov/vuln/detail/CVE-2026-96652
  • https://forums.plex.tv/t/plex-media-server/30447/711
  • https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-266-01.json
  • https://www.cve.org/CVERecord?id=CVE-2026-96652
  • https://zmain.info/blog/plex2shell
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96652
  • https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html
  • https://ltna.com.au/cyber

Indicators of Compromise

Type Value Description
SHA256 2d3c618b21a7e2f8bcd735da188e44a7609ff3f204832dd0781cd09e4388c9db SHA256 hash of XMRig cryptominer (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 5712ef510481f15fe8b18fdd10b73026d57cb3d9d151878a692358b99a464441 SHA256 hash of cryptominer docker file (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 68938fb428f2bcfef4ede62f7b29cd0f15f37ed59e94462c099f2ca64e36baa7 SHA256 hash of UPX packed cryptominer executable (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 b20f39fc00d242e706b6c30367ad811c676e0575050a4ec2f30104b696944b49 SHA256 hash of UPX unpacked cryptominer executable (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 e546b10aee5edc754da4f9b0baace00392257121911f630145078eafad1e6bd9 SHA256 hash of ‘myawesomeproxy’ malware (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 176.65.139.228 Source IP for exploitation attempt (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 217.60.194.116 Source IP for malicious file download (cryptominer) (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 45.194.92.222 Source IP for initial exploitation attempt (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 91.92.40.202 Source IP for exploitation attempt (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain 127.0.0.1.45-194-92-222.sslip.io Dynamic DNS domain used in exploitation URI (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain proxystream.st Domain associated with ‘myawesomeproxy’ malware traffic (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)

MITRE ATT&CK

  • T1190 — Exploit Public-Facing Application
  • T1059.003 — Windows Command Shell
  • T1496 — Resource Hijacking
  • T1583 — Acquire Infrastructure
  • T1133 — External Remote Services
  • T1204.002 — Malicious File
  • T1071 — Application Layer Protocol
  • T1090.002 — External Proxy
  • T1090 — Proxy
  • T1059 — Command and Scripting Interpreter
  • T1583.003 — Virtual Private Server
  • T1204 — User Execution
  • T1571 — Non-Standard Port
  • T1027 — Obfuscated Files or Information
  • T1486 — Data Encrypted for Impact
  • T1573 — Encrypted Channel
  • T1569 — System Services
  • T1027.002 — Software Packing
  • T1071.001 — Web Protocols
  • T1105 — Ingress Tool Transfer
  • T1090.001 — Internal Proxy
🤖 AI Attribution
Generated by gemini-2.5-flash ·
2,195 input / 1,702 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged actively_exploited_kev, cryptominer, medium, plex, remote code execution, ssrf, vulnerability, xmrigLeave a comment

CVE-2026-96655: Plex Media Server SSRF Vulnerability Exploited for Cryptomining

Posted on November 3, 2026 by Kyle

Overview

CVE-2026-96655 is an authenticated Server-Side Request Forgery (SSRF) vulnerability in Plex Media Server. It allows an attacker to force the server to make requests to arbitrary internal or external addresses. This flaw is critical as it is actively being exploited, often chained with other vulnerabilities, to deploy cryptominer malware such as XMRig on compromised servers.

Technical Analysis

  • Vulnerability: Server-Side Request Forgery (SSRF) (CWE-918).
  • Affected Product: Plex Media Server.
  • Affected Versions: Before 1.43.3.10861.
  • Attack Vector: An authenticated user can manipulate the /video/:/transcode/universal path parameter to specify arbitrary URLs for the server to request.
  • Prerequisites: Requires an authenticated user session.
  • Impact: Allows an attacker to scan internal networks, access internal services, or potentially bypass firewall rules. When chained with other vulnerabilities, it can lead to remote code execution and resource hijacking.
  • Chaining: This vulnerability can be chained with CVE-2026-96652, CVE-2026-96654, and CVE-2026-96656, which community intelligence suggests are used together for remote code execution and cryptominer deployment.
  • CVSS 3.1: 4.3 (MEDIUM) – CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N.

Detection

  • Monitor Plex Media Server web access logs for requests to the /video/:/transcode/universal path containing unusual or internal IP addresses/domains (e.g., 127.0.0.1, localhost, 192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12) in the URI.
  • Look for outbound network connections originating from the Plex Media Server process to unexpected external IP addresses or ports, especially those associated with cryptomining pools (e.g., 3333, 4444, 5555, 7777, 8080, 9000, 14444).
  • Detect suspicious process creation by the Plex Media Server.exe process, such as cmd.exe, powershell.exe, sh.exe, or known cryptominer executables (e.g., xmrig.exe).
  • Hunt for resource utilization spikes (CPU, network) on the Plex server that are not correlated with legitimate media transcoding or streaming activities, potentially indicating cryptominer execution.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Plex Media Server SSRF Attempt via Transcode Path

title: Plex Media Server SSRF Attempt via Transcode Path
id: 9029a12a-f9c7-43f1-801e-2a21b36a18d9
status: experimental
description: Detects attempts to exploit CVE-2026-96655 by requesting internal or suspicious external addresses via the '/video/:/transcode/universal' path parameter in Plex Media Server web logs.
logsource:
  category: webserver
detection:
  selection_path:
    c-uri|contains: '/video/:/transcode/universal'
  selection_target:
    c-uri|contains:
      - '127.0.0.1'
      - 'localhost'
      - '192.168.'
      - '10.'
      - '172.16.'
      - '172.17.'
      - '172.18.'
      - '172.19.'
      - '172.20.'
      - '172.21.'
      - '172.22.'
      - '172.23.'
      - '172.24.'
      - '172.25.'
      - '172.26.'
      - '172.27.'
      - '172.28.'
      - '172.29.'
      - '172.30.'
      - '172.31.'
  condition: all of selection*
level: high

Plex Media Server Spawning Suspicious Process

title: Plex Media Server Spawning Suspicious Process
id: 7e7f1b2c-3d4e-4f5a-8b9c-0d1e2f3a4b5c
status: experimental
description: Detects Plex Media Server.exe spawning known cryptominer executables or common shell interpreters, indicating potential post-exploitation activity after chaining vulnerabilities.
logsource:
  product: windows
  service: sysmon
detection:
  selection_parent:
    ParentImage|endswith: '\\Plex Media Server.exe'
  selection_child:
    Image|endswith:
      - '\\xmrig.exe'
      - '\\powershell.exe'
      - '\\cmd.exe'
      - '\\sh.exe'
  condition: all of selection*
level: critical

Mitigations

  1. Immediately update Plex Media Server to version 1.43.3.10861 or later to patch CVE-2026-96655 and related vulnerabilities.
  2. Implement network segmentation to restrict outbound connections from the Plex Media Server to only necessary services and destinations.
  3. Enforce strong authentication policies for all Plex users, including multi-factor authentication where possible.
  4. Regularly review Plex Media Server logs for suspicious activity and unexpected outbound connections.
  5. Consider placing Plex Media Server behind a reverse proxy or Web Application Firewall (WAF) to filter malicious requests.

References

  • https://forums.plex.tv/t/plex-media-server/30447/711
  • https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-266-01.json
  • https://www.cve.org/CVERecord?id=CVE-2026-96655
  • https://zmain.info/blog/plex2shell
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96655
  • https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html

Indicators of Compromise

Type Value Description
SHA256 2d3c618b21a7e2f8bcd735da188e44a7609ff3f204832dd0781cd09e4388c9db XMRig cryptominer payload (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 5712ef510481f15fe8b18fdd10b73026d57cb3d9d151878a692358b99a464441 Cryptominer payload (docker) (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 68938fb428f2bcfef4ede62f7b29cd0f15f37ed59e94462c099f2ca64e36baa7 Cryptominer payload ‘x’ (UPX packed) (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 b20f39fc00d242e706b6c30367ad811c676e0575050a4ec2f30104b696944b49 Cryptominer payload ‘x’ (UPX unpacked) (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 e546b10aee5edc754da4f9b0baace00392257121911f630145078eafad1e6bd9 Proxy payload ‘myawesomeproxy’ (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 176.65.139.228 Source IP of exploitation attempts (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 217.60.194.116 Source IP for malicious file download (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 45.194.92.222 Source IP of exploitation attempts (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 91.92.40.202 Source IP of exploitation attempts (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain 127.0.0.1.45-194-92-222.sslip.io Dynamic DNS domain used in exploitation URI (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain proxystream.st Domain related to proxy service traffic (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
URL https://zmain.info/blog/plex2shell Vulnerability research blog detailing the chained exploit (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
malware_family XMRig Cryptominer malware deployed post-exploitation
malware_family myawesomeproxy Proxy malware deployed post-exploitation

MITRE ATT&CK

  • T1190 — Exploit Public-Facing Application
  • T1090.003 — Multi-hop Proxy
  • T1496 — Resource Hijacking
  • T1059 — Command and Scripting Interpreter
  • T1583 — Acquire Infrastructure
  • T1133 — External Remote Services
  • T1204.002 — Malicious File
  • T1071 — Application Layer Protocol
  • T1090.002 — External Proxy
  • T1090 — Proxy
  • T1583.003 — Virtual Private Server
  • T1204 — User Execution
  • T1571 — Non-Standard Port
  • T1027 — Obfuscated Files or Information
  • T1486 — Data Encrypted for Impact
  • T1573 — Encrypted Channel
  • T1569 — System Services
  • T1027.002 — Software Packing
  • T1071.001 — Web Protocols
  • T1105 — Ingress Tool Transfer
  • T1090.001 — Internal Proxy
🤖 AI Attribution
Generated by gemini-2.5-flash ·
2,111 input / 2,003 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged cryptominer, exploitation, medium, plex, ssrf, vulnerability, windows, xmrigLeave a comment

CVE-2026-96654: Plex Media Server URI Scheme Neutralization Vulnerability Exploited for Cryptomining

Posted on November 3, 2026 by Kyle

Overview

Plex Media Server is affected by CVE-2026-96654, a medium-severity vulnerability allowing attackers to manipulate URI schemes to call internal plugin functions. This flaw can be chained with other vulnerabilities to achieve remote code execution. Threat actors are actively exploiting this to deploy cryptomining malware, making immediate patching critical for affected organizations and users.

Technical Analysis

  • CVE-2026-96654: Improper Neutralization of Encoded URI Schemes in a Web Page.
  • Description: Plex Media Server before 1.43.3.10861 does not correctly neutralize URL values included in searchOne, allowing an attacker to call other plugins’ functions and supply their own parameters.
  • CVSS 3.1: 6.5 (Medium) – CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N. This indicates network access, low attack complexity, no privileges required, no user interaction, unchanged scope, and low impact on confidentiality and integrity, with no impact on availability.
  • Weakness: CWE-84 (Improper Neutralization of Input During Web Page Generation).
  • Affected Versions: Plex Media Server versions prior to 1.43.0.10861.
  • Attack Vector: Network-based, unauthenticated. Exploitation involves crafting malicious URI requests to the Plex Media Server.
  • Chaining: This vulnerability can be chained with CVE-2026-96652, CVE-2026-96655, and CVE-2026-96656, potentially escalating impact to remote code execution.
  • Observed Impact: Active exploitation has been observed, leading to the deployment of cryptominer malware (e.g., XMRig) and proxy software (myawesomeproxy).

Detection

  • Monitor Plex Media Server process (Plex Media Server.exe) for unusual child process creation (e.g., cmd.exe, powershell.exe, wscript.exe, cscript.exe, or known cryptominer executables like xmrig.exe or myawesomeproxy.exe).
  • Inspect web server access logs for Plex Media Server for requests containing searchOne with unusual or encoded parameters, especially those attempting to invoke internal plugin functions.
  • Look for outbound network connections from the Plex Media Server process to known cryptomining pools or unusual IP addresses/ports.
  • Scan for the presence of known cryptominer executables (xmrig.exe) or proxy software (myawesomeproxy.exe) in unexpected directories, particularly within the Plex installation path or temporary directories.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Plex Media Server Spawning Suspicious Child Process

title: Plex Media Server Spawning Suspicious Child Process
id: 9a2b1c3d-4e5f-6a7b-8c9d-0e1f2a3b4c5d
status: experimental
description: Detects suspicious child processes (e.g., cmd, powershell, cryptominers) spawned by Plex Media Server, indicating potential exploitation of CVE-2026-96654 or similar vulnerabilities.
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    ParentImage|endswith: '\Plex Media Server.exe'
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\xmrig.exe'
      - '\myawesomeproxy.exe'
  condition: selection
level: high

XMRig Cryptominer Process Creation

title: XMRig Cryptominer Process Creation
id: 1f2e3d4c-5b6a-7f8e-9d0c-1b2a3f4e5d6c
status: experimental
description: Detects the creation of the XMRig cryptominer process, often deployed after successful exploitation of vulnerabilities like CVE-2026-96654.
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID: 1
    Image|endswith: '\xmrig.exe'
  condition: selection
level: high

Mitigations

  1. Patch Immediately: Upgrade Plex Media Server to version 1.43.3.10861 or later. Refer to the official Plex release notes.
  2. Network Segmentation: Isolate Plex Media Server instances from critical internal networks.
  3. Restrict Outbound Connectivity: Implement firewall rules to limit outbound connections from the Plex Media Server to only necessary services, blocking access to known cryptomining pools.
  4. Principle of Least Privilege: Ensure the Plex Media Server runs with the minimum necessary user permissions.
  5. Regular Audits: Periodically review Plex Media Server logs and system activity for signs of compromise.

References

  • https://nvd.nist.gov/vuln/detail/CVE-2026-96654
  • https://forums.plex.tv/t/plex-media-server/30447/711
  • https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-266-01.json
  • https://www.cve.org/CVERecord?id=CVE-2026-96654
  • https://zmain.info/blog/plex2shell
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96654
  • https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html

Indicators of Compromise

Type Value Description
SHA256 2d3c618b21a7e2f8bcd735da188e44a7609ff3f204832dd0781cd09e4388c9db SHA256 hash of XMRig cryptominer (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 5712ef510481f15fe8b18fdd10b73026d57cb3d9d151878a692358b99a464441 SHA256 hash of cryptominer docker file (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 68938fb428f2bcfef4ede62f7b29cd0f15f37ed59e94462c099f2ca64e36baa7 SHA256 hash of UPX packed cryptominer executable (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 b20f39fc00d242e706b6c30367ad811c676e0575050a4ec2f30104b696944b49 SHA256 hash of UPX unpacked cryptominer executable (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 e546b10aee5edc754da4f9b0baace00392257121911f630145078eafad1e6bd9 SHA256 hash of ‘myawesomeproxy’ malware (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 176.65.139.228 Source IP for exploitation attempt (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 217.60.194.116 Source IP for malicious file download (cryptominer) (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 45.194.92.222 Source IP for initial exploitation attempt (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 91.92.40.202 Source IP for exploitation attempt (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain 127.0.0.1.45-194-92-222.sslip.io Dynamic DNS domain used in exploitation URI (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain proxystream.st Domain associated with ‘myawesomeproxy’ malware traffic (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain sslip.io DNS service leveraged by attacker for owner token theft (via https://zmain.info/blog/plex2shell)
Email security@plex.tv Plex security contact email for vulnerability reporting (via https://zmain.info/blog/plex2shell)

MITRE ATT&CK

  • T1059.003 — Windows Command Shell
  • T1059.001 — PowerShell
  • T1496 — Resource Hijacking
  • T1583 — Acquire Infrastructure
  • T1133 — External Remote Services
  • T1204.002 — Malicious File
  • T1071 — Application Layer Protocol
  • T1190 — Exploit Public-Facing Application
  • T1090.002 — External Proxy
  • T1090 — Proxy
  • T1059 — Command and Scripting Interpreter
  • T1583.003 — Virtual Private Server
  • T1204 — User Execution
  • T1571 — Non-Standard Port
  • T1027 — Obfuscated Files or Information
  • T1486 — Data Encrypted for Impact
  • T1573 — Encrypted Channel
  • T1569 — System Services
  • T1027.002 — Software Packing
  • T1071.001 — Web Protocols
  • T1105 — Ingress Tool Transfer
  • T1090.001 — Internal Proxy
🤖 AI Attribution
Generated by gemini-2.5-flash ·
2,105 input / 1,684 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged cryptominer, exploitation, medium, plex, remote code execution, vulnerability, windowsLeave a comment

CVE-2026-96656: Plex Media Server Arbitrary File Write Vulnerability Exploited In-The-Wild

Posted on November 3, 2026 by Kyle

Overview

CVE-2026-96656 is a high-severity arbitrary file write vulnerability in Plex Media Server, affecting versions prior to 1.43.3.10861. An authenticated admin user can exploit this to write arbitrary files, which are then executed upon server load. This vulnerability is being actively exploited in conjunction with other Plex vulnerabilities to deploy cryptominers such as XMRig, posing a significant resource hijacking and potential further compromise risk.

Technical Analysis

  • Vulnerability ID: CVE-2026-96656
  • Weakness Enumeration: CWE-73 (External Control of File Name or Path).
  • Affected Products: Plex Media Server before 1.43.3.10861.
  • Attack Vector: An authenticated admin user can manipulate the TranscoderH264Options preference.
  • Exploitation Mechanism: The TranscoderH264Options preference is appended verbatim to x264’s option string during transcoding. This allows an attacker to inject arbitrary data into a file path or name, leading to the creation of arbitrary files.
  • Code Execution: At startup, Plex Media Server loads and executes all .so (shared object) files without signature, execute bit, or symbol checks. By writing a malicious .so file to a directory Plex loads from, an attacker can achieve arbitrary code execution.
  • Chaining: This vulnerability can be chained with CVE-2026-96652, CVE-2026-96654, and CVE-2026-96655 to achieve broader impact, such as privilege escalation or bypassing other controls.
  • CVSS 3.1 Score: 7.2 (HIGH) – CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.

Detection

  • Monitor Plex Media Server log files for unusual TranscoderH264Options modifications or errors related to transcoding that indicate path manipulation attempts.
  • Look for the creation of new or modified .so files in Plex Media Server installation directories, data directories (e.g., C:\ProgramData\Plex Media Server\ on Windows, /var/lib/plexmediaserver/ on Linux), or temporary directories (e.g., C:\Windows\Temp\, /tmp/).
  • Monitor for unexpected child processes spawned by the Plex Media Server executable (e.g., Plex Media Server.exe, Plex Transcoder.exe) or its associated processes. Look for cmd.exe, powershell.exe, sh, bash, python, or known cryptominer executables (e.g., xmrig).
  • Implement network monitoring to detect outbound connections from the Plex Media Server to known cryptomining pools, suspicious IP addresses, or C2 infrastructure.
  • Utilize File Integrity Monitoring (FIM) on critical Plex Media Server directories to detect unauthorized file changes or creations.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Plex Media Server Spawning Suspicious Process

title: Plex Media Server Spawning Suspicious Process
id: 9381e4b3-c15b-4b1a-8e2a-1f2d3c4e5f6a
status: experimental
description: Detects suspicious process creation by Plex Media Server, indicative of post-exploitation activity after arbitrary file write.
logsource:
  category: process_creation
  product: windows
  service: sysmon
detection:
  selection:
    ParentImage|endswith:
      - '\Plex Media Server.exe'
      - '\Plex Transcoder.exe'
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
      - '\sh.exe'
      - '\bash.exe'
      - '\python.exe'
  condition: selection
level: high

Plex Media Server Suspicious Shared Object File Creation

title: Plex Media Server Suspicious Shared Object File Creation
id: 7a2b0c1d-e3f4-5g6h-7i8j-9k0l1m2n3o4p
status: experimental
description: Detects the creation of new .so files in potentially exploitable locations by Plex Media Server, which could indicate arbitrary file write exploitation.
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID: 11
    TargetFilename|endswith: '.so'
    Image|endswith:
      - '\Plex Media Server.exe'
      - '\Plex Transcoder.exe'
    TargetFilename|contains:
      - 'C:\ProgramData\Plex Media Server\'
      - 'C:\Users\Public\'
      - 'C:\Windows\Temp\'
  condition: selection
level: high

XMRig Cryptominer Process Activity

title: XMRig Cryptominer Process Activity
id: 5d6e7f8a-9b0c-1d2e-3f4a-5b6c7d8e9f0a
status: experimental
description: Detects common process creation patterns associated with XMRig cryptominer, often deployed after successful exploitation of vulnerabilities like CVE-2026-96656.
logsource:
  category: process_creation
  product: windows
  service: sysmon
detection:
  selection_img:
    Image|contains:
      - 'xmrig'
      - 'miner'
  selection_cmd:
    CommandLine|contains:
      - '--donate-level'
      - '--url'
      - '--user'
      - '--pass'
      - '-o stratum+tcp://'
      - '-a rx/0'
      - '-k --nicehash'
  condition: 1 of selection_*
level: high

Mitigations

  1. Patch Immediately: Upgrade Plex Media Server to version 1.43.3.10861 or later. Refer to the official Plex release notes for the latest security updates.
  2. Restrict Admin Access: Limit administrative access to Plex Media Server to only trusted and authorized personnel.
  3. Network Segmentation: Isolate Plex Media Server instances on a dedicated network segment to limit lateral movement and impact in case of compromise.
  4. Monitor Outbound Connections: Implement egress filtering on network firewalls to prevent unauthorized outbound connections from the Plex Media Server, particularly to known cryptomining ports or suspicious IP ranges.
  5. Regular Backups: Maintain regular backups of Plex Media Server configurations and data to facilitate recovery from potential compromise.

References

  • https://forums.plex.tv/t/plex-media-server/30447/711
  • https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2026/va-26-266-01.json
  • https://www.cve.org/CVERecord?id=CVE-2026-96656
  • https://zmain.info/blog/plex2shell
  • https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-96656

Indicators of Compromise

Type Value Description
SHA256 2d3c618b21a7e2f8bcd735da188e44a7609ff3f204832dd0781cd09e4388c9db XMRig cryptominer payload (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 50e93e8d8c26bd95d0ba91ba9b7c5c15532050866f52c3aef04f9773b7418767 Unknown malware · confidence 100% · first seen 2026-10-20
SHA256 5712ef510481f15fe8b18fdd10b73026d57cb3d9d151878a692358b99a464441 Cryptominer payload (docker) (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 68938fb428f2bcfef4ede62f7b29cd0f15f37ed59e94462c099f2ca64e36baa7 Cryptominer payload ‘x’ (UPX packed) (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 6915f57c96c880803863d30eefaa5e3fe3923e11c948cb6747c68478d2e6cf40 Unknown malware · confidence 100% · first seen 2026-10-20
SHA256 a580786ff7336e916e92bb79db96d5d6f48119cd3b0b4e45211b47e298be5380 Unknown malware · confidence 100% · first seen 2026-10-20
SHA256 a9a309154493193c70bf6f805fe70e1bc4e9564e2f0e20cd1600c72587c7e65f XMRIG · confidence 95% · first seen 2026-10-18
SHA256 b20f39fc00d242e706b6c30367ad811c676e0575050a4ec2f30104b696944b49 Cryptominer payload ‘x’ (UPX unpacked) (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 cababb6448ee3f2a274f516dc6b0fdc9f47d084a84d7bd164546c9c4b1755d44 Unknown malware · confidence 100% · first seen 2026-10-20
SHA256 e546b10aee5edc754da4f9b0baace00392257121911f630145078eafad1e6bd9 Proxy payload ‘myawesomeproxy’ (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
SHA256 f083b3647e50fb548c2b97887e51927bc62b429aaa7c4828e316bd5ef6503453 Unknown malware · confidence 100% · first seen 2026-10-20
SHA256 f599491cce46b1d94c762eff392458ae015e7163620b07ad7ceaa16708b1bf4f Unknown malware · confidence 100% · first seen 2026-10-20
IP Address 176.65.139.228 Source IP of exploitation attempts (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 202.78.167.55 Unknown malware · confidence 100% · first seen 2026-10-20
IP Address 217.60.194.116 Source IP for malicious file download (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 45.194.92.222 Source IP of exploitation attempts (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
IP Address 77.90.185.205 XMRIG · confidence 95% · first seen 2026-10-18
IP Address 91.92.40.202 Source IP of exploitation attempts (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain 127.0.0.1.45-194-92-222.sslip.io Dynamic DNS domain used in exploitation URI (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain autoccb.tech Unknown malware · confidence 100% · first seen 2026-10-20
Domain ota.proxystream.st XMRIG · confidence 95% · first seen 2026-10-18
Domain proxystream.st Domain related to proxy service traffic (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)
Domain www.autoccb.tech Unknown malware · confidence 100% · first seen 2026-10-20
URL http://217.60.194.116/docker XMRIG · confidence 95% · first seen 2026-10-18
URL https://www.autoccb.tech/api/v1/poll Unknown malware · confidence 100% · first seen 2026-10-20
URL https://www.autoccb.tech/api/v1/result Unknown malware · confidence 100% · first seen 2026-10-20
URL https://zmain.info/blog/plex2shell Vulnerability research blog detailing the chained exploit (via https://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html)

MITRE ATT&CK

  • T1059.001 — PowerShell
  • T1059.003 — Windows Command Shell
  • T1574.002 — DLL Side-Loading
  • T1496 — Resource Hijacking
  • T1036.005 — Match Legitimate Resource Name or Location
  • T1583 — Acquire Infrastructure
  • T1133 — External Remote Services
  • T1204.002 — Malicious File
  • T1071 — Application Layer Protocol
  • T1190 — Exploit Public-Facing Application
  • T1090.002 — External Proxy
  • T1090 — Proxy
  • T1059 — Command and Scripting Interpreter
  • T1583.003 — Virtual Private Server
  • T1204 — User Execution
  • T1571 — Non-Standard Port
  • T1027 — Obfuscated Files or Information
  • T1486 — Data Encrypted for Impact
  • T1573 — Encrypted Channel
  • T1569 — System Services
  • T1027.002 — Software Packing
  • T1071.001 — Web Protocols
  • T1105 — Ingress Tool Transfer
  • T1090.001 — Internal Proxy
🤖 AI Attribution
Generated by gemini-2.5-flash ·
2,236 input / 2,147 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged arbitrary file write, cryptominer, cwe-73, high, high-severity, media server, plex, remote code execution, vulnerability, xmrigLeave a comment

CVE-2026-106931: EG Secure Solutions SiteGuard Server Edition OS Command Injection

Posted on November 3, 2026 by Kyle

Overview

CVE-2026-106931 identifies an OS command injection vulnerability within EG Secure Solutions SiteGuard Server Edition. This flaw enables a local attacker with low privileges to execute arbitrary operating system commands with elevated root or SYSTEM privileges. The vulnerability is critical due to its potential for full system compromise and is listed in CISA’s Known Exploited Vulnerabilities Catalog.

Technical Analysis

EG Secure Solutions SiteGuard Server Edition is susceptible to an OS command injection vulnerability (CWE-78). A local attacker with low privileges can leverage this flaw to inject and execute arbitrary OS commands. The successful execution of these commands occurs with the privileges of the affected product, which are root or SYSTEM. The CVSS 3.0 score is 7.8 (HIGH), with a vector of CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, indicating a local attack vector requiring low privileges, with high impact on confidentiality, integrity, and availability.

  • Vulnerability Type: OS Command Injection (CWE-78)
  • Affected Product: EG Secure Solutions SiteGuard Server Edition
  • Attack Vector: Local (AV:L)
  • Privileges Required: Low (PR:L)
  • Impact: Arbitrary OS command execution with root or SYSTEM privileges, leading to high impact on confidentiality, integrity, and availability.
  • Affected Versions: Specific affected versions are not detailed in the provided source material, but the vulnerability affects SiteGuard Server Edition.

Detection

Detection efforts should focus on identifying unusual process execution patterns originating from the SiteGuard Server Edition process, particularly the spawning of shell interpreters or system utilities.

  • Monitor process creation events for SiteGuard Server Edition (or its associated executable) spawning suspicious child processes like cmd.exe, powershell.exe, sh, bash, python, perl, or other scripting interpreters.
  • Look for command-line arguments passed to these child processes that indicate system modification, privilege escalation attempts, or data exfiltration.
  • Analyze web server logs (if SiteGuard has a web interface) for unusual or malformed requests that could trigger command injection, especially in parameters known to be processed by the application.
  • Review system logs for unexpected changes to critical system files, user accounts, or service configurations that might follow successful exploitation.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

SiteGuard Server Edition Spawning Windows Shell

title: SiteGuard Server Edition Spawning Windows Shell
id: 934d6731-a1b2-4c3e-8d5f-e2f0a1b2c3d4
status: experimental
description: Detects SiteGuard Server Edition spawning cmd.exe or powershell.exe, indicative of OS command injection exploitation.
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID: 1
    ParentImage|contains: 'SiteGuard'
    Image|endswith:
      - '\\cmd.exe'
      - '\\powershell.exe'
  condition: selection
level: high

SiteGuard Server Edition Spawning Linux Shell

title: SiteGuard Server Edition Spawning Linux Shell
id: 5e6f7a8b-c9d0-1e2f-3a4b-5c6d7e8f9a0b
status: experimental
description: Detects SiteGuard Server Edition spawning common Linux shells, indicative of OS command injection exploitation.
logsource:
  product: linux
  service: auditd
detection:
  selection:
    type: 'EXECVE'
    a0|contains: 'SiteGuard'
    a1|endswith:
      - '/bin/sh'
      - '/bin/bash'
      - '/bin/dash'
      - '/bin/zsh'
  condition: selection
level: high

Mitigations

  1. Patch Immediately: Apply all available security updates and patches from EG Secure Solutions for SiteGuard Server Edition. Refer to the vendor’s security advisories for specific patch information.
  2. Least Privilege: Ensure that the SiteGuard Server Edition service runs with the absolute minimum necessary privileges. If possible, restrict its ability to spawn new processes or execute arbitrary commands.
  3. Network Segmentation: Isolate systems running SiteGuard Server Edition on a dedicated network segment to limit potential lateral movement if compromised.
  4. Endpoint Detection and Response (EDR): Deploy and configure EDR solutions to monitor for and block suspicious process creation and command execution originating from the SiteGuard Server Edition process.
  5. Input Validation: While a vendor fix is paramount, ensure that any custom integrations or scripts interacting with SiteGuard Server Edition implement robust input validation to prevent similar injection flaws.

References

  • https://nvd.nist.gov/vuln/detail/CVE-2026-106931
  • https://jvn.jp/en/jp/JVN88474777/
  • https://www.eg-secure.co.jp/siteguard/news/alert-202610-1
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-106931
  • https://ltna.com.au/cyber

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1059 — Command and Scripting Interpreter
  • T1059.003 — Windows Command Shell
  • T1059.004 — Unix Shell
🤖 AI Attribution
Generated by gemini-2.5-flash ·
1,901 input / 1,513 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged cisa_kev, command_injection, high, privilege_escalation, siteguard, vulnerabilityLeave a comment

CVE-2026-102764: Critical BeyondTrust Remote Support Authentication Bypass

Posted on October 17, 2026 by Kyle

Overview

CVE-2026-102764 is a critical authentication bypass vulnerability affecting BeyondTrust Remote Support appliances. This flaw allows a remote, unauthenticated attacker to perform arbitrary file operations on the vulnerable appliance. It has been added to CISA’s Known Exploited Vulnerabilities Catalog, indicating active exploitation by sophisticated threat actors, including those linked to ARMORY CASTLE.

Technical Analysis

The vulnerability (CWE-290, Improper Neutralization of Special Elements used in an Authentication Bypass) resides within internal components of BeyondTrust Remote Support. These components fail to adequately validate the origin of received messages, enabling an attacker to spoof legitimate communications. Under specific conditions, this spoofing allows an unauthenticated remote attacker to execute file operations on the appliance, potentially leading to arbitrary code execution, privilege escalation to root, and the deployment of backdoors or webshells.

  • CVE ID: CVE-2026-102764
  • CVSS 3.1 Score: 9.8 (CRITICAL)
  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Affected Products: BeyondTrust Remote Support versions up to and including 26.2.3.
  • Attack Vector: Network (AV:N), requiring low attack complexity (AC:L) with no privileges (PR:N) or user interaction (UI:N).
  • Impact: High confidentiality, integrity, and availability impact (C:H/I:H/A:H).
  • Observed Exploitation: Actively exploited in the wild by threat actors, including ARMORY CASTLE, to achieve root access and deploy malware such as SAWFLY and BARECLAW.

Detection

Detection efforts should focus on anomalous activity originating from or targeting BeyondTrust Remote Support appliances, particularly suspicious file operations or process execution.

  • Network Logs: Monitor for unusual network traffic patterns to/from BeyondTrust appliances, especially unexpected connections or data transfers post-exploitation.
  • Appliance Logs: Review system logs on BeyondTrust appliances for:
    • Unusual process creation by the BeyondTrust service (e.g., sh, bash, python, perl, cmd.exe, powershell.exe spawned by the main BeyondTrust process).
    • Suspicious file modifications or creations in web root directories (e.g., /var/www/html, /opt/beyondtrust/web/) indicative of webshell deployment.
    • Changes to system configuration files or new user accounts being created.
    • Attempts to modify or delete log files.
  • Endpoint Detection and Response (EDR): On systems interacting with or hosting the BeyondTrust appliance, look for:
    • Execution of known malware families like SAWFLY or BARECLAW.
    • Unusual outbound connections from the appliance to external C2 infrastructure.
    • Privilege escalation attempts or suspicious persistence mechanisms being established.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

BeyondTrust Remote Support – Suspicious Process Creation

title: BeyondTrust Remote Support - Suspicious Process Creation
id: 9a3b2c1d-4e5f-6a7b-8c9d-0e1f2a3b4c5d
status: experimental
description: Detects suspicious process creation by the BeyondTrust Remote Support service, indicative of post-exploitation activity after CVE-2026-102764 exploitation. This could include shell execution or other arbitrary commands.
logsource:
  product: linux
  service: auditd
detection:
  selection:
    type: 'EXECVE'
    a0|contains: ['sh', 'bash', 'python', 'perl', 'php', 'nc', 'wget', 'curl']
    # Adjust 'comm' or 'exe' based on the actual BeyondTrust service process name on the appliance
    # Example: comm: 'beyondtrust_service' or exe|endswith: '/opt/beyondtrust/bin/service'
    # For broader detection, you might omit the parent process if logs are limited.
  condition: selection
level: high

BeyondTrust Remote Support – Suspicious File Write in Web Root

title: BeyondTrust Remote Support - Suspicious File Write in Web Root
id: 1b2c3d4e-5f6a-7b8c-9d0e-1f2a3b4c5d6e
status: experimental
description: Detects suspicious file writes in common web root directories on a BeyondTrust appliance, potentially indicating webshell deployment after CVE-2026-102764 exploitation.
logsource:
  product: linux
  service: auditd
detection:
  selection:
    type: 'SYSCALL'
    syscall: 'openat'
    a1: 'O_WRONLY|O_CREAT'
    # Common web root paths for appliances. Adjust based on actual BeyondTrust appliance structure.
    name|startswith: ['/var/www/', '/opt/beyondtrust/web/', '/usr/share/nginx/html/', '/usr/local/apache2/htdocs/']
    # Look for common webshell extensions or suspicious file names
    name|endswith: ['.php', '.jsp', '.asp', '.aspx', '.pl', '.py', '.sh', '.cgi', '.txt', '.log']
    # Exclude known legitimate writes if causing FPs
  condition: selection
level: high

Mitigations

Prioritize immediate patching and implement compensating controls to limit potential impact.

  1. Patch Immediately: Upgrade BeyondTrust Remote Support to a patched version beyond 26.2.3 as soon as possible. Refer to the vendor advisory for specific patch versions.
  2. Network Segmentation: Isolate BeyondTrust Remote Support appliances on a dedicated network segment with strict ingress/egress filtering to limit exposure and contain potential breaches.
  3. Principle of Least Privilege: Ensure that the BeyondTrust appliance and associated services operate with the minimum necessary privileges.
  4. Monitor Appliance Logs: Implement robust logging and continuous monitoring of BeyondTrust appliance system and application logs for suspicious activity.
  5. Web Application Firewall (WAF): Deploy a WAF in front of the BeyondTrust appliance to detect and block suspicious web requests, although this vulnerability may bypass some WAF rules due to its internal component nature.

References

  • https://www.beyondtrust.com/blog/entry/bt26-05
  • https://beyondtrustcorp.service-now.com/csm?id=csm_kb_article&sysparm_article=KB0024066
  • https://nvd.nist.gov/vuln/detail/CVE-2026-102764
  • https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102764
  • https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-beyondtrust
  • https://ltna.com.au/cyber
  • https://socprime.com/blog/cve-2026-10264-beyondtrust-zero-day-exploited/
  • https://ppl-ai-file-upload.s3.amazonaws.com/web/direct-files/attachments/11146061/e3a50834-c553-4e4c-b521-58d936951de5/Chinese-Hackers-Exploit-BeyondTrust-Zero-Day-to-Gain-Root-Access-and-Deploy-Backdoors.pdf

Indicators of Compromise

Type Value Description
SHA256 1f19b9a27d79c11bda00a1e8faf74a7fdd683d38ccef1b60df2fd0307e3aa462 SHA-256 hash of the BARECLAW binary (via https://socprime.com/blog/cve-2026-102764-beyondtrust-zero-day-exploited/)
SHA256 dc14e215269a93fdbc4c1a80b984c23faf7af0911c6dbb85309796a6f2ae95fb SHA-256 hash of the SAWFLY webshell (via https://socprime.com/blog/cve-2026-102764-beyondtrust-zero-day-exploited/)
info ARMORY CASTLE Threat actor group observed exploiting CVE-2026-102764.
info BARECLAW Associated malware family observed in post-exploitation activities.
info SAWFLY Associated malware family observed in post-exploitation activities.
info backdoor Generic term for persistent access mechanisms deployed post-exploitation.
info webshell Common post-exploitation artifact deployed after successful exploitation.

MITRE ATT&CK

  • T1190 — Exploit Public-Facing Application
  • T1068 — Exploitation for Privilege Escalation
  • T1505.003 — Web Shell
  • T1083 — File and Directory Discovery
  • T1003 — OS Credential Dumping
  • T1133 — External Remote Services
  • T1548.003 — Sudo and Sudo Caching
  • T1021.004 — SSH
  • T1005 — Data from Local System
  • T1572 — Protocol Tunneling
  • T1136.001 — Local Account
  • T1070.001 — Clear Windows Event Logs
  • T1548.001 — Setuid and Setgid
  • T1552.001 — Credentials In Files
  • T1041 — Exfiltration Over C2 Channel
  • T1090.003 — Multi-hop Proxy
  • T1562.001 — Disable or Modify Tools
  • T1070.004 — File Deletion
  • T1543.002 — Systemd Service
  • T1090.001 — Internal Proxy
  • T1078.003 — Local Accounts
🤖 AI Attribution
Generated by gemini-2.5-flash ·
2,394 input / 2,344 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged armory castle, authentication bypass, bareclaw, beyondtrust, critical, cve-2026-102764, privilege escalation, remote support, sawfly, vulnerability, webshell, zero-day exploitationLeave a comment

CVE-2026-21589: Atlassian Data Center Arbitrary File Read Vulnerability

Posted on October 17, 2026 by Kyle

Overview

CVE-2026-21589 is an arbitrary file access vulnerability impacting multiple Atlassian Data Center products, including Bitbucket, Confluence, Jira Software, Jira Service Management, Bamboo, Crowd, Crucible, and Fisheye. This flaw allows an unauthenticated attacker to read specific files from the web application root directory. Given reports of active exploitation, immediate patching is critical for affected organizations.

Technical Analysis

  • Vulnerability: CWE-552 (Files or Directories Accessible to External Parties). An unauthenticated attacker can access specific files within the web application root directory.
  • Affected Products & Versions:
    • Bitbucket Data Center: introduced in >= 4.6.0, vulnerable up to < 9.4.26, < 10.2.8, < 10.5.1
    • Confluence Data Center: introduced in >= 5.10.0, vulnerable up to < 9.2.26, < 10.2.19
    • Crowd Data Center: introduced in >= 2.11.0, vulnerable up to < 6.3.7, < 7.0.3, < 7.1.7, < 7.2.4
    • Jira Software Data Center: introduced in >= 7.1.0, vulnerable up to < 9.12.40, < 10.3.26, < 11.3.12
    • Jira Service Management Data Center: introduced in >= 3.1.0, vulnerable up to < 5.12.40, < 10.3.26, < 11.3.12
    • Bamboo Data Center: introduced in >= 7.0.1, vulnerable up to < 10.2.24, < 12.1.12
    • Crucible: vulnerable up to < 4.9.15
    • Fisheye: vulnerable up to < 4.9.15
  • Attack Vector: Network (AV:N). Exploitation is remote and unauthenticated (PR:N).
  • Prerequisites: The attacker must have prior knowledge of the exact filename and path of the target file. The vulnerability does not allow directory enumeration.
  • Impact: Confidentiality (C:H). Successful exploitation can lead to the disclosure of sensitive files, potentially including configuration files, credentials, or other proprietary data. Integrity and Availability are not directly impacted (I:N, A:N).
  • CVSS v3.1 Score: 7.5 (High) – CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Detection

  • Web Server Access Logs: Monitor web server access logs (e.g., Apache, Nginx, IIS) for GET requests to known sensitive files or file types within the Atlassian application’s web root that are not typically served publicly.
    • Look for requests to configuration files such as dbconfig.xml, atlassian-user.xml, server.xml, web.xml, setenv.sh, setenv.bat, application.properties, application.yml.
    • Look for requests to backup files (.bak, .zip, .sql) or log files (.log, catalina.out, .env) directly within the web application root or common subdirectories.
    • Analyze sc-status codes for successful (200) or unusual (e.g., 403, 404 for files that should exist but not be accessible) access attempts to these paths.
  • Network Intrusion Detection Systems (NIDS): Deploy NIDS rules to identify HTTP GET requests targeting specific sensitive file paths associated with Atlassian products.

Sigma Detection Rules

⚠️ AI-generated detection rules. These are experimental starting points. Review field names, EventIDs, and logic against your environment’s schema before deploying. Tune to reduce false positives.

Atlassian Data Center – Suspicious Configuration File Access (CVE-2026-21589)

title: Atlassian Data Center - Suspicious Configuration File Access (CVE-2026-21589)
id: 75751911-c918-4a6c-9418-866415779496
status: experimental
description: Detects unauthenticated attempts to access sensitive Atlassian or Java web application configuration files via CVE-2026-21589.
logsource:
  category: webserver
detection:
  selection:
    cs-method: 'GET'
    cs-uri-stem|endswith:
      - 'dbconfig.xml'
      - 'atlassian-user.xml'
      - 'server.xml'
      - 'web.xml'
      - 'setenv.sh'
      - 'setenv.bat'
      - 'application.properties'
      - 'application.yml'
      - 'config.xml'
      - 'settings.xml'
  condition: selection
level: high

Atlassian Data Center – Suspicious Log or Backup File Access (CVE-2026-21589)

title: Atlassian Data Center - Suspicious Log or Backup File Access (CVE-2026-21589)
id: 02d44e54-4f0e-4a11-8c4b-149d6837895e
status: experimental
description: Detects unauthenticated attempts to access sensitive log, backup, or environment files within the web application root via CVE-2026-21589.
logsource:
  category: webserver
detection:
  selection:
    cs-method: 'GET'
    cs-uri-stem|endswith:
      - '.log'
      - '.bak'
      - '.zip'
      - '.sql'
      - '.env'
      - 'catalina.out'
  condition: selection
level: medium

Mitigations

  1. Patch Immediately: Apply the latest security patches for all affected Atlassian Data Center products. Refer to the Atlassian advisories linked in the references for specific fix versions.
    • Bitbucket Data Center: Upgrade to 9.4.26, 10.2.8, 10.5.1 or later.
    • Confluence Data Center: Upgrade to 9.2.26, 10.2.19 or later.
    • Crowd Data Center: Upgrade to 6.3.7, 7.0.3, 7.1.7, 7.2.4 or later.
    • Jira Software Data Center: Upgrade to 9.12.40, 10.3.26, 11.3.12 or later.
    • Jira Service Management Data Center: Upgrade to 5.12.40, 10.3.26, 11.3.12 or later.
    • Bamboo Data Center: Upgrade to 10.2.24, 12.1.12 or later.
    • Crucible: Upgrade to 4.9.15 or later.
    • Fisheye: Upgrade to 4.9.15 or later.
  2. Restrict File Access: Ensure proper file system permissions are in place, limiting read access to sensitive configuration and data files to only the necessary service accounts.
  3. Network Segmentation: Isolate Atlassian Data Center instances from direct internet exposure where possible, placing them behind reverse proxies or web application firewalls (WAFs) that can filter suspicious requests.
  4. Monitor Logs: Continuously monitor web server and application logs for suspicious access patterns to sensitive files.

References

  • https://nvd.nist.gov/vuln/detail/CVE-2026-21589
  • https://jira.atlassian.com/browse/BAM-26567
  • https://jira.atlassian.com/browse/BSERV-20604
  • https://jira.atlassian.com/browse/CONFSERVER-104488
  • https://jira.atlassian.com/browse/CRUC-8741
  • https://jira.atlassian.com/browse/CWD-6610
  • https://jira.atlassian.com/browse/FE-7583
  • https://jira.atlassian.com/browse/JRASERVER-79546
  • https://jira.atlassian.com/browse/JSDSERVER-16809
  • https://www.securityweek.com/attackers-target-critical-atlassian-vulnerability-within-hours-of-poc-publication/
  • https://previdian.com/CVE-2026-21589
  • https://labs.watchtowr.com/you-wont-hear-about-these-even-in-myths-atlassian-jira-confluence-and-more-pre-auth-arbitrary-file-read-cve-2026-21589/
  • https://thehackernews.com/2026/10/atlassian-data-center-flaw-draws.html
  • https://github.com/watchtowrlabs/watchTowr-vs-Atlassian-CVE-2026-21589
  • https://www.bleepingcomputer.com/news/security/hackers-exploit-critical-atlassian-flaw-after-public-poc-release/

Indicators of Compromise

No public IOCs available at time of writing.

MITRE ATT&CK

  • T1190 — Exploit Public-Facing Application
  • T1083 — File and Directory Discovery
  • T1552.001 — Credentials In Files
🤖 AI Attribution
Generated by gemini-2.5-flash ·
3,117 input / 2,588 output tokens ·
Reviewed and approved by a human analyst before publication
Posted in vulnerabilityTagged active-exploitation, arbitrary-file-read, atlassian, cve, data-center, high, pre-auth, vulnerabilityLeave a comment

Posts navigation

Older posts
Newer posts
Proudly powered by WordPress | Theme: micro, developed by DevriX.