# CVE-2025-8095: Recoverable obfuscation using the OECH1 prefix encoding in OpenEdge

> Attackers can recover obfuscated data because the OECH1 encoding is cryptographically weak, requiring users to switch to supported symmetric encryption methods.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:U/AU:Y/V:D/RE:M/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-cghg-c2cv-qhxh

## What is CVE-2025-8095?

CVE-2025-8095 is a critical vulnerability in Progress Software Corporation OpenEdge, published on 14 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OECH1 prefix encoding is intended to obfuscate values across the OpenEdge platform.  It has been identified as cryptographically weak and unsuitable for stored encodings and enterprise applications.  OECH1 encodings should be considered exploitable and immediately replaced by any other supported prefix encoding, all of which are based on symmetric encryption.

Weakness: CWE-257 (Storing Passwords in a Recoverable Format)

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


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

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

## Is CVE-2025-8095 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8095 is a critical vulnerability in Progress Software Corporation OpenEdge, published on 14 Apr 2026. 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-8095 in the wild and no public exploit code.

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

## Sources

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

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