Skip to main content
← Vulnerabilities

Cleartext storage of sensitive information in Ivanti UWM before version 2026.4 allows a local authenticated attacker to retrieve another…

6.3MediumCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
25/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Ivanti UWM is affected by a flaw that stores sensitive information in cleartext, letting a local attacker who has a valid account read another local user's session token. The attacker must be on the same machine and must be logged in, but no user interaction is needed.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

Cleartext storage of sensitive information in Ivanti UWM before version 2026.4 allows a local authenticated attacker to retrieve another local user's session token.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach14/20Affects Ivanti (an enterprise product or network appliance)
  • Severity6.3/10CVSS 6.3
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-105813 (Cleartext storage of sensitive information in Ivanti UWM before version 2026.4 allows a local authenticated attacker to retrieve another…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-105813 (entry last updated 2026-11-10):
Affected:
- Ivanti User Workspace Manager: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-105813 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-105813 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://hub.ivanti.com/s/article/Security-Advisory-Ivanti-User-Workspace-Manager-CVE-2026-105813?language=en_US
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-105813
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-105813.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Ivanti User Workspace Manager

    Version range not reported

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.