Ivanti Sentry up to R10.5.1/R10.6.1/R10.7.0 authentication bypass
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.1 | $0-$5k | 5.14 |
Summary
A vulnerability has been found in Ivanti Sentry up to R10.5.1/R10.6.1/R10.7.0 and classified as critical. Impacted is an unknown function. Performing a manipulation results in authentication bypass. This vulnerability is identified as CVE-2026-10523. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, was found in Ivanti Sentry up to R10.5.1/R10.6.1/R10.7.0. This affects an unknown part. The manipulation with an unknown input leads to a authentication bypass vulnerability. CWE is classifying the issue as CWE-288. A product requires authentication, but the product has an alternate path or channel that does not require authentication. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An Authentication Bypass vulnerability (CWE-288) in Ivanti Sentry before the R10.5.2, R10.6.2 and R10.7.1 versions allows a remote unauthenticated attacker to create arbitrary administrative accounts and obtain full administrative access
The advisory is shared at hub.ivanti.com. This vulnerability is uniquely identified as CVE-2026-10523 since 06/01/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version R10.5.2, R10.6.2 or R10.7.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.4VulDB Meta Temp Score: 9.1
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.9
CNA Vector (ivanti): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Authentication bypassCWE: CWE-288 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Sentry R10.5.2/R10.6.2/R10.7.1
Timeline
06/01/2026 CVE reserved06/09/2026 Advisory disclosed
06/09/2026 VulDB entry created
06/09/2026 VulDB entry last update
Sources
Advisory: hub.ivanti.comStatus: Confirmed
CVE: CVE-2026-10523 (🔒)
GCVE (CVE): GCVE-0-2026-10523
GCVE (VulDB): GCVE-100-369561
Entry
Created: 06/09/2026 17:43Changes: 06/09/2026 17:43 (63)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.