Skip to navigation

Threat reportVulnerabilityTL-2026-0269

CVE-2026-21902: Juniper PTX Series Junos OS Evolved Unauthenticated Remote Code Execution as Root via On-Box Anomaly Detection Framework (CVSS 9.8)

criticalPATCHED

Critical unauthenticated remote code execution vulnerability in Juniper Networks PTX Series routers running Junos OS Evolved. The On-Box Anomaly Detection Framework exposes a Python REST API on port 8160/TCP bound to all interfaces without authentication, allowing any network-based attacker to execute arbitrary commands as root via crafted API requests.

Key facts

IdentifiersTL-2026-0269, CVE-2026-21902
Also known asJSA107128
SeverityCRITICAL
CVSS9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
Exploitation statusPublic proof-of-concept exploit for a linked CVE
EPSSCVE-2026-21902: 18.0% (97.1th percentile)
Affected productsJuniper Networks Junos OS Evolved; Juniper Networks PTX Series Routers
Weaknesses (CWE)CWE-276, CWE-732
ToolswatchTowr-vs-JunosEvolved-CVE-2026-21902
MITRE ATT&CK techniquesT1040 Network Sniffing, T1046 Network Service Discovery, T1053 Scheduled Task/Job, T1059 Command and Scripting Interpreter, T1068 Exploitation for Privilege Escalation, T1070 Indicator Removal, T1071 Application Layer Protocol, T1082 System Information Discovery, T1190 Exploit Public-Facing Application, T1210 Exploitation of Remote Services, T1211 Exploitation for Stealth, T1489 Service Stop and 8 more in the attack flow
MotivationUNKNOWN
Target sectorstelecommunications, government, financial, healthcare, energy, technology, critical-infrastructure, internet-service-providers, cloud-providers, defense
Target regionsGlobal
Detection rules9 (1 shown free)
Sources14 cited sources

Detection coverage

As of 2026-07-19, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0269 across Splunk SPL, Microsoft KQL and Sigma, covering 24 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: CVE-2026-21902 Post-Exploitation — Root Command Execution via schedule_enforcer

Detects indicators of successful CVE-2026-21902 post-exploitation on Juniper PTX devices. After the initial API exploitation, the schedule_enforcer.py process (running as root) executes attacker-controlled commands via subprocess.run(shell=True). This detection monitors syslog from Juniper devices for shell process spawning by the schedule_enforcer process, RE-SHELL command type execution, and unexpected child process creation patterns indicating arbitrary command execution with root privileges.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • Severity: critical
  • Confidence: high

Splunk SPL

index=syslog OR index=network_devices sourcetype="syslog" OR sourcetype="juniper:junos:structured" host="ptx*" OR host="PTX*"
| search (process="*schedule_enforcer*" OR process_name="schedule_enforcer.py") AND (message="*RE-SHELL*" OR message="*/bin/sh*" OR message="*/bin/bash*" OR message="*subprocess*" OR message="*shell=True*")
| eval is_suspicious=case(
    match(message, "RE-SHELL"), "MALICIOUS_COMMAND_TYPE",
    match(message, "/bin/(sh|bash)"), "SHELL_SPAWN",
    match(message, "subprocess"), "SUBPROCESS_EXECUTION",
    1=1, "UNKNOWN")
| stats count min(_time) as first_seen max(_time) as last_seen values(message) as commands values(is_suspicious) as indicators by host, source_ip
| where count > 0
| sort -count

Microsoft KQL

Syslog
| where TimeGenerated > ago(24h)
| where Computer has_any ("ptx", "PTX") or HostName has_any ("ptx", "PTX")
| where ProcessName has "schedule_enforcer" or SyslogMessage has "schedule_enforcer"
| where SyslogMessage has_any ("RE-SHELL", "/bin/sh", "/bin/bash", "subprocess", "shell=True")
| extend SuspiciousIndicator = case(
    SyslogMessage has "RE-SHELL", "MALICIOUS_COMMAND_TYPE",
    SyslogMessage has_any ("/bin/sh", "/bin/bash"), "SHELL_SPAWN",
    SyslogMessage has "subprocess", "SUBPROCESS_EXECUTION",
    true, "UNKNOWN")
| summarize EventCount=count(), Commands=make_set(SyslogMessage), Indicators=make_set(SuspiciousIndicator), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by Computer, HostIP
| sort by EventCount desc

Sigma

title: CVE-2026-21902 Post-Exploitation Root Command Execution via schedule_enforcer.py
id: 8b4e2c3f-c5d6-4f7a-9b0c-1d2e3f4a5b6c
status: experimental
description: Detects schedule_enforcer.py process executing shell commands as root on Juniper PTX devices indicating successful CVE-2026-21902 exploitation and arbitrary command execution
references:
  - https://supportportal.juniper.net/JSA107128
  - https://labs.watchtowr.com/sometimes-you-can-just-feel-the-security-in-the-design-junos-os-evolved-cve-2026-21902-rce/
author: Threadlinqs Team
date: 2026/03/22
tags:
  - attack.execution
  - attack.t1059.004
  - attack.persistence
  - attack.t1053
  - attack.privilege_escalation
  - attack.t1068
  - cve.2026.21902
logsource:
  product: linux
  service: syslog
detection:
  selection_process:
    process_name|contains: 'schedule_enforcer'
  selection_indicators:
    SyslogMessage|contains:
      - 'RE-SHELL'
      - '/bin/sh'
      - '/bin/bash'
      - 'subprocess.run'
  condition: selection_process and selection_indicators
falsepositives:
  - Legitimate Anomaly Detection Framework scheduled maintenance tasks executed by authorized administrators
level: critical

Tuning notes: Update host filter to match your PTX router naming convention. Add exclusions for known legitimate schedule_enforcer operations during maintenance windows. Correlate with SPL-001 alerts for the same dest_ip to confirm full exploitation chain.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • CVE-2026-21902 Exploitation — Anomaly Detection API Requests on Port 8160 (KQL) · unlock with TL Creds
  • CVE-2026-21902 Post-Exploitation — DAG Workflow Abuse and Unauthorized Configuration Commits (KQL) · unlock with TL Creds
  • CVE-2026-21902 Post-Compromise — Lateral Movement and Credential Access from PTX Router (KQL) · unlock with TL Creds
  • CVE-2026-21902 Exploitation — HTTP POST Chain to Anomaly Detection REST API (Sigma Primary) · unlock with TL Creds
  • CVE-2026-21902 Post-Exploitation — Anomaly Detection Framework Process Abuse (Sigma Primary) · unlock with TL Creds
  • CVE-2026-21902 Post-Compromise — Defense Evasion and Impact on Juniper PTX Infrastructure (Sigma Primary) · unlock with TL Creds
  • CVE-2026-21902 Juniper PTX Anomaly Detection API Exploitation — Network Traffic · unlock with TL Creds
  • CVE-2026-21902 Post-Compromise — Anomalous Outbound Traffic from PTX Management Interface · unlock with TL Creds

Indicators of compromise

As of 2026-07-19, Threadlinqs Intelligence tracks 24 indicators of compromise for TL-2026-0269.

24 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

CVSS 9.8 with no user interaction required.

CVE-2026-21902 is a critical pre-authentication remote code execution vulnerability affecting Juniper Networks PTX Series routers running Junos OS Evolved version 25.4R1-EVO. The flaw resides in the On-Box Anomaly Detection Framework, an internal security monitoring service that was inadvertently exposed to external network access due to incorrect default permissions (CWE-276/CWE-732).

The vulnerability stems from a Python-based REST API server (api_server.py) that binds to 0.0.0.0:8160/TCP instead of the localhost interface. This service is part of the On-Box Anomaly Detection Framework and was designed to be reachable only by other internal processes over the internal routing instance. However, the incorrect permission assignment causes the service to listen on all network interfaces, making it accessible to any unauthenticated remote attacker.

The exploitation chain leverages four REST API endpoints that require no authentication:

1. POST /config/command/<name> — Creates a Command definition with type RE-SHELL containing arbitrary shell syntax 2. POST /config/dag/<name> — Defines a DAG (Directed Acyclic Graph) workflow referencing the malicious command 3. POST /config/dag-instance/<name> — Creates a scheduled execution instance with immediate timing 4. POST /config/commit — Validates and persists the configuration, triggering execution

When the schedule_enforcer.py process (running as root) detects the scheduled DAG instance, it retrieves the command definition and passes the attacker-controlled syntax field directly to subprocess.run(command, shell=True), achieving arbitrary command execution with root privileges. The vulnerable code path flows through execute_dag_instance() -> execute_dag() -> run_bfs_on_dag_actions() -> execute_command(), with no input sanitization at any stage.

The service is enabled by default on affected versions without requiring any specific configuration, meaning all PTX Series routers running vulnerable Junos OS Evolved versions are exposed out of the box. Successful exploitation grants complete device control including configuration manipulation (routing tables, BGP sessions, ACLs), traffic interception or redirection, credential and cryptographic key exfiltration, and service disruption via control-plane interference.

Juniper Networks released this as an out-of-cycle emergency security bulletin (JSA107128) on February 25, 2026, indicating the severity and urgency. The watchTowr Labs team published a detailed technical analysis and proof-of-concept on March 3, 2026, demonstrating the full exploitation chain. Multiple government agencies including the Cyber Security Agency of Singapore issued alerts. No confirmed active exploitation in the wild has been reported, though the trivial exploitation complexity and public PoC availability make exploitation highly likely.

MITRE ATT&CK techniques by tactic:

credential-access

T1040 Network Sniffing

discovery

T1046 Network Service Discovery; T1082 System Information Discovery

execution

T1053 Scheduled Task/Job; T1059 Command and Scripting Interpreter

privilege-escalation

T1068 Exploitation for Privilege Escalation

defense-evasion

T1070 Indicator Removal

command-and-control

T1071 Application Layer Protocol

initial-access

T1190 Exploit Public-Facing Application

Lateral Movement

T1210 Exploitation of Remote Services

Defense Evasion

T1211 Exploitation for Stealth

impact

T1489 Service Stop; T1498 Network Denial of Service; T1565 Data Manipulation

Impact

T1495 Firmware Corruption

Persistence

T1505 Server Software Component

persistence

T1543 Create or Modify System Process

Reconnaissance

T1595.001 Active Scanning: Scanning IP Blocks; T1595.002 Active Scanning: Vulnerability Scanning

defense-impairment

T1685 Disable or Modify Tools

Remediation

Patches

  • Junos OS Evolved 25.4R1-S1-EVO (emergency out-of-cycle patch)
  • Junos OS Evolved 25.4R2-EVO
  • Junos OS Evolved 26.2R1-EVO

Immediate actions

  • Block TCP port 8160 at network perimeter via ACLs and firewall filters
  • Restrict management plane access to trusted internal subnets only
  • Disable the vulnerable service using CLI command: request pfe anomalies disable
  • Audit PTX Series router fleet for Junos OS Evolved version 25.4R1-EVO exposure
  • Monitor for unauthorized connections to port 8160/TCP on all PTX Series devices

Workarounds

  • Disable On-Box Anomaly Detection: request pfe anomalies disable
  • Apply firewall filter to block external access to TCP port 8160
  • Restrict management interface access via lo0 filter to trusted hosts only

Longer-term hardening

  • Deploy network segmentation isolating router management interfaces from untrusted networks
  • Implement out-of-band management networks for all critical network infrastructure
  • Deploy network-based IDS/IPS signatures for anomalous HTTP traffic to port 8160
  • Establish automated version compliance monitoring for Juniper infrastructure
  • Review and harden all Juniper device management plane access controls

Affected and fixed versions

  • Juniper Networks — Junos OS Evolved
    Vulnerable versions: 25.4R1-EVO (all builds before 25.4R1-S1-EVO)
    Fixed in: 25.4R1-S1-EVO; 25.4R2-EVO; 26.2R1-EVO
  • Juniper Networks — PTX Series Routers
    Vulnerable versions: All PTX models running vulnerable Junos OS Evolved versions
    Fixed in: PTX models running patched Junos OS Evolved

Timeline

Last updated · revalidated 1× · latest source

  • CVE-2026-21902 published to NVD; Juniper Networks releases out-of-cycle emergency security bulletin JSA107128
  • Threat intelligence reports begin covering the vulnerability; ThreatIntelReport publishes initial technical analysis
  • Juniper confirms patched versions 25.4R1-S1-EVO and 25.4R2-EVO available; workaround via request pfe anomalies disable documented
  • Cyber Security Agency of Singapore issues Alert AL-2026-020; multiple security news outlets publish analyses and risk assessments
  • UpGuard and additional security vendors publish risk assessments and exposure analyses for enterprise customers
  • Vendor and third-party trackers (runZero) clarify the precise vulnerable version boundary: 25.4R1-EVO through versions prior to 25.4R1-S1-EVO, and 25.4R1-S1-EVO through versions prior to 25.4R2-EVO; releases before 25.4R1-EVO confirmed not vulnerable.
  • watchTowr Labs researcher McCaulay Hudson (@_mccaulay) credited as discoverer and author of the technical write-up and public PoC exploit.
  • NVD record last modified with additional details including CVSS 4.0 score of 9.3 and updated CWE/CAPEC references
  • watchTowr Labs publishes detailed technical analysis with full exploitation chain walkthrough and PoC tools on GitHub
  • Purple Ops publishes detailed exploitation guide with step-by-step API request examples and detection recommendations
  • Cyble Research and Intelligence Labs includes CVE-2026-21902 in weekly vulnerability report, confirming ongoing risk assessment
  • As of 2026-05-29, CVE-2026-21902 remains PATCHED: Juniper's out-of-cycle fixes (25.4R1-S1-EVO/25.4R2-EVO) are public, the flaw was vendor-discovered with no confirmed in-the-wild exploitation, and it is not in CISA KEV. A public watchTowr PoC keeps residual risk for unpatched PTX fleets, but no active campaign or actor is reported.

Update history

Sources cited

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 14 sources; published ; last updated .

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats