# CVE-2026-102037: Junos OS: SRX Series: An attacker causes arbitrary configuration commit when the custom URL-feed feature is used

> An attacker can commit arbitrary configuration with root privileges via XML injection in the custom URL-feed feature on Juniper SRX devices.

- **Severity:** Critical 9.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-24fq-57v4-c9fp

## What is CVE-2026-102037?

CVE-2026-102037 is a critical vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-91 (XML Injection)

## Which versions are affected by CVE-2026-102037?


## How do I fix CVE-2026-102037?

No fix has been published for CVE-2026-102037 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102037 being exploited?

There is no known exploitation of CVE-2026-102037 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102037 and fix it if it is affected.

What it is: CVE-2026-102037 is a critical vulnerability in Juniper Networks Junos OS, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102037 in the wild and no public exploit code.

Affected product: Juniper Networks Junos OS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102037/ (Markdown: https://insights.sbomify.com/CVE-2026-102037/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102037
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102037
- OSV: https://osv.dev/vulnerability/CVE-2026-102037

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102037/
Summaries are generated and may contain mistakes; the official description above is the record.