Evidence used
- CISA confirms exploitation in the wild.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-104935High confidence
Ivanti Connect Secure Authentication Bypass by Spoofing Vulnerability
Ivanti · Connect Secure
8.6HighCVSS 3.1
Patch now
Patch availableCISA confirms exploitation in the wild and lists 2026-10-16 as the remediation due date.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:Critical, raised one band.upgradedsince 13 Oct 2026
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Increase monitoring for the attack path and post-exploitation behaviour described in the report.
Verification
- Confirm that the asset runs Ivanti Connect Secure and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
CISA confirms exploitation in the wild and lists 2026-10-16 as the remediation due date.
Patch available01
What, why and how
Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands.
What
Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands.
Why
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands.
Why
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation Confirmed in the wild
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-10-13.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Authentication Bypass by Spoofing → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-290 ↗
CWE-290: Authentication Bypass by Spoofing. This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:LCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 13 Oct 2026 · Last source change 13 Oct 2026, 19:58 UTC · CWE-290 · Authentication Bypass by Spoofing
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source Unavailable
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceNo official EUVD mapping
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched
Missing structured fields: affected versions. Missing data is not evidence of low risk; review the primary advisory.
Material change intelligence
View recent updates ↗What changed after publication
- BlackTree coverageBlackTree article coverage changed from no BlackTree article to 1 BlackTree article.BlackTree editorial ↗
- Before
- no BlackTree article
- After
- 1 BlackTree article
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: hub.ivanti.com/Security-Advisory-Ivanti-Connect-Secure-CVE-2026-104935.hub.ivanti.com ↗
- Before
- remediation: hub.ivanti.com/Security-Advisory-Ivanti-Connect-Secure-CVE-2026-104935
- After
- remediation: hub.ivanti.com/Security-Advisory-Ivanti-Connect-Secure-CVE-2026-104935 · vendor advisory: hub.ivanti.com/Security-Advisory-Ivanti-Connect-Secure-CVE-2026-104935
- Vendor guidanceAuthoritative vendor guidance changed: added remediation: hub.ivanti.com/Security-Advisory-Ivanti-Connect-Secure-CVE-2026-104935.CNA ↗
- Before
- no authoritative guidance recorded
- After
- remediation: hub.ivanti.com/Security-Advisory-Ivanti-Connect-Secure-CVE-2026-104935
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- No structured affected-product or version range is currently available from the CVE record or NVD. · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- See the vendor and CVE records for the affected range. · Fixed: Connect Secure: 25.1.3.0, 25.1.3.1, 22.8R2.5, 22.7R2.14
- Remediation statusRemediation status changed from Awaiting fix to Patch available.CNA ↗
- Before
- Awaiting fix
- After
- Patch available
- SeveritySeverity changed from Unknown to High.CNA ↗
- Before
- Unknown
- After
- High
- CVSS scoreCVSS score changed from not recorded to 8.6 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L).CNA ↗
- Before
- not recorded
- After
- 8.6 (CVSS 3.1 · CNA · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L)
- Catalogue recordCVE added to the BlackTree catalogue.CISA KEV ↗
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.