# CVE-2025-56266: Other in n/a

> Attackers can execute arbitrary code in Avigilon ACM by exploiting a Host Header Injection vulnerability via crafted URLs.

- **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:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-3664-c5jc-w4rv

## What is CVE-2025-56266?

CVE-2025-56266 is a critical vulnerability in n/a, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Host Header Injection vulnerability in Avigilon ACM v7.10.0.20 allows attackers to execute arbitrary code via supplying a crafted URL.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-444 (Inconsistent Interpretation of HTTP Requests), CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2025-56266?

It affects 1 product.


Products: Avigilon Access Control Manager.

## How do I fix CVE-2025-56266?

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

## Is CVE-2025-56266 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56266 exists.

Public exploit code:

- Avigilon ACM - Host Header Injection (nuclei): http/cves/2025/CVE-2025-56266.yaml

## Other vulnerabilities in n/a

- [CVE-2025-56267](https://insights.sbomify.com/CVE-2025-56267/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56266 and fix it if it is affected.

What it is: CVE-2025-56266 is a critical vulnerability in n/a, published on 8 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56266 exists.

Affected product: n/a. 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-2025-56266/ (Markdown: https://insights.sbomify.com/CVE-2025-56266/index.md)
```

## Sources

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

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