CVE-2026-76427 Vulnerability Analysis & Exploit Details

CVE-2026-76427
Vulnerability Scoring

4.9
/10
Medium Risk

The vulnerability CVE-2026-76427 could compromise system integrity but typically requires user interaction to be exploited.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-76427 Details

Status: Analyzed

Last updated: 🕐 28 Sep 2026, 13:01 UTC
Originally published on: 🕘 16 Sep 2026, 21:17 UTC

Time between publication and last update: 11 days

CVSS Release: version 3

CVSS3 Source

psirt@cisco.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

CVE-2026-76427 Vulnerability Summary

CVE-2026-76427: A vulnerability in the offline profiler feed service of Cisco ISE could allow an authenticated, remote attacker to read arbitrary files that are stored on an affected device. This vulnerability is due to the parsing of attacker-controlled feed metadata with an XML parser that does not disable external entity resolution. An attacker could exploit this vulnerability by uploading a crafted offline feed package through the administrative interface. A successful exploit could allow the attacker to read arbitrary files from the file system and issue requests to internal systems from the affected device. To exploit this vulnerability, the attacker must have valid administrative credentials.

Assessing the Risk of CVE-2026-76427

Access Complexity Graph

The exploitability of CVE-2026-76427 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-76427

The exploitability of CVE-2026-76427 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-76427, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-76427, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-76427 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-76427 poses no threat to data integrity.
  • Availability: None
    CVE-2026-76427 does not impact system availability.

CVE-2026-76427 References

External References

CWE Common Weakness Enumeration

CWE-611

CAPEC Common Attack Pattern Enumeration and Classification

  • Data Serialization External Entities Blowup CAPEC-221 This attack takes advantage of the entity replacement property of certain data serialization languages (e.g., XML, YAML, etc.) where the value of the replacement is a URI. A well-crafted file could have the entity refer to a URI that consumes a large amount of resources to create a denial of service condition. This can cause the system to either freeze, crash, or execute arbitrary code depending on the URI.

Vulnerable Configurations

  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1\(0.440\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1\(0.440\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1\(0.518\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1\(0.518\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:003.001\(000.518\):-:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:003.001\(000.518\):-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch1:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch10:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch10:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch2:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch3:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch4:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch5:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch5:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch6:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch6:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch7:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch7:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch8:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch8:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch9:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1.0:patch9:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1:patch1:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1:patch1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1:patch2:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1:patch2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1:patch3:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1:patch3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1:patch4:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1:patch4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1:patch5:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1:patch5:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1:patch6:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1:patch6:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.1:patch7:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.1:patch7:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:003.002\(000.116\):-:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:003.002\(000.116\):-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2\(0.149\):*:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2\(0.149\):*:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch1:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch10:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch10:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch11:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch11:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch2:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch3:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch4:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch5:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch5:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch6:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch6:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch7:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch7:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch8:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch8:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch9:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2.0:patch9:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2:patch1:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2:patch1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2:patch2:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2:patch2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2:patch3:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2:patch3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.2:patch4:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.2:patch4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch1:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch10:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch10:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch11:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch11:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch2:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch3:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch4:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch5:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch5:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch6:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch6:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch7:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch7:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch8:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch8:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch9:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.3.0:patch9:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.4.0:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.4.0:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch1:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch2:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch3:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch3:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch4:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch4:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch5:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch5:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch6:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.4.0:patch6:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.5.0:-:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.5.0:-:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.5.0:patch1:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.5.0:patch1:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.5.0:patch2:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.5.0:patch2:*:*:*:*:*:*
  • cpe:2.3:a:cisco:identity_services_engine:3.5.0:patch3:*:*:*:*:*:*
    cpe:2.3:a:cisco:identity_services_engine:3.5.0:patch3:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-76427: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-96294 – Uncaught exception, Improper Handling of Exceptional Conditions vulnerability in Apache Thrift NodeJS bindings. This issue affects Apache Thrift...
  • CVE-2026-96292 – Inefficient regular expression complexity, Inefficient Algorithmic Complexity vulnerability in Apache Thrift Lua bindings. This issue affects Ap...
  • CVE-2026-96288 – Uncontrolled Recursion, Allocation of resources without limits or throttling vulnerability in Apache Thrift Erlang bindings. This issue affects ...
  • CVE-2026-94653 – Inefficient Algorithmic Complexity vulnerability in Apache Thrift PHP bindings. This issue affects Apache Thrift: before 0.25.0. Users are re...
  • CVE-2026-94652 – Missing release of memory after effective lifetime vulnerability in Apache Thrift c++ bindings. This issue affects Apache Thrift: before 0.25.0....