Skip to main content

Junos OS CVE-2026-102037

| EUVDEUVD-2026-101362 CRITICAL
XML Injection (aka Blind XPath Injection) (CWE-91)
2026-10-14 juniper GHSA-24fq-57v4-c9fp
9.2
CVSS 4.0 · Vendor: juniper
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Control or MITM configured URL-feed server
  2. Delivery
    Return crafted malicious XML response
  3. Exploit
    utmd parses and injects into config
  4. Execution
    Commit arbitrary configuration as root
  5. Impact
    Full device takeover

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization XPath query parameterization
Exploitation Conditions

Exploitation requires the SRX device to be running UTM with a custom URL-category feed (custom URL-feed) pointing at a configured custom URL-feed server - a non-default feature that must be explicitly enabled. The attacker must additionally control that feed server or be positioned to intercept and alter its response (MITM) so utmd receives malicious XML. Devices without a configured custom URL-feed are not exposed via this path. While no credentials are needed (PR:N), these configuration and positioning prerequisites (reflected as AT:P) are the primary limiting factors; the exploit is network-reachable with low complexity only once they hold.

Impact

This is a genuine high-priority issue, not an inflated high-CVSS artifact. The provided CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N) with VC:H/VI:H/VA:H yields 9.2 (Critical), and the outcome - an unauthenticated attacker committing arbitrary device configuration with root privileges - represents total compromise of a security appliance. The key tempering signal is AT:P (Attack Requirements: Present): exploitation is not a simple remote-unauth hit against a default box. It requires the SRX to have a UTM custom URL-feed server configured AND the attacker to control or intercept that server's response, so this is conditional rather than universally reachable. No EPSS score, CISA KEV listing, or POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation - the risk is driven by severity and ease-of-use once the precondition is met, not by observed in-the-wild activity. Supplemental metrics reinforce priority (AU:Y automatable, V:C concentrated value), meaning that where the precondition holds, exploitation could be scripted. Note a minor inconsistency: the vector marks subsequent-system availability SA:L while SC:N/SI:N, and the 'root configuration commit' outcome arguably implies broader device/scope impact than the subsequent-system metrics capture - verify blast radius against the Juniper advisory.

Exploit ScenarioDerived

An SRX Series firewall is configured to pull a UTM custom URL-category feed from an external URL-feed server. An attacker who controls that feed server (or who can machine-in-the-middle the unauthenticated/unvalidated connection to it) returns a crafted response containing injected XML, which utmd parses and uses to commit attacker-chosen configuration on the device as root. No public exploit code was provided in the intelligence, so this reflects the CVSS network vector (AV:N) and low attack complexity (AC:L) rather than an observed POC.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

XML injection in the Unified Threat Management daemon (utmd) of Junos OS on SRX Series devices allows an unauthenticated network attacker to push arbitrary Junos device configuration that the daemon then commits with root privileges, by serving a crafted XML response from a configured custom URL-feed server. Exploitation is not opportunistic: the SRX must be running UTM with a custom URL-category feed pointed at an attacker-influenced server, and the attacker must either control that feed server or be positioned to intercept and modify its response (a MITM), which is why the vendor's CVSS 4.0 score of 9.2 sits alongside an independent assessed vector of CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Impact is total on exposed devices - full confidentiality, integrity and availability loss on the affected SRX - but no public exploit has been identified at time of analysis and there is no confirmed active exploitation. Treat it as a genuine high-priority issue rather than an inflated high-CVSS artifact, and prioritize any SRX running a custom URL-feed.

RemediationAI

Juniper's advisory JSA112186 (https://supportportal.juniper.net/JSA112186) is the authoritative source for the fixed Junos OS release covering this utmd XML injection; patch status is 'Patch available per vendor advisory' and the exact fixed version is not restated in the intelligence supplied here, so consult the advisory for the release matching your SRX platform and Junos OS train and upgrade before re-enabling affected functionality. Where an immediate upgrade is not possible, the most direct compensating control is to remove or disable the custom URL-category feed from the UTM configuration so utmd never ingests third-party XML; the trade-off is loss of custom URL categorization for that policy until the feed is restored on a patched build. Where the feed must remain active, pin the custom URL-feed to a server you fully control and enforce TLS with certificate validation so a network-positioned attacker cannot substitute the response - the trade-off is that misconfigured or expired certificates will break feed updates. Additionally, restrict utmd's outbound reachability to the specific feed server addresses or management network (this reduces MITM opportunities but requires updating rules whenever feed infrastructure changes), and monitor commit/audit logs for unexpected configuration commits originating from the UTM daemon, since such commits are a strong indicator of successful exploitation. Treat any SRX that ran an unpatched build with an attacker-reachable custom URL-feed as potentially compromised and audit its configuration.

Affected VersionsENISA

Junos OS 23.4 <23.4R2-S8.13
Junos OS 24.2 <24.2R2-S5.5
Junos OS 25.4 <25.4R1-S3
Junos OS 25.2 <25.2R2-S2
Junos OS 24.4 <24.4R2-S5
Junos OS 26.2 <26.2R1-S2

Affected Packages

