CVE-2025-49671VulnerabilityPublished 8 Jul 2025Updated 13 Feb 2026

CVE-2025-49671: Microsoft Windows Server 2008 R2 Service Pack 1 · Information Exposure

Affects Microsoft Windows Server 2008 R2 Service Pack 1Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
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: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of integrity within 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 8 Jul 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-25.

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.

cwe-125

What to do

Affected software

Product	Affected	Fixed in
Microsoft Windows Server 2008 R2 Service Pack 1	Affected =6.1.7601.0	Fixed in–

AI-suggested

1. Disable RRAS if it is not required, especially on legacy Windows Server 2008 R2 systems, to eliminate the attack surface. 2. If RRAS is necessary, restrict access to RRAS services using network segmentation and firewall rules to limit exposure to trusted networks and users only. 3. Monitor network traffic for unusual RRAS-related activity or unexpected connection attempts that could indicate exploitation attempts. 4. Apply any available security updates or hotfixes from Microsoft as they become available, even if official support has ended, through extended support agreements or third-party patch providers. 5. Implement strict user interaction policies and educate users about the risks of initiating unexpected RRAS connections or responding to unsolicited network prompts. 6. Plan and prioritize migration from Windows Server 2008 R2 to supported Windows Server versions (e.g., 2019 or later) to benefit from ongoing security updates and improved security features. 7. Conduct regular vulnerability assessments and penetration tests focusing on legacy systems and RRAS configurations to identify and remediate exposures. 8. Employ network intrusion detection/prevention systems (IDS/IPS) tuned to detect anomalous RRAS traffic patterns.

Description

Exposure of sensitive information to an unauthorized actor in Windows Routing and Remote Access Service (RRAS) allows an unauthorized attacker to disclose information over a network.

Impact

For European organizations, the primary impact is the unauthorized disclosure of sensitive information, which could include network topology, routing details, or other configuration data that could facilitate further attacks such as network reconnaissance or targeted intrusions. Confidentiality breaches could compromise internal network security postures and expose sensitive operational data. Since Windows Server 2008 R2 is an older platform, many organizations in sectors like government, critical infrastructure, manufacturing, and finance may still operate legacy systems vulnerable to this issue. The lack of integrity or availability impact limits the immediate operational disruption, but the information disclosure could be leveraged by advanced persistent threat (APT) actors to plan more damaging attacks. The requirement for user interaction reduces the likelihood of automated widespread exploitation but does not eliminate risk, especially in environments where users initiate RRAS connections frequently. The absence of known exploits in the wild suggests limited current exploitation but also highlights the importance of proactive mitigation before attackers develop weaponized exploits. The medium severity rating indicates a moderate but non-trivial risk that should be addressed promptly, especially in regulated environments subject to data protection laws such as GDPR.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Feb 2026, 10:19 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats