CVE Tools

CVE-2026-49163

Application Insights Profiler Elevation of Privilege Vulnerability

No known exploitation. EPSS puts it in the 62nd percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether you use Application Insights Profiler in your application setup (and confirm which hosts/services expose it).
  2. Review who has valid application credentials that could reach Application Insights Profiler from the network (especially any shared accounts, service accounts, or leaked credentials).
  3. Look for any vendor update or hotfix release notes that address CVE-2026-49163; if no fix exists yet, proceed to the compensating controls in the next steps.
  4. Restrict network access to Application Insights Profiler so it is not reachable from the public internet (allow only required internal networks/IPs).
  5. Reduce credential risk: rotate any credentials used by your app/profile tooling and remove unnecessary permissions.
  6. If you can’t patch immediately, temporarily disable Application Insights Profiler in the environment where it isn’t required, or limit it to a tightly controlled internal environment only.

What it is

From the CVE record

Improper limitation of a pathname to a restricted directory ('path traversal') in Application Insights Profiler allows an authorized attacker to elevate privileges over a network.

In plain language

Written by AI from the record

Application Insights Profiler has a path-traversal weakness that an authenticated attacker can use to break out of intended file limits and run commands, which is serious for small businesses if your app credentials could be obtained—but there’s no confirmed patch available right now.

Authenticated attackers can exploit a path traversal flaw in Application Insights Profiler to bypass pathname restrictions and execute commands or access files outside the allowed directory, enabling privilege escalation and full impact on confidentiality, integrity, and availability.

If you're affected

  • Full system compromise possible
  • Sensitive data exposure
  • Ransomware-ready environment
  • Service disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS62nd
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.0% chance of exploitation activity in the next 30 days, which ranks it in the 62nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

8 events over 11 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Record updatedrecord updated, record updated
  3. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

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

Scored 8.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store