Home › Intelligence › Brief
VULNERABILITY BRIEF 🟡 Medium Vulnerability

Cleartext Credential Storage in Johnson Controls Simplex Incident Manager (CVE‑2026‑27875) Risks Local Credential Theft

A medium‑severity vulnerability (CVE‑2026‑27875) in Johnson Controls Simplex Incident Manager stores passwords and tokens in cleartext memory, allowing a low‑privilege local attacker to extract them. For SOC 2‑compliant organizations, this exposes a gap in access‑control safeguards and audit evidence.

Verisq™ Intelligence · 📅 August 20, 2026 · 📰 cisa.gov
🟡
Severity
Medium
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
3 recommended
📰
Source
cisa.gov

CVE-2026-27875: Cleartext Credential Storage in Johnson Controls Simplex Incident Manager Enables Local Credential Extraction

What It Is — The Simplex Incident Manager (versions ≤ V2.01) stores passwords and authentication tokens in cleartext within system memory. A local attacker with low privileges can dump memory and retrieve those credentials.

Exploitability — No public exploit code, but the flaw is trivial to weaponize with standard memory‑dump tools. CVSS 3.1 base score 5.8 (Medium). CISA has issued advisory ICSA‑26‑232‑01.

Affected Products — Johnson Controls Simplex Incident Manager ≤ V2.01 (building‑automation/ICS platform).

Why It Matters for Compliance & Audit Readiness

  • SOC 2 Access Control criteria (CC6.1, CC6.2) require encryption of sensitive data at rest and in use; cleartext storage directly violates those controls.
  • Continuous control monitoring must capture evidence that credential handling is protected; otherwise auditors will flag a material weakness.
  • Enterprise buyers in critical‑infrastructure sectors increasingly demand proof of secure credential management as part of SOC 2 attestations.

Recommended Actions

  1. Upgrade to Simplex Incident Manager v2.01.01 or later.
  2. Restrict local console access to authorized personnel; enforce least‑privilege on host OS accounts.
  3. Deploy endpoint detection that alerts on memory‑dumping utilities or suspicious processes.
  4. Enable full‑disk encryption and secure boot to mitigate offline analysis.
  5. Capture and retain audit logs of local access attempts for SOC 2 evidence.

Source: CISA Advisory ICSA‑26‑232‑01

📰 Original Source
https://www.cisa.gov/news-events/ics-advisories/icsa-26-232-01 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →