# CVE-2026-76448: Cisco Identity Services Engine SQL Injection Vulnerability

> Authenticated attackers with admin credentials can execute arbitrary SQL queries to view or modify unauthorized data in Cisco ISE.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-m876-v9f2-m2w4

## What is CVE-2026-76448?

CVE-2026-76448 is a medium-severity SQL injection vulnerability in Cisco Identity Services Engine, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) could allow an authenticated, remote attacker to conduct an SQL or HQL injection attack on an affected device.

This vulnerability is due to insufficient validation of user-supplied input to the affected APIs before it is used to build database queries. An attacker could exploit this vulnerability by sending a crafted request to an affected device. A successful exploit could allow the attacker to execute arbitrary SQL or HQL queries against the underlying database, which could allow the attacker to view or modify data that they are not authorized to access. To exploit this vulnerability, the attacker must have valid administrative credentials.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-76448?

It affects 2 products.


Products: Cisco Identity Services Engine, Cisco Identity Services Engine Passive Identity Connector.

## How do I fix CVE-2026-76448?

No fix has been published for CVE-2026-76448 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76448 being exploited?

There is no known exploitation of CVE-2026-76448 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Identity Services Engine

- [CVE-2026-76460](https://insights.sbomify.com/CVE-2026-76460/): Cisco Identity Services Engine Incorrect Use of Privileged APIs (critical 10.0, exploited in the wild)
- [CVE-2025-20337](https://insights.sbomify.com/CVE-2025-20337/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2025-20281](https://insights.sbomify.com/CVE-2025-20281/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2026-20130](https://insights.sbomify.com/CVE-2026-20130/): Cisco Identity Services Engine Hardening Release - Improper Neutralization Vulnerabilities (critical 10.0)
- [CVE-2026-20192](https://insights.sbomify.com/CVE-2026-20192/): Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76448 and fix it if it is affected.

What it is: CVE-2026-76448 is a medium-severity SQL injection vulnerability in Cisco Identity Services Engine, published on 16 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76448 in the wild and no public exploit code.

Affected product: Cisco Identity Services Engine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76448/ (Markdown: https://insights.sbomify.com/CVE-2026-76448/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76448
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76448
- OSV: https://osv.dev/vulnerability/CVE-2026-76448

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76448/
Summaries are generated and may contain mistakes; the official description above is the record.