How severe is CVE-2026-95699?

CVE-2026-95699 has a CVSS 3.x base score of 9.6, rated critical severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability high.

Is CVE-2026-95699 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-95699?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-95699 published?

CVE-2026-95699 was published on 2026-09-24 and last updated on 2026-09-25.

CVE-2026-95699

CVE-2026-95699 is a critical-severity vulnerability with a CVSS 3.x base score of 9.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-653.

Key facts

Severity: Critical (CVSS 3.x base score 9.6)
CVSS v4: 8.4
EPSS exploit prediction: 0% (20th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-653
Published: 2026-09-24
Last modified: 2026-09-25

Description

Prior to 9/18/2026, the iSteamX mobile application's AWS policy could grant authenticated users access to wildcard MQTT topics, which can expose other users' device data and allow the attacker to start and stop other connected users' devices. This risked exposing user profile information and potential scalding due to unintended device activation.

Frequently asked questions

What is CVE-2026-95699?: Prior to 9/18/2026, the iSteamX mobile application's AWS policy could grant authenticated users access to wildcard MQTT topics, which can expose other users' device data and allow the attacker to start and stop other connected users' devices. This risked exposing user profile information and potential scalding due to unintended device activation.
How severe is CVE-2026-95699?: CVE-2026-95699 has a CVSS 3.x base score of 9.6, rated critical severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability high.
Is CVE-2026-95699 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-95699?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-95699 published?: CVE-2026-95699 was published on 2026-09-24 and last updated on 2026-09-25.

References

Other CWE-653 vulnerabilities

CVE-2026-4692 — Critical (CVSS 10.0): Sandbox escape in the Responsive Design Mode component. This vulnerability was fixed in Firefox 149, Firefox ESR…
CVE-2026-63071 — Critical (CVSS 9.8): Improper Isolation or Compartmentalization vulnerability in Apache Syncope. An administrator with adequate…
CVE-2026-53421 — Critical (CVSS 9.8): Improper Isolation or Compartmentalization vulnerability in Apache Syncope. An administrator with adequate…
CVE-2026-53405 — Critical (CVSS 9.8): Improper Isolation or Compartmentalization vulnerability in Apache Syncope. An administrator with adequate…
CVE-2025-1974 — Critical (CVSS 9.8): A security issue was discovered in Kubernetes where under certain conditions, an unauthenticated attacker with access…
CVE-2024-33768 — Critical (CVSS 9.8): lunasvg v2.3.9 was discovered to contain a segmentation violation via the component composition_solid_source_over.

Browse all CWE-653 vulnerabilities →