# CVE-2025-11906: Privilege escalation via writable configuration files in Progress Flowmon

> A local attacker with SSH access can escalate privileges to root due to incorrect file permissions on system configuration files.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-g429-pfpf-366c

## What is CVE-2025-11906?

CVE-2025-11906 is a medium-severity vulnerability in Progress Software Flowmon, published on 30 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability exists in Progress Flowmon versions prior 12.5.6 where certain system configuration files have incorrect file permissions, allowing a user with access to the default flowmon system user account used for SSH access to potentially escalate privileges to root during service initialization.

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

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


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

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

## Is CVE-2025-11906 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11906 is a medium-severity vulnerability in Progress Software Flowmon, published on 30 Oct 2025. 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-2025-11906 in the wild and no public exploit code.

Affected product: Progress Software Flowmon. 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-11906/ (Markdown: https://insights.sbomify.com/CVE-2025-11906/index.md)
```

## Sources

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

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