# CVE-2026-26121: Azure IOT Explorer Spoofing Vulnerability

> An unauthorized attacker can exploit a server-side request forgery flaw in Azure IoT Explorer to perform spoofing attacks over the network.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2026
- **Updated:** 19 Jun 2026
- **Also known as:** GHSA-vg48-j87h-hc85

## What is CVE-2026-26121?

CVE-2026-26121 is a high-severity server-side request forgery vulnerability in Microsoft Azure IoT Explorer, published on 10 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server-side request forgery (ssrf) in Azure IoT Explorer allows an unauthorized attacker to perform spoofing over a network.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Microsoft Azure Iot Explorer.

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

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

## Is CVE-2026-26121 being exploited?

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

## Other vulnerabilities in Microsoft Azure IoT Explorer

- [CVE-2026-23661](https://insights.sbomify.com/CVE-2026-23661/): Azure IoT Explorer Information Disclosure Vulnerability (high 7.5)
- [CVE-2026-23662](https://insights.sbomify.com/CVE-2026-23662/): Azure IoT Explorer Information Disclosure Vulnerability (high 7.5)
- [CVE-2026-23664](https://insights.sbomify.com/CVE-2026-23664/): Azure IoT Explorer Information Disclosure Vulnerability (high 7.5)
- [CVE-2026-21528](https://insights.sbomify.com/CVE-2026-21528/): Azure IoT Explorer Information Disclosure Vulnerability (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26121 is a high-severity server-side request forgery vulnerability in Microsoft Azure IoT Explorer, published on 10 Mar 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-26121 in the wild and no public exploit code.

Affected product: Microsoft Azure IoT Explorer. 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-26121/ (Markdown: https://insights.sbomify.com/CVE-2026-26121/index.md)
```

## Sources

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

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