# CVE-2026-101997: SQL injection in Junos OS

> An unauthenticated attacker can execute code with root privileges on Juniper SRX devices via SQL injection in the Security Intelligence feed connection.

- **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`)
- **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-mqrp-79wg-jvr3

## What is CVE-2026-101997?

CVE-2026-101997 is a critical SQL injection 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 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ipfd of Juniper Networks Junos OS on SRX Series allows an unauthenticated network-based attacker to execute code with root privileges via a configured Security Intelligence feed connection.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-101997 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101997 is a critical SQL injection 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-101997 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-101997/ (Markdown: https://insights.sbomify.com/CVE-2026-101997/index.md)
```

## Sources

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

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