VulnerabilityPublished 16 Mar 2026

CVE-2026-4217: XREAL Nebula App · Unprotected Storage of Credentials

Affects XREAL Nebula AppSource CVE Database V5

Compare

Public exploit available · CVSS 2.0 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

2.0Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
XREALNebula App	Affected =3.2.0 =3.2.1	Fixed in–

AI-suggested

To mitigate CVE-2026-4217, organizations should implement strict physical and local access controls on devices running the XREAL Nebula App to prevent unauthorized local access. Employ device-level security measures such as strong authentication, device encryption, and secure lock screens to reduce the risk of local exploitation. Monitor devices for unusual local activity or attempts to manipulate app files or parameters. Where possible, restrict installation or usage of vulnerable app versions and consider disabling or limiting the app’s cloud storage features until a vendor patch is available. Engage with the vendor or community to track any forthcoming updates or patches addressing this vulnerability. Additionally, conduct regular security audits of app permissions and local environment security to detect potential exploitation attempts. For high-security environments, consider alternative applications with stronger key management assurances.

Description

A security vulnerability has been detected in XREAL Nebula App up to 3.2.1 on Android. This impacts an unknown function of the file in ai/nreal/nebula/flutterPlugin/CloudStoragePlugin.java of the component ai.nreal.nebula.universal. Such manipulation of the argument accessKey/secretAccessKey/securityToken leads to unprotected storage of credentials. The attack can only be performed from a local environment. The attack requires a high level of complexity. The exploitability is said to be difficult. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The potential impact of CVE-2026-4217 is limited due to the requirement for local access and the high complexity of exploitation. If successfully exploited, an attacker might manipulate key parameters, potentially gaining unauthorized access to cloud storage resources or disrupting secure communications within the app. However, the vulnerability does not directly compromise data confidentiality, integrity, or availability on a broad scale. The lack of remote exploitability and user interaction reduces the risk of widespread attacks. Organizations using the XREAL Nebula App on Android devices could face targeted local threats, especially in environments where devices are shared or physically accessible by untrusted individuals. The absence of vendor response and patches means the vulnerability remains unmitigated, but the low severity and exploitation difficulty limit its immediate threat to global organizations.

Summary

CVE-2026-4217 identifies a key management error within the XREAL Nebula App (versions 3.2.0 and 3.2.1) on Android platforms. The vulnerability arises from improper manipulation of key-related parameters—specifically accessKey, secretAccessKey, and securityToken—within the ai/nreal/nebula/flutterPlugin/CloudStoragePlugin.java file of the ai.nreal.nebula.universal component. This flaw can lead to incorrect handling or exposure of sensitive key material, potentially undermining secure access to cloud storage or related services. The attack vector is strictly local, meaning an attacker must have physical or local access to the device to exploit the vulnerability. The complexity of the attack is high, indicating that exploitation requires advanced skills and conditions. The vulnerability does not require user interaction and does not affect confidentiality, integrity, or availability significantly, as reflected in its low CVSS 4.0 score of 2. The vendor was notified but has not issued any response or patch, and no known exploits are currently active in the wild. This vulnerability highlights a risk in key management practices within the app's cloud storage plugin, which could be leveraged in targeted local attacks but is unlikely to be exploited remotely or at scale.

References

Community reviews

Loading reviews…