dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-26255

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.17763.5696 / 10.0.19044.4291 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows Remote Access Connection Manager Information Disclosure Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An information disclosure vulnerability exists in Windows Remote Access Connection Manager (RASCMAN). The vulnerability allows a local attacker to potentially access sensitive information through the Remote Access Connection Manager service. The CVSS 5.5 score indicates moderate severity with low attack complexity and local attack vector.

MitigationApply the Microsoft security update for CVE-2024-26255 through Windows Update or manual patch deployment to affected Windows systems running Remote Access Connection Manager.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1809Operating system
Affected:< 10.0.17763.5696
Windows 10 21h2Operating system
Affected:< 10.0.19044.4291
Windows 10 22h2Operating system
Affected:< 10.0.19045.4291
Windows 11 21h2Operating system
Affected:< 10.0.22000.2899
Windows 11 22h2Operating system
Affected:< 10.0.22621.3447
Windows 11 23h2Operating system
Affected:< 10.0.22631.3447
Windows Server 2019Operating system
Affected:< 10.0.17763.5696
Windows Server 2022Operating system
Affected:< 10.0.20348.2402

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the Windows version and build number
    Affected if The build number is lower than the version thresholds: 17763.5696 for Windows 10 1809/Server 2019, 19044.4291 for Windows 10 21h2, 19045.4291 for Windows 10 22h2, 22000.2899 for Windows 11 21h2, 22621.3447 for Windows 11 22h2, 22631.3447 for Windows 11 23h2, or 20348.2402 for Windows Server 2022
  2. Verify RASCMAN service presence
    Open Command Prompt or PowerShell and run 'Get-Service -Name RasMan' or 'sc query RasMan' to check if the Remote Access Connection Manager service exists on the system
    Affected if The RASCMAN service is present and running on a Windows version with a build number below the thresholds listed above
  3. Confirm exact OS build via PowerShell
    Run 'Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber' in PowerShell to retrieve the precise OS name and build number
    Affected if The OsBuildNumber value is less than the corresponding threshold for your specific Windows version

A system is affected if it runs any of the listed Windows versions with a build number below the specified threshold and has the RASCMAN service present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.17763.5696 / 10.0.19044.4291 / 10.0.19045.4291 or later
Fixed in 10.0.17763.569610.0.19044.429110.0.19045.4291
Interim mitigation

Apply the Microsoft security update for CVE-2024-26255 through Windows Update or manual patch deployment to affected Windows systems running Remote Access Connection Manager.

Recommended fix High confidence

Windows 10 1809/Server 2019: 10.0.17763.5696 | Windows 10 21h2: 10.0.19044.4291 | Windows 10 22h2: 10.0.19045.4291 | Windows 11 21h2: 10.0.22000.2899 | Windows 11 22h2: 10.0.22621.3447 | Windows 11 23h2: 10.0.22631.3447 | Windows Server 2022: 10.0.20348.2402

  1. Identify current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. For Windows 10 1809 and Windows Server 2019: Upgrade to version 10.0.17763.5696 or later
  3. For Windows 10 21h2: Upgrade to version 10.0.19044.4291 or later
  4. For Windows 10 22h2: Upgrade to version 10.0.19045.4291 or later
  5. For Windows 11 21h2: Upgrade to version 10.0.22000.2899 or later
  6. For Windows 11 22h2: Upgrade to version 10.0.22621.3447 or later
  7. For Windows 11 23h2: Upgrade to version 10.0.22631.3447 or later
  8. For Windows Server 2022: Upgrade to version 10.0.20348.2402 or later
Caveat Standard Windows security update risks - test in non-production environment before broad deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26255 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26255 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data