# CVE-2025-9038: S1 Agile Privilege Escalation

> An attacker can escalate privileges on Windows systems running GE Vernova S1 Agile Configuration Software due to improper privilege management.

- **Severity:** High 7.5 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/S:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2025
- **Updated:** 24 Sep 2025
- **Also known as:** GHSA-qv9v-x5p8-5h5p

## What is CVE-2025-9038?

CVE-2025-9038 is a high-severity vulnerability in GE Vernova S1 Agile Configuration Software, published on 22 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Privilege Management vulnerability in GE Vernova S1 Agile Configuration Software on Windows allows Privilege Escalation.This issue affects S1 Agile Configuration Software: 3.1 and previous version.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2025-9038 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9038 is a high-severity vulnerability in GE Vernova S1 Agile Configuration Software, published on 22 Sep 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-9038 in the wild and no public exploit code.

Affected product: GE Vernova S1 Agile Configuration Software. 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-9038/ (Markdown: https://insights.sbomify.com/CVE-2025-9038/index.md)
```

## Sources

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

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