⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.8

How to Fix CVE-2026-8992: Authentication Bypass in Secure Access Client

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 8.8 - High
Actively exploited?Not currently listed in CISA KEV
AffectedSecure Access Client before 22.8R6
Fixed in22.8R6
Type (CWE)CWE-295: Improper certificate validation

What is CVE-2026-8992?

CVE-2026-8992 is an authentication bypass in Secure Access Client. A flaw in the authentication or session-handling logic lets a remote attacker reach administrative functions without valid credentials. In several reported cases this leads directly to remote code execution. Vendor description: An improper certificate validation vulnerability in Ivanti Secure Access Client before 22.8R6 allows a remote unauthenticated attacker to execute arbitrary code.

Why this CVE matters

Authentication bypass on a network appliance or admin console is a top-tier target. Once the attacker is past the login, every administrative endpoint becomes available, including the ones that change settings, upload firmware, or run shell commands.

For deployments of Secure Access Client that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

Check your installed Secure Access Client version against the affected ranges in the vendor advisory linked below. If you cannot determine the version, treat the system as potentially affected and apply the patched build.

Open the Ivanti product's About page in the admin UI or run the documented version-check command from the vendor's release notes. Cross-reference the build number against the advisory.

How to fix CVE-2026-8992

  1. Read the vendor advisory in full: https://hub.ivanti.com/s/article/May-2026-Security-Advisory-Ivanti-Secure-Access-Client-CVE-2026-7431-CVE-2026-7432?language=en_US
  2. Upgrade Secure Access Client to 22.8R6 or a later version listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Rotate any credentials, API keys, or session tokens that the vulnerable service touched. An unauthenticated RCE-class flaw means anything the process could see should be treated as exposed.
  5. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  6. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Network appliance upgrade

The vendor advisory (https://hub.ivanti.com/s/article/May-2026-Security-Advisory-Ivanti-Secure-Access-Client-CVE-2026-7431-CVE-2026-7432?language=en_US) names the patched build as Secure Access Client 22.8R6.


# 1. Confirm the running firmware
show version

# 2. Download the patched image from the vendor support portal; verify SHA256.
sha256sum secure-access-client-patched.img

# 3. Apply via vendor upgrade procedure (TFTP, SCP, USB, or web GUI).
# 4. Reboot, then re-run the version command to confirm the patched build loaded.

Verify the fix landed


# Vendor advisory: https://hub.ivanti.com/s/article/May-2026-Security-Advisory-Ivanti-Secure-Access-Client-CVE-2026-7431-CVE-2026-7432?language=en_US
# 1. Compare the running version against the fixed build named above.
#    (Replace the version probe with the platform-specific command from the block above.)

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag this CVE on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you cannot patch immediately

Restrict access to the affected administrative interface to trusted internal networks. Disable the vulnerable component if the vendor documents that as an interim option. Patch immediately when feasible.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in Secure Access Client, scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-8992 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-8992?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Do I need to assume compromise if my Secure Access Client was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*