CVE-2026-92625 Control iD CVE debrief

Who should care

Defenders responsible for systems using iDSecure versions prior to 4.8.3.0 should assess exposure and potential impact, and prioritize verifying and mitigating this vulnerability. This includes reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Why it matters

CVE-2026-92625 is a high-severity vulnerability affecting Control iD iDSecure, allowing unauthenticated Denial of Service attacks. Defenders should prioritize verifying exposure and assessing potential impact, focusing on systems using iDSecure versions prior to 4.8.3.0.

• Potential Denial of Service attacks
• Service unavailability due to continuous restart cycle
• Need for verification of iDSecure version and exposure
• Potential impact on system availability and reliability

Technical summary

The /api/license/restartService endpoint in Control iD iDSecure versions prior to 4.8.3.0 is vulnerable to unauthenticated Denial of Service attacks, allowing attackers to terminate and restart the iDSecure service process. This can be done by repeatedly calling the endpoint, causing a continuous restart cycle that renders the service unavailable. The vulnerability has a CVSS score of 7.5 and is classified as HIGH severity. Defenders should prioritize verifying exposure and assessing potential impact, focusing on systems using iDSecure versions prior to 4.8.3.0.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact, focusing on systems using iDSecure versions prior to 4.8.3.0.

Recommended defensive actions

• Verify iDSecure version and assess exposure
• Implement authentication for the /api/license/restartService endpoint
• Monitor for potential Denial of Service attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 7.5 and HIGH severity. A source reference from Tenable is also available. The vulnerability affects Control iD iDSecure versions prior to 4.8.3.0 and can be exploited via the /api/license/restartService endpoint. Defenders should verify exposure and assess potential impact.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.