High Access control

CVE-2025-55148 — Missing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure...

Missing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6, Ivanti ZTA Gateway before 2.8R2.3-723 and Ivanti Neurons for Secure Access before 22.8R1.4 (Fix deployed on 02-Aug-2025) allows a remote authenticated attacker with read-only admin privileges to configure restricted settings.

Published Sep 9, 2025 · Updated Oct 18, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: ivanti

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.6% (30-day exploitation probability)+7
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.57%

ahead of 46% of scored CVEs · Oct 18, 2026

Affects

Ivanti

Connect Secure and 4 more

CVSS base

7.6

High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Ivanti Connect Secure, Ivanti Neurons For Secure Access, Ivanti Policy Secure…).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Ivanti	Connect Secure	version 22.7version 22.7-r2.8version 22.7-r2.7version 22.7-r2.6version 22.7-r2.5version 22.7-r2.4version 22.7-r2.3version 22.7-r2.2 and 9 more version 22.7-r2version 22.7-r2.1< 22.7version 22.7-r1version 22.7-r1.1version 22.7-r1.2version 22.7-r1.3version 22.7-r1.4version 22.7-r1.5	Vulnerable	NIST National Vulnerability Database
Ivanti	Connect Secure	versions not specified by the source	Vulnerable	CVE Program (cve.org) e CISA ADP
Ivanti	Neurons For Secure Access	versions not specified by the source	Vulnerable	CVE Program (cve.org) e CISA ADP
Ivanti	Neurons For Secure Access	version 22.8-r1.3version 22.8-r1.2version 22.8-r1.1version 22.8-r1< 22.8	Vulnerable	NIST National Vulnerability Database
Ivanti	Policy Secure	version 22.7-r1.2version 22.7-r1.5version 22.7-r1.4version 22.7-r1.3version 22.7-r1.1version 22.7-r1version 22.7< 22.7	Vulnerable	NIST National Vulnerability Database
Ivanti	Policy Secure	versions not specified by the source	Vulnerable	CVE Program (cve.org) e CISA ADP
Ivanti	Zero Trust Access Gateway	version 22.8-r2.2	Vulnerable	NIST National Vulnerability Database
Ivanti	ZTA Gateway	versions not specified by the source	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
7.6	CVSS 3.1	High	2.8	4.7	3c1d8aa1-5a33-4ea4-8992-aadd6440af75 via NIST National Vulnerability Database
7.6	CVSS 3.1	High	—	—	GitHub, Inc. via GitHub Security Advisories
7.6	CVSS 3.1	High	—	—	ivanti via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H (score shown at the top: 3c1d8aa1-5a33-4ea4-8992-aadd6440af75)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-862 · Missing Authorization

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Audit administrative actions and access to resources outside each user’s normal pattern.

web/proxy/WAF logsnetwork IDS/IPSauthentication logsapplication logs

Timeline

What happened to this CVE, newest first.

2026
Affected products added · ivanti/connect secure, ivanti/policy secure, ivanti/zta gateway, ivanti/neurons for secure access
Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 18, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 18, 2026
Affected products added · ivanti/connect secure, ivanti/policy secure, ivanti/zero trust access gateway, ivanti/neurons for secure access
Oct 18, 2026 · NIST National Vulnerability Database
CVSS changed · 7.6
Oct 18, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 18, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 18, 2026 · Alertas do Telegram
2025
CVE published
Sep 9, 2025 · ivanti

Source activity

Repeated readings are counted rather than listed.

2× References added · Oct 18, 2026 – Oct 18, 2026
1× Official description updated · Oct 18, 2026 – Oct 18, 2026

References

3 on the record

forums.ivanti.com/s/article/September-Security-Advisory-Ivanti-Connect-Secure-Policy-Se
Vendor Advisory, NIST National Vulnerability Database
github.com/advisories/GHSA-9vj6-36jx-c7r8
GitHub Security Advisories
nvd.nist.gov/vuln/detail/CVE-2025-55148
GitHub Security Advisories

Elsewhere on this site

Ivanti
every CVE for this vendor

Access control
same class

CWE-862
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-111357 Ivanti Connect Secure 22.8R2.4 mishandles the manner in which the dsinvoked broker trusts DSCache... 4d
High CVE-2026-104935 Ivanti Connect Secure Authentication Bypass by Spoofing Vulnerability KEV 6d
High CVE-2025-55147 CSRF in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6,... Sep 9, 2025
Medium CVE-2025-8711 CSRF in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure before 22.7R1.6,... Sep 9, 2025
Medium CVE-2025-8712 Missing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure... Sep 9, 2025
Medium CVE-2025-55143 Reflected text injection in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure... Sep 9, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-55148 is "Missing authorization in Ivanti Connect Secure before 22.7R2.9 or 22.8R2, Ivanti Policy Secure...", rated High. It affects Connect Secure (Ivanti); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.6 describes technical severity. EPSS 0.57% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.