# CVE-2025-27997: Privilege escalation in n/a

> Attackers can escalate privileges by placing malicious scripts in the ProgramData directory, affecting Battle.net client users.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2025
- **Updated:** 21 May 2025
- **Also known as:** GHSA-9mgg-ww23-jfhc

## What is CVE-2025-27997?

CVE-2025-27997 is a high-severity vulnerability in n/a, published on 21 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue in Blizzard Battle.net v2.40.0.15267 allows attackers to escalate privileges via placing a crafted shell script or executable into the C:\ProgramData directory.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Blizzard Battle.net.

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

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

## Is CVE-2025-27997 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-27383](https://insights.sbomify.com/CVE-2020-27383/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27997 is a high-severity vulnerability in n/a, published on 21 May 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-27997 in the wild and no public exploit code.

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-27997/ (Markdown: https://insights.sbomify.com/CVE-2025-27997/index.md)
```

## Sources

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

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