# CVE-2025-56577: Hardcoded credentials in n/a

> A local attacker can obtain sensitive information from Evope Core due to the presence of hard coded cryptographic keys.

- **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:** 29 Aug 2025
- **Updated:** 29 Aug 2025
- **Also known as:** GHSA-7hr9-c7mv-j423

## What is CVE-2025-56577?

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

### Official description

An issue in Evope Core v.1.1.3.20 allows a local attacker to obtain sensitive information via the use of hard coded cryptographic keys.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 1 product.


Products: Evope Evope Core.

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

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

## Is CVE-2025-56577 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56577 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56577 is a high-severity vulnerability in n/a, published on 29 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56577 exists.

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

## Sources

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

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