CVE-2025-47955: Windows Remote Access Connection Manager Elevation of Privilege Vulnerability
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.90% (FIRST EPSS); higher than 60.3% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper privilege management in Windows Remote Access Connection Manager allows an authorized attacker to elevate privileges locally.
- Published
- Jun 10, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.9% · 60th percentile
- CWE
- CWE-269
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | windows 10 1507 | cpe:2.3:o:microsoft:windows_10_1507 |
| microsoft | windows 10 1607 | cpe:2.3:o:microsoft:windows_10_1607 |
| microsoft | windows 10 1809 | cpe:2.3:o:microsoft:windows_10_1809 |
| microsoft | windows 10 21h2 | cpe:2.3:o:microsoft:windows_10_21h2 |
| microsoft | windows 10 22h2 | cpe:2.3:o:microsoft:windows_10_22h2 |
| microsoft | windows 11 22h2 | cpe:2.3:o:microsoft:windows_11_22h2 |
| microsoft | windows 11 23h2 | cpe:2.3:o:microsoft:windows_11_23h2 |
| microsoft | windows 11 24h2 | cpe:2.3:o:microsoft:windows_11_24h2 |
| microsoft | windows server 2008 | cpe:2.3:o:microsoft:windows_server_2008 |
| microsoft | windows server 2012 | cpe:2.3:o:microsoft:windows_server_2012 |
| microsoft | windows server 2016 | cpe:2.3:o:microsoft:windows_server_2016 |
| microsoft | windows server 2019 | cpe:2.3:o:microsoft:windows_server_2019 |
and 3 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Windows 10 Version 1507
- 10.0.10240.0 and later · before 10.0.10240.21014affected
Microsoft Windows 10 Version 1607
- 10.0.14393.0 and later · before 10.0.14393.8066affected
Microsoft Windows 10 Version 1809
- 10.0.17763.0 and later · before 10.0.17763.7314affected
Microsoft Windows 10 Version 21H2
- 10.0.19044.0 and later · before 10.0.19044.5854affected
Microsoft Windows 10 Version 22H2
- 10.0.19045.0 and later · before 10.0.19045.5854affected
Microsoft Windows 11 version 22H2
- 10.0.22621.0 and later · before 10.0.22621.5335affected
Microsoft Windows 11 version 22H3
- 10.0.22631.0 and later · before 10.0.22631.5335affected
Microsoft Windows 11 Version 23H2
- 10.0.22631.0 and later · before 10.0.22631.5335affected
Microsoft Windows 11 Version 24H2
- 10.0.26100.0 and later · before 10.0.26100.4061affected
Microsoft Windows Server 2008 R2 Service Pack 1
- 6.1.7601.0 and later · before 6.1.7601.27729affected
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
- 6.1.7601.0 and later · before 6.1.7601.27729affected
Microsoft Windows Server 2008 Service Pack 2
- 6.0.6003.0 and later · before 6.0.6003.23317affected
Affected versions · NVD (9)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft windows server 2008all versions
- microsoft windows server 2008r2
- microsoft windows server 2012all versions
- microsoft windows server 2012r2
- microsoft windows server 2016before 10.0.14393.8066
- microsoft windows server 2019before 10.0.17763.7314
- microsoft windows server 2022before 10.0.20348.3630
- microsoft windows server 2022 23h2before 10.0.25398.1611
- microsoft windows server 2025before 10.0.26100.3981
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-34527Windows Print Spooler Remote Code Execution VulnerabilityKEV95Now
- CVE-2021-40444Microsoft MSHTML Remote Code Execution VulnerabilityKEV94Now
- CVE-2025-33053Internet Shortcut Files Remote Code Execution VulnerabilityKEV91Now
Published before and after this one in the same product
- ← EarlierCVE-2025-33075Jun 10, 2025 · Windows Installer Elevation of Privilege Vulnerability31Monitor
- ← EarlierCVE-2025-47160Jun 10, 2025 · Windows Shortcut Files Security Feature Bypass Vulnerability21Monitor
- Later →CVE-2025-47159Jul 8, 2025 · Windows Virtualization-Based Security (VBS) Elevation of Privilege Vulnerability31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-38014273 days apartWindows Installer Elevation of Privilege VulnerabilityKEV63This week
- CVE-2024-26169455 days apartWindows Error Reporting Service Elevation of Privilege VulnerabilityKEV62This week
- CVE-2025-330670 days apartWindows Task Scheduler Elevation of Privilege Vulnerability33Monitor
- CVE-2025-21287147 days apartWindows Installer Elevation of Privilege Vulnerability31Monitor
- CVE-2025-2746828 days apartWindows Kernel-Mode Driver Elevation of Privilege Vulnerability28Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.