# CVE-2026-25112: Privilege escalation in Genetec Airport Operational Manager

> Attackers can escalate privileges due to insecure permissions in the Genetec RabbitMQ deployment configuration.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 9 Jun 2026
- **Also known as:** GHSA-7vxw-69v7-42x7

## What is CVE-2026-25112?

CVE-2026-25112 is a high-severity vulnerability in Genetec Airport Operational Manager, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A high-severity vulnerability in the deployment of Genetec RabbitMQ that allows a privilege escalation attack.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2026-25112 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25112 is a high-severity vulnerability in Genetec Airport Operational Manager, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25112 in the wild and no public exploit code.

Affected product: Genetec Airport Operational Manager. 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-25112/ (Markdown: https://insights.sbomify.com/CVE-2026-25112/index.md)
```

## Sources

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

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