CVE-2025-55333VulnerabilityPublished 14 Oct 2025Updated 22 Feb 2026

CVE-2025-55333: Microsoft Windows 10 Version 1507 · Incomplete Comparison with Missing Factors

Affects Microsoft Windows 10 Version 1507Source CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.1Medium

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

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

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C

Base metrics

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

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

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
Microsoft Windows 10 Version 1507	Affected =10.0.10240.0	Fixed in–

AI-suggested

1. Upgrade affected systems from Windows 10 Version 1507 to a supported, patched version of Windows 10 or later, as this legacy version is no longer supported and lacks security updates. 2. Enforce strict physical security controls to prevent unauthorized physical access to devices, including secure storage, access logging, and surveillance. 3. Implement full device inventory and asset management to quickly identify and isolate vulnerable devices. 4. Use multifactor authentication and hardware-based security modules (e.g., TPM) to strengthen BitLocker’s protection where possible. 5. Regularly back up encrypted data and verify backup integrity to mitigate data loss risks. 6. Monitor for signs of device tampering or unauthorized access, including unusual boot attempts or hardware changes. 7. Educate users and administrators about the risks of physical attacks and the importance of securing devices. 8. Consider additional encryption layers or endpoint protection solutions that can detect or prevent unauthorized access attempts. 9. Stay informed about vendor advisories and apply patches promptly once available. 10. For high-risk environments, consider device retirement or replacement if upgrading is not feasible.

Description

Incomplete comparison with missing factors in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.

Impact

The primary impact of CVE-2025-55333 is the compromise of data confidentiality and integrity on devices running Windows 10 Version 1507 with BitLocker enabled. An attacker with physical access can bypass BitLocker encryption, exposing sensitive data or modifying it without detection. This can lead to data breaches, intellectual property theft, and loss of trust in device security. Since availability is not affected, systems remain operational, but the security guarantees of BitLocker are nullified. Organizations relying on BitLocker for endpoint encryption, especially in regulated industries such as finance, healthcare, and government, face increased risk of compliance violations and reputational damage. The requirement for physical access limits remote exploitation but raises concerns in scenarios involving device theft, loss, or insider threats. The lack of patches means vulnerable systems remain exposed until mitigations or upgrades are applied. Legacy systems running this early Windows 10 version are particularly vulnerable, and the impact is exacerbated in environments with weak physical security controls. Overall, the vulnerability threatens the foundational security of encrypted data on affected devices, potentially enabling attackers to bypass encryption protections and access or alter confidential information.

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-55333 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Feb 2026, 20:56 UTC

WeaknessesCWE-1023

Technical details

References

Community reviews

Related threats