cve.bz

CVE-2026-20195 cisco identity services engine: Observable Response Discrepancy

5.3 mediumEPSS 0.3%

Medium (5.3) in cisco identity services engine. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability in an identity management API endpoint of Cisco ISE could allow an unauthenticated, remote attacker to enumerate valid user accounts on an affected device. This vulnerability exists because error messages are observed when the affected API endpoint is called. An attacker could exploit this vulnerability by sending a series of crafted requests to the affected endpoint and analyzing the differentiated responses. A successful exploit could allow the attacker to compile a list of valid usernames on an affected system.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-05-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-204 Observable Response Discrepancy
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-20195 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-20195?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-20195?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-20195 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-20195

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-20195](https://cve.bz/cve/badge/CVE-2026-20195.svg)](https://cve.bz/cve/CVE-2026-20195)

HTML:

<a href="https://cve.bz/cve/CVE-2026-20195"><img src="https://cve.bz/cve/badge/CVE-2026-20195.svg" alt="CVE-2026-20195"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cisco:identity_services_enginethrough 3.2.0
cisco:identity_services_engine3.3.0
cisco:identity_services_engine3.3.0:patch1
cisco:identity_services_engine3.3.0:patch10
cisco:identity_services_engine3.3.0:patch2
cisco:identity_services_engine3.3.0:patch3
cisco:identity_services_engine3.3.0:patch4
cisco:identity_services_engine3.3.0:patch5
cisco:identity_services_engine3.3.0:patch6
cisco:identity_services_engine3.3.0:patch7
cisco:identity_services_engine3.3.0:patch8
cisco:identity_services_engine3.3.0:patch9
cisco:identity_services_engine3.4.0
cisco:identity_services_engine3.4.0:patch1
cisco:identity_services_engine3.4.0:patch2
cisco:identity_services_engine3.4.0:patch3
cisco:identity_services_engine3.4.0:patch4
cisco:identity_services_engine3.4.0:patch5
cisco:identity_services_engine3.5.0
cisco:identity_services_engine3.5.0:patch1
cisco:identity_services_engine3.5.0:patch2

Attack patterns (CAPEC)

  • CAPEC-331 ICMP IP Total Length Field Probe Likelihood: Medium · Severity: Low
  • CAPEC-332 ICMP IP 'ID' Field Error Message Probe Likelihood: Medium · Severity: Low
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON