# CVE-2026-12164: Privilege Escalation in Fortra File Integrity Monitoring (FIM)


- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-3x8g-cjc2-45qp

## What is CVE-2026-12164?

CVE-2026-12164 is a medium-severity vulnerability in Fortra File Integrity Monitoring (FIM), published on 23 Jun 2026. 

### Official description

Fortra File Integrity Monitoring (FIM), formerly Tripwire Enterprise, versions prior to 9.4.0 may assign incorrect or elevated effective permissions to users created by the tetool import command while FIM is running, particularly when the import also creates or changes roles or role-permission relationships.

Weakness: CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Fortra File Integrity Monitoring.

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

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

## Is CVE-2026-12164 being exploited?

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

## Other vulnerabilities in Fortra File Integrity Monitoring (FIM)

- [CVE-2026-12163](https://insights.sbomify.com/CVE-2026-12163/): Stored XSS in Fortra File Integrity Monitoring (FIM) (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12164 is a medium-severity vulnerability in Fortra File Integrity Monitoring (FIM), published on 23 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-12164 in the wild and no public exploit code.

Affected product: Fortra File Integrity Monitoring (FIM). 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-12164/ (Markdown: https://insights.sbomify.com/CVE-2026-12164/index.md)
```

## Sources

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

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