dbcve.org
Azure Iot ExplorerApplication · Microsoft

CVE-2026-26121

HIGH · 7.5 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 0.15.14 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Server-side request forgery (SSRF) vulnerability in Azure IoT Explorer enables an unauthorized attacker to induce the application to make arbitrary network requests to internal or external resources, potentially accessing sensitive internal services or exfiltrating data.

MitigationImplement strict allowlist-based URL validation, restrict outgoing network requests to trusted domains, and apply network segmentation to limit the impact of SSRF attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure Iot ExplorerApplication
Affected:< 0.15.14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Azure IoT Explorer version
    Open Azure IoT Explorer, go to Help > About, or run 'iot-explorer --version' from command line if available. On Windows, also check Add/Remove Programs or the executable's properties (right-click iot-explorer.exe > Properties > Details tab) for the version field.
    Affected if The displayed version is lower than 0.15.14 (e.g., 0.15.13, 0.15.0, etc.)
  2. Identify if application makes network requests to arbitrary URLs
    Inspect Azure IoT Explorer usage patterns. The SSRF vulnerability is triggered when the application processes user-supplied URLs for IoT device connections, cloud endpoint configurations, or custom module requests. Monitor network activity using tools like Wireshark or Process Monitor while using features that accept URL inputs (device connection strings, custom endpoints, hub configurations).
    Affected if The application accepts and processes URLs from untrusted input sources, particularly in device connection, cloud gateway, or module configuration features.
  3. Review application network configuration
    Check Azure IoT Explorer settings files or configuration directories for any stored endpoint URLs. On Windows, typical locations include %APPDATA%\iot-explorer or %LOCALAPPDATA%\iot-explorer. Examine any JSON or config files containing connection strings, hub URLs, or custom endpoint definitions.
    Affected if Configurable URL endpoints are stored or processed without strict allowlist validation.

You are affected if Azure IoT Explorer version is lower than 0.15.14 AND the application is used to connect to IoT devices or cloud endpoints via user-supplied or configurable URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.15.14 or later
Fixed in 0.15.14
Interim mitigation

Implement strict allowlist-based URL validation, restrict outgoing network requests to trusted domains, and apply network segmentation to limit the impact of SSRF attacks.

Recommended fix High confidence

Azure IoT Explorer 0.15.14

  1. Navigate to the official Azure IoT Explorer releases page or Microsoft repository
  2. Download Azure IoT Explorer version 0.15.14 or later
  3. Install the updated version following the standard installation procedure
  4. Verify the installed version is 0.15.14 or later by checking the application's about or version information

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Azure Iot Explorer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26121 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26121 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data