# CVE-2026-76461: Cisco Secure Email Gateway SQL Injection

> Unauthenticated remote attackers can execute arbitrary commands with root privileges via crafted emails due to SQL injection in email parsing.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 14 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-jwpf-jww6-h6vr

## What is CVE-2026-76461?

CVE-2026-76461 is a critical SQL injection vulnerability in Cisco Asyncos, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the email parsing of Cisco AsyncOS Software for Cisco Secure Email Gateway could allow an unauthenticated, remote attacker to execute arbitrary commands with root privileges on the underlying operating system.

This vulnerability is due to insufficient validation in the email parsing logic. An attacker could exploit this vulnerability by sending a crafted email message that contains malicious SQL statements through an affected device. A successful exploit could allow the attacker to execute arbitrary SQL statements, leading to command execution with root privileges on the underlying operating system.

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

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

It affects 1 product.


Products: Cisco Asyncos.

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

No fix has been published for CVE-2026-76461 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Sep 2026.

## Is CVE-2026-76461 being exploited?

Yes. Attackers have exploited CVE-2026-76461 in the wild since at least 14 Sep 2026.

Public exploit code:

- CVE-2026-76461 (github_poc): https://github.com/0xredash/CVE-2026-76461
- CVE-2026-76461 (github_poc): https://github.com/S3v3n-JG/CVE-2026-76461
- CVE-2026-76461 - Draft or TODO (github_poc): https://github.com/HORKimhab/CVE-2026-76461
- https://github.com/fevar54/CVE-2026-76461-Detection-Kit- (github_poc): https://github.com/fevar54/CVE-2026-76461-Detection-Kit-

## Other vulnerabilities in Cisco Asyncos

- [CVE-2025-20393](https://insights.sbomify.com/CVE-2025-20393/): Cisco Multiple Products Improper Input Validation (critical 10.0, exploited in the wild)
- [CVE-2026-76519](https://insights.sbomify.com/CVE-2026-76519/): Cisco Secure Email Gateway Relative Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2024-20435](https://insights.sbomify.com/CVE-2024-20435/): Command injection in Cisco Secure Web Appliance (high 8.8)
- [CVE-2019-15956](https://insights.sbomify.com/CVE-2019-15956/): Cisco Web Security Appliance Unauthorized Device Reset Vulnerability (high 8.8)
- [CVE-2021-34698](https://insights.sbomify.com/CVE-2021-34698/): Cisco Web Security Appliance Proxy Service Denial of Service Vulnerability (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76461 is a critical SQL injection vulnerability in Cisco Asyncos, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-76461 in the wild since at least 14 Sep 2026.

Affected product: Cisco Asyncos. 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-76461/ (Markdown: https://insights.sbomify.com/CVE-2026-76461/index.md)
```

## Sources

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

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