
Verified security news
CISA added CVE-2026-111357 (Ivanti Connect Secure) to its Known Exploited Vulnerabilities catalog on 2026-10-30. This is the catalog-addition date, not necessarily the vulnerability's discovery or disclosure date.
CISA's description: Ivanti Connect Secure contains a missing authentication for critical function vulnerability that could allow a local authenticated attacker to escalate their privileges. This vulnerability can be chained with CVE-2026-104935 and CVE-2026-118527.
CISA's listed action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA lists use in ransomware campaigns as Unknown. "Unknown" does not mean ransomware use is ruled out. Catalog deadlines apply to the entities covered by the relevant federal directive; they are not universal legal obligations.
Source: CISA Known Exploited Vulnerabilities catalog — CVE-2026-111357 (added 2026-10-30; checked 2026-11-02).
Recommendations, not reported incident facts
The guidance below explains general risk-reduction steps. It does not establish that your organization is affected or that NativeCyber has prevented this specific attack. Verify affected versions and applicable updates in the official advisory before making changes.
Hypothetical workplace scenario: an IT team at a regional enterprise keeps a remote access appliance in place because it still supports shift workers, field staff, and a few vendors. The business has already removed most former employees from the HR system, but a couple of accounts, shared VPN groups, and old admin permissions were never fully reviewed. That setup matters because a missing-authentication-for-critical-function flaw in a remote access product can become much more dangerous when any valid account, even a low-privilege one, is still active. The main lesson is simple: identity cleanup and access review are part of vulnerability defense, not a separate task.
Why this vulnerability matters operationally
The verified issue in Ivanti Connect Secure is a privilege-escalation weakness that requires a local authenticated attacker. That means the problem is not only whether the software is present, but whether the organization has strong control over who can authenticate and what happens after login. If a former employee, contractor, or over-privileged service account still has access, an attacker may have a better path to abuse the appliance and move toward broader internal systems. For enterprise operations, that can affect remote work, support access, file systems, and other services that depend on the gateway as a trusted entry point.
The identity angle: former employees are not just HR records
A common mistake is treating offboarding as complete once email is disabled. Remote access environments need a second look. Accounts tied to VPN, single sign-on, admin consoles, break-glass procedures, and shared support groups can linger after the person leaves. In a hypothetical help desk scenario, a former contractor still has access to a privileged support group because the account was never removed from the appliance, even though the badge was turned in months ago. That kind of stale access turns a software flaw into an access-control problem. The safe assumption is that every unused account, stale group, and forgotten token should be reviewed as if it were a live pathway.
What to do first: reduce who can reach the appliance
Start with access reduction, because fewer valid accounts means fewer chances to abuse any authenticated weakness. Confirm that all former employee and former contractor accounts are disabled everywhere the appliance trusts identity, not just in HR or the directory. Review privileged roles and remove any account that does not truly need administrative or support rights. Check whether shared admin credentials, emergency accounts, or dormant vendor access are still active. If the appliance can be restricted to only approved source networks, do that. If remote access is only needed for specific groups, segment those users rather than exposing the whole organization to the same path.
What to do next: verify mitigation and logging ownership
The source requires applying vendor mitigations and following CISA guidance such as BOD 26-04 and forensics triage requirements where applicable. For an organization, that translates into clear ownership: the network or platform team should confirm the appliance version, the security team should validate whether mitigations are in place, and the identity team should verify account removal and role changes. Logging matters too. Make sure authentication logs, admin actions, and unusual privilege changes are being collected and reviewed. If a suspicious login occurs, the team should know who will isolate the appliance, preserve logs, and decide whether to move to incident response. That planning is important because a privilege-escalation flaw can become an internal access crisis fast.
What good defensive practice looks like in a real shop
In a hypothetical mid-size organization, the best response is a short joint review between identity, network, and security operations. They should compare the list of active remote access users against current staff and contractor records, then remove anything stale. They should verify whether the appliance is internet-exposed, whether compensating controls exist, and whether the risk changes if mitigation is not available. They should also test whether new admin access requires approval and whether former staff are removed from every trust relationship the appliance uses. This is not about perfection. It is about making sure a local authenticated flaw cannot be paired with forgotten access and weak oversight to create a wider breach path.
A practical checklist
- Confirm all former employee, contractor, and vendor accounts tied to the appliance are disabled or removed.
- Review privileged groups, admin roles, and break-glass accounts for unnecessary access.
- Verify vendor mitigations are applied and documented by the platform or network owner.
- Check whether the appliance is exposed to the internet and limit access where possible.
- Collect and review authentication and admin logs for unusual login or privilege activity.
- Assign one owner for identity cleanup, one for appliance mitigation, and one for incident response triage.
How NativeCyber can help
Explore NativeCyber's identity security services or request a consultation to discuss your organization's priorities.
Further reading
Prepared with AI assistance for NativeCyber. This article provides general educational guidance, not a security assessment or legal advice.
Free weekly newsletter
Indian Country Cyber Brief
The security stories that matter for tribal IT, and what to do Monday.
About the newsletter
