# CVE-2025-40585: Hardcoded credentials in Energy Services

> Attackers can use default credentials to gain control of the G5DFR component and tamper with device outputs in Siemens Energy Services.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 10 Jun 2025
- **Also known as:** GHSA-8rxv-vgf4-465c

## What is CVE-2025-40585?

CVE-2025-40585 is a critical vulnerability in Siemens Energy Services, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been identified in Energy Services (All versions with G5DFR). Affected solutions using G5DFR contain default credentials. This could allow an attacker to gain control of G5DFR component and tamper with outputs from the device.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2025-40585 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-40585 is a critical vulnerability in Siemens Energy Services, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40585 in the wild and no public exploit code.

Affected product: Siemens Energy Services. 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-40585/ (Markdown: https://insights.sbomify.com/CVE-2025-40585/index.md)
```

## Sources

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

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