CVE-2026-118740 - Aspire Dashboard Security Feature Bypass (Missing Authorization)
Detects exploitation and exposure conditions for CVE-2026-118740, a security feature bypass (CWE-862, Missing Authorization) in the .NET Aspire Dashboard (Aspire.Dashboard.Sdk packages) prior to version 13.6.5. The Aspire Dashboard exposes OpenTelemetry data (traces, logs, metrics), resource details, environment variables and console logs. A missing-authorization flaw allows an unauthenticated or improperly-authorized actor on the network to bypass the dashboard's frontend/OTLP authentication and access sensitive telemetry and configuration. Because the issue is an authorization bypass rather than a memory-corruption bug, detection focuses on exposed/vulnerable dashboard instances, anomalous unauthenticated access to dashboard HTTP endpoints and OTLP ports (default 18888 frontend, 18889 OTLP), and access that lacks the expected authentication token/header. Exploit status is theoretical as of disclosure (2026-11-12).
Vulnerability Intelligence
TheoreticalAffected Software
- Vendor
- nuget
- Product
- Aspire.Dashboard.Sdk.linux-x64, Aspire.Dashboard.Sdk.linux-arm64, Aspire.Dashboard.Sdk.linux-musl-x64, Aspire.Dashboard.Sdk.osx-x64, Aspire.Dashboard.Sdk.osx-arm64, Aspire.Dashboard.Sdk.win-x64, Aspire.Dashboard.Sdk.win-arm64
- Versions
- < 13.6.5
Weakness (CWE)
Timeline
- Disclosed
- November 12, 2026
References & Proof of Concept
- https://github.com/microsoft/aspire/security/advisories/GHSA-4g86-54fm-h9h8
- https://nvd.nist.gov/vuln/detail/CVE-2026-118740
- https://github.com/dotnet/announcements/issues/526
- https://github.com/microsoft/aspire/issues/22148
- https://github.com/microsoft/aspire/commit/0b6bfe2f538d4eed8a9ae7e11651c09dbbe886b8
- https://github.com/microsoft/aspire/releases/tag/v13.6.5
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-118740
- https://github.com/advisories/GHSA-4g86-54fm-h9h8
CVSS
- Attack Vector
- Network
- Attack Complexity
- Low
- Privileges Required
- None
- User Interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
What is CVE-2026-118740 CVE-2026-118740 - Aspire Dashboard Security Feature Bypass (Missing Authorization)?
CVE-2026-118740 - Aspire Dashboard Security Feature Bypass (Missing Authorization) (CVE-2026-118740) maps to the Initial Access and Discovery and Collection tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for CVE-2026-118740 - Aspire Dashboard Security Feature Bypass (Missing Authorization), covering the data sources and telemetry it touches: Microsoft Sentinel, IIS Logs, Network Proxy, Microsoft Defender for Endpoint. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
- Tactic
- Initial Access Discovery Collection
// df00tech DF00-dc8b2fb75e · https://df00tech.com/detections/CVE-2026-118740 · licence: https://df00tech.com/detections/licence
// Detect unauthenticated / token-less access to Aspire Dashboard endpoints (frontend 18888, OTLP 18889)
let aspirePorts = dynamic([18888, 18889]);
union
(
W3CIISLog
| where csUriStem has_any ("/StructuredLogs", "/Traces", "/Metrics", "/ConsoleLogs", "/api/v1/traces", "/api/v1/logs", "/v1/traces", "/v1/logs")
| where sPort in (aspirePorts) or csUriStem has "aspire"
| extend AuthHeaderPresent = iff(isnotempty(csUserAgent) and csUriQuery has_any ("token", "otlp"), true, false)
| where scStatus in (200, 101)
| project TimeGenerated, Computer, cIP, sIP, sPort, csMethod, csUriStem, csUriQuery, scStatus, csUserAgent
),
(
CommonSecurityLog
| where DestinationPort in (aspirePorts)
| where isnotempty(RequestURL) and RequestURL has_any ("StructuredLogs", "Traces", "Metrics", "otlp")
| project TimeGenerated, Computer=DeviceName, cIP=SourceIP, sIP=DestinationIP, sPort=DestinationPort, csMethod=RequestMethod, csUriStem=RequestURL, csUriQuery="", scStatus=0, csUserAgent=DeviceCustomString1
)
| summarize Hits=count(), Methods=make_set(csMethod), URIs=make_set(csUriStem) by cIP, sIP, sPort, Computer, bin(TimeGenerated, 10m)
| where Hits > 5 Flags HTTP access to Aspire Dashboard telemetry endpoints and OTLP ports from clients, highlighting volumes consistent with scraping telemetry via the authorization bypass. Correlate source IPs against known/authorized operators.
Data Sources
Required Tables
False Positives
- Authorized developers or SRE staff legitimately browsing the dashboard from the corporate network.
- Health-check probes or synthetic monitors hitting dashboard endpoints on a schedule.
- Internal load balancers or reverse proxies aggregating requests from a single source IP.
Query fingerprint DF00-dc8b2fb75e · licence
Sigma logsource & community rules
The detection logic for CVE-2026-118740 - Aspire Dashboard Security Feature Bypass (Missing Authorization) (CVE-2026-118740) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: network_connection
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-118740
References (8)
- https://github.com/microsoft/aspire/security/advisories/GHSA-4g86-54fm-h9h8
- https://nvd.nist.gov/vuln/detail/CVE-2026-118740
- https://github.com/dotnet/announcements/issues/526
- https://github.com/microsoft/aspire/issues/22148
- https://github.com/microsoft/aspire/commit/0b6bfe2f538d4eed8a9ae7e11651c09dbbe886b8
- https://github.com/microsoft/aspire/releases/tag/v13.6.5
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-118740
- https://github.com/advisories/GHSA-4g86-54fm-h9h8
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.
- Test 1 Access Aspire Dashboard telemetry endpoint without authorization token
Expected signal: Web/proxy access log entries showing GET requests to /StructuredLogs and /v1/traces on ports 18888/18889 without an Authorization header.
- Test 2 Port scan of Aspire Dashboard default ports
Expected signal: NetworkConnectIP4 / network flow events to ports 18888 and 18889 from the testing host.
- Test 3 Repeated OTLP trace retrieval to simulate telemetry scraping
Expected signal: Ten HTTP GET requests to /v1/traces on port 18889 from a single source within a short window, no Authorization header.
Response Playbook
Triage
- Confirm the affected host is running an Aspire.Dashboard.Sdk package below version 13.6.5 (inventory via dotnet tool/package manifests or deployment manifests).
- Determine whether the Aspire Dashboard frontend (default port 18888) and/or OTLP endpoint (default port 18889) is reachable from untrusted networks; check firewall/NSG and binding address (0.0.0.0 vs loopback).
- Review access logs for the flagged source IPs and confirm whether requests to telemetry endpoints (/StructuredLogs, /Traces, /Metrics, /ConsoleLogs, /v1/traces, /v1/logs) succeeded without an authorization token.
- Assess what sensitive data the exposed dashboard could leak (environment variables, connection strings, console logs, traces containing secrets).
Containment
- Restrict dashboard ports (18888/18889) to loopback or an authenticated reverse proxy / management VLAN via firewall, NSG or security group rules.
- Upgrade the Aspire.Dashboard.Sdk package to 13.6.5 or later and redeploy the affected application(s).
- If immediate patching is not possible, disable the dashboard or enforce frontend/OTLP authentication tokens and rotate any secrets that may have been exposed through telemetry.
Evidence Collection
- Preserve web/reverse-proxy access logs and OTLP connection logs covering the exposure window, including source IPs, URIs and response codes.
- Capture the running package version and deployment manifest showing the vulnerable Aspire.Dashboard.Sdk version.
- Export any telemetry/console-log content that may have been accessed to scope data exposure and identify leaked secrets.
Escalation Criteria
- ! Evidence of successful telemetry or environment-variable retrieval by an unauthorized external source IP.
- ! Exposed dashboard reachable from the public internet or an untrusted network segment.
- ! Indicators that secrets (connection strings, API keys) visible in dashboard telemetry were subsequently used elsewhere.
Investigation Guide
Forensic Artifacts
- >
Web/reverse-proxy access logs showing token-less 200 responses to Aspire telemetry endpoints. - >
Network connection records to ports 18888/18889 from unexpected source IPs. - >
Package lock/manifest files recording the vulnerable Aspire.Dashboard.Sdk version. - >
Aspire Dashboard console-log and trace exports that reveal accessed content.
Tuning Guidance
Baseline the set of legitimate operator source IPs and monitoring systems that access the dashboard and exclude them. Confirm the actual dashboard ports in your environment (18888/18889 are defaults but can be overridden) and tune port lists accordingly. Where a reverse proxy terminates auth, pivot detection to the proxy logs and the presence/absence of the upstream authorization token rather than the backend. Lower the hit threshold if dashboards should normally be loopback-only.
Hunting Queries
Hunt for successful access to Aspire Dashboard telemetry endpoints grouped by source IP to find scraping behavior and identify unauthorized clients.
// df00tech DF00-dc8b2fb75e · https://df00tech.com/detections/CVE-2026-118740 · licence: https://df00tech.com/detections/licence
W3CIISLog | where csUriStem has_any ("StructuredLogs","Traces","Metrics","ConsoleLogs","/v1/traces","/v1/logs") | where scStatus == 200 | summarize count() by cIP, csUriStem, bin(TimeGenerated, 1h) | sort by count_ desc ``` df00tech DF00-dc8b2fb75e · https://df00tech.com/detections/CVE-2026-118740 · licence: https://df00tech.com/detections/licence ```
index=web (uri_path="*StructuredLogs*" OR uri_path="*/v1/traces*" OR uri_path="*ConsoleLogs*") status=200 | stats count by src_ip uri_path | sort - count Atomic Red Team Tests
Simulates an unauthenticated request to the Aspire Dashboard structured logs/OTLP endpoint to generate telemetry matching the bypass pattern (lab only; against a test instance you control).
Command
curl -sk -o /dev/null -w '%{http_code}\n' http://127.0.0.1:18888/StructuredLogs; curl -sk -o /dev/null -w '%{http_code}\n' http://127.0.0.1:18889/v1/traces Cleanup
echo 'No persistent changes made by this test' Expected Telemetry
Web/proxy access log entries showing GET requests to /StructuredLogs and /v1/traces on ports 18888/18889 without an Authorization header.
Expected Detection
KQL/SPL/EQL rules flag non-401/403 access to Aspire telemetry endpoints without an auth token.
Probes the default Aspire Dashboard frontend and OTLP ports to simulate discovery of an exposed vulnerable instance.
Command
for p in 18888 18889; do (echo > /dev/tcp/127.0.0.1/$p) >/dev/null 2>&1 && echo "port $p open"; done Cleanup
echo 'No persistent changes made by this test' Expected Telemetry
NetworkConnectIP4 / network flow events to ports 18888 and 18889 from the testing host.
Expected Detection
CrowdStrike CQL and QRadar AQL rules flag connections to Aspire Dashboard ports.
Issues multiple token-less requests to the OTLP traces endpoint to exceed the detection volume threshold in a lab environment.
Command
1..10 | ForEach-Object { try { Invoke-WebRequest -Uri 'http://127.0.0.1:18889/v1/traces' -UseBasicParsing -TimeoutSec 2 | Out-Null } catch {} } Cleanup
Write-Output 'No persistent changes made by this test' Expected Telemetry
Ten HTTP GET requests to /v1/traces on port 18889 from a single source within a short window, no Authorization header.
Expected Detection
Volume-threshold rules (Hits/conn_count > 5) fire for the single source IP accessing telemetry endpoints.
Related Detections
Related Techniques
Same Tactic: Initial Access
Browse by tactic
- Reconnaissance TA0043
- Resource Development TA0042
- Initial Access TA0001
- Execution TA0002
- Persistence TA0003
- Privilege Escalation TA0004
- Stealth TA0005
- Defense Impairment TA0112
- Credential Access TA0006
- Discovery TA0007
- Lateral Movement TA0008
- Collection TA0009
- Command and Control TA0011
- Exfiltration TA0010
- Impact TA0040