CVE-2026-2999
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 · uneditedIDExpert Windows Logon Agent developed by Changing has a Remote Code Execution vulnerability, allowing unauthenticated remote attackers to force the system to download arbitrary executable files from a remote source and execute them.
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 · high confidenceThe IDExpert Windows Logon Agent contains an RCE vulnerability that allows unauthenticated remote attackers to force the application to download arbitrary executable files from a remote URL and execute them on the target system. This results in complete compromise of the affected machine.
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>= 2.7.3.230719, <= 2.8.4.250925CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if IDExpert Windows Logon Agent is installedCheck for the presence of IDExpert installation directory (typically in Program Files or Program Files (x86)) or look for service named 'IDExpert' or 'IdexpertLogonAgent' in Windows Services (services.msc)Affected if The application is installed and the service exists on the system
-
Check installed version of IDExpertOpen Windows Registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{ProductGUID} or look in Add/Remove Programs for the version, or check the version property of the executable in the installation folderAffected if The installed version falls within >= 2.7.3.230719 and <= 2.8.4.250925
-
Verify if the logon agent service is runningOpen services.msc and look for IDExpert-related service, or run 'sc query' for IDExpert services to determine if the vulnerable component is activeAffected if The IDExpert logon agent service is currently running
-
Check network exposure of the serviceUse 'netstat -an' or Windows Firewall with Advanced Security inbound rules to determine if the IDExpert service port (commonly TCP 8080 or configured port) is listening on external interfaces or is accessible from non-localhost addressesAffected if The service is listening on 0.0.0.0 or an external IP address rather than only 127.0.0.1 localhost
If IDExpert Windows Logon Agent is installed with a version between 2.7.3.230719 and 2.8.4.250925 and the service is running and network-accessible, the system is affected by this unauthenticated RCE vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply vendor-supplied patches or updates for IDExpert Windows Logon Agent immediately. Until patched, network segmentation and restricting outbound connections from affected systems may reduce exposure.
- 1. Identify the current version of IDExpert Windows Logon Agent installed on the system
- 2. Navigate to the vendor patch page at https://www.changingtec.com/news_detail.jsp?item_id=348 to obtain the vendor-provided patch or fixed version information
- 3. Apply the vendor patch or upgrade to the fixed version as specified by Changing in the security advisory
- 4. Verify that the patch/upgrade was successfully applied by checking the IDExpert version
- 5. Test that the RCE vulnerability is no longer exploitable - the system should no longer download and execute arbitrary files from remote sources without validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2999 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2999 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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