euvd junos_os fix: 23.4R2-S8.13, 24.2R2-S5.5, 24.4R2-S5, 25.2R2-S2, 25.4R1-S3, 26.2R1-S2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is utmd, the Unified Threat Management daemon in Juniper Networks Junos OS, mapped under CPE cpe:2.3:a:juniper_networks:junos_os:*:*:*:*:*:*:*:*, i.e. a wildcard across Junos OS releases rather than a single fixed version. The root-cause class is CWE-91 (XML Injection): content received from an external source is interpolated into an XML document without neutralization, so attacker-supplied markup is parsed by the daemon as XML rather than treated as inert data. In this deployment, utmd polls a custom URL-category feed server to retrieve URL categorization data, parses the XML reply, and applies the result within a daemon that operates at root privilege. Because the malicious payload crosses from a network response into the daemon's privileged configuration path, a tampered feed response can be interpreted as configuration instructions and committed on the device - the injection is therefore both a parser flaw and a privilege-boundary failure. The vulnerability is not generic to all Junos OS deployments: it requires UTM to be active and a custom URL-feed (custom URL-category feed) to be explicitly configured and pointed at a server, which the independent assessment reflects as the AT:P prerequisite in the CVSS 4.0 vector. Devices without that configuration are not reachable through this code path, and the vector's PR:N confirms no credentials are needed once the configuration and positioning prerequisites are met.

Know when Junos Os gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (juniper) PRIMARY 9.2 HIGH
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:L/AU:Y/R:A/V:C/RE:M
vuln.today AI 8.1 HIGH

AV:N and PR:N since the malicious response is delivered over the network without credentials, but AC:H because exploitation depends on a configured custom URL-feed server the attacker must control or intercept (CVSS 3.1 has no AT metric).

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (juniper).

CVSS VectorVendor: juniper

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
Low

Lifecycle Timeline

4
Patch available
Oct 14, 2026 - 18:05 EUVD
Severity Changed
Oct 14, 2026 - 17:22 NVD
HIGH CRITICAL
CVSS changed
Oct 14, 2026 - 17:22 NVD
8.1 (HIGH) 9.2 (CRITICAL)
CVE Published
Oct 14, 2026 - 16:51 cve.org
CRITICAL 9.2

DescriptionCVE.org

An XML Injection vulnerability in the Unified Threat Management daemon (utmd) of Juniper Networks Junos OS on SRX Series devices allows an unauthenticated network attacker to commit arbitrary device configuration with root privileges via a malicious response from a configured custom URL-feed server.

Executive ViewAI

Why It Matters

Juniper SRX Series firewalls running Junos OS with Unified Threat Management (UTM) and a custom URL-feed are affected by a critical vulnerability (CVE-2026-102037) that could allow an unauthenticated attacker to fully compromise the device, including its configuration and security controls. Organizations using these devices for perimeter security face potential total loss of confidentiality, integrity, and availability, which could lead to network-wide breaches or outages. While exploitation requires specific conditions-an attacker-controlled or intercepted URL-feed server-the severity and potential impact warrant immediate mitigation efforts.

Business Impact: High
Compensating Controls

Disable custom URL-feed functionality on SRX devices if not essential; if required, ensure the feed server is fully trusted and secured, enforce TLS with certificate validation, and restrict network access to the feed server. Monitor device logs for unauthorized configuration changes. Apply vendor-provided mitigations when available.

Threat Intelligence Overview

EPSS Score
0.5%
Top 60% exploitable
Prevalence
High
Juniper SRX Series are widely deployed enterprise firewall/UTM appliances
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

CVE-2026-102059 HIGH
8.7 Oct 14

OS command injection in the phcd phone-home daemon of Juniper Networks Junos OS and Junos OS Evolved lets an adjacent, u

CVE-2026-101956 CRITICAL
9.3 Oct 14

Unauthenticated remote code execution with root privileges affects Juniper Networks Junos OS devices that expose the J-W

CVE-2026-102175 CRITICAL
9.3 Oct 14

Heap-based buffer overflow in the sdxd service-deployment daemon of Juniper Networks Junos OS and Junos OS Evolved allow

CVE-2026-33792 CRITICAL
9.3 Oct 14

A stack-based buffer overflow in the srxpfe packet forwarding process of Juniper Networks Junos OS on SRX Series devices

CVE-2026-101986 CRITICAL
9.3 Oct 14

Unauthenticated remote code execution with elevated privileges is possible in Juniper Junos OS and Junos OS Evolved thro

CVE-2026-101982 CRITICAL
9.3 Oct 14

Remote root code execution in the routing protocol daemon (rpd) of Juniper Junos OS is reachable through protocol-valid

CVE-2026-101990 CRITICAL
9.3 Oct 14

Remote code execution (on Junos OS) and rpd denial of service (on Junos OS and Junos OS Evolved) result from a stack-bas

CVE-2026-33796 CRITICAL
9.3 Oct 14

Remote code execution with root privileges on Juniper Networks Junos OS and Junos OS Evolved is possible when the routin

CVE-2026-101983 CRITICAL
9.3 Oct 14

Remote code execution and denial of service in Juniper Networks Junos OS and Junos OS Evolved arise from a stack-based b

CVE-2026-101954 CRITICAL
9.3 Oct 14

Unauthenticated remote attackers can gain root-level configuration access and fully compromise Juniper Junos OS and Juno

CVE-2026-101980 CRITICAL
9.3 Oct 14

Integer underflow in the Junos OS kernel can crash a device when the Extended Echo feature (RFC 8335 ICMP probing) is co

CVE-2026-101950 CRITICAL
9.3 Oct 14

Heap-based buffer overflow in Juniper Networks Junos OS on SRX Series devices that have Secure Vector Routing (SVR) enab

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy