CyberSecBulletin
CVE-2025-48819NVD status: Analyzed

Windows 10 Version 1507: Sensitive Data Storage in Improperly Locked Memory

Published Updated By the CyberSecBulletin desk

CVE-2025-48819 is a high-severity sensitive data storage in improperly locked memory vulnerability in Windows 10 Version 1507 from Microsoft, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited from the same local network by an attacker with a low-privileged account, without any action from a user. The record lists version 10.0.10240.21073 as the first without the flaw, so updating Windows 10 Version 1507 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.35% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Windows 10 Version 1507 to 10.0.10240.21073 or a later version.
  2. Update Windows 10 Version 1607 to 10.0.14393.8246 or a later version.
  3. Update Windows 10 Version 1809 to 10.0.17763.7558 or a later version.
  4. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 150710.0.10240.0 up to, but not including, 10.0.10240.2107310.0.10240.21073
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.824610.0.14393.8246
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.755810.0.17763.7558
MicrosoftWindows 10 Version 21H210.0.19044.0 up to, but not including, 10.0.19044.609310.0.19044.6093
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.609310.0.19045.6093
MicrosoftWindows 11 version 22H210.0.22621.0 up to, but not including, 10.0.22621.562410.0.22621.5624
MicrosoftWindows 11 version 22H310.0.22631.0 up to, but not including, 10.0.22631.562410.0.22631.5624
MicrosoftWindows 11 Version 23H210.0.22631.0 up to, but not including, 10.0.22631.562410.0.22631.5624
MicrosoftWindows 11 Version 24H210.0.26100.0 up to, but not including, 10.0.26100.465210.0.26100.4652
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0 up to, but not including, 6.1.7601.278206.1.7601.27820
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0 up to, but not including, 6.1.7601.278206.1.7601.27820
MicrosoftWindows Server 2008 Service Pack 26.0.6003.0 up to, but not including, 6.0.6003.234186.0.6003.23418
MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)6.0.6003.0 up to, but not including, 6.0.6003.234186.0.6003.23418
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.255736.2.9200.25573
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.255736.2.9200.25573
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.226766.3.9600.22676
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.226766.3.9600.22676
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.824610.0.14393.8246
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.824610.0.14393.8246
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.755810.0.17763.7558
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.755810.0.17763.7558
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.393210.0.20348.3932
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0 up to, but not including, 10.0.25398.173210.0.25398.1732
MicrosoftWindows Server 202510.0.26100.0 up to, but not including, 10.0.26100.465210.0.26100.4652
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0 up to, but not including, 10.0.26100.465210.0.26100.4652

Version data comes from the organisation that assigned the CVE; 10 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
AdjacentThe attacker must be on the same local network segment.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).

Official description

Sensitive data storage in improperly locked memory in Windows Universal Plug and Play (UPnP) Device Host allows an authorized attacker to elevate privileges over an adjacent network.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Sensitive Data Storage in Improperly Locked Memory

The product stores sensitive data in memory that is not locked, or that has been incorrectly locked.

How developers prevent this class of flaw

  • Identify data that needs to be protected from swapping and choose platform-appropriate protection mechanisms.
  • When using potentially risky functions such as mlock() or VirtualLock(), check return values to ensure that locking operations are successful.

More Sensitive Data Storage in Improperly Locked Memory vulnerabilities (CWE-591)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Windows 10 Version 1507

All Windows 10 Version 1507 vulnerabilities

Recent Sensitive Data Storage in Improperly Locked Memory vulnerabilities

Spotted an error? Tell us.