CVE-2025-8095

Recoverable obfuscation using the OECH1 prefix encoding in OpenEdge

Published Apr 14, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability arises from the OECH1 prefix encoding, designed for obfuscation but found to be cryptographically weak. Because of this weakness, any values encoded with OECH1—including credentials and secrets—can be retrieved by attackers who can analyze the encoded data. This can lead to exposure of sensitive data, such as passwords, compromising account integrity and system confidentiality.

Affected Systems

The flaw affects Progress Software Corporation's OpenEdge platform. All instances that rely on OECH1 prefix encoding for protecting values are susceptible. No specific version details are supplied, so any OpenEdge deployment using OECH1 should be considered at risk.

Risk and Exploitability

The CVSS score of 9.1 indicates a critical severity, reflecting a serious risk when the encoding is used. The EPSS score is not available, but the lack of KEV listing suggests it is not yet widely exploited. Inferred, the likely attack vector involves an adversary with read access to the database or configuration files that contain OECH1-encoded data, enabling them to decode and recover the original values. The vulnerability does not require special privileges beyond access to stored data, making it both highly impactful and relatively easy to exploit if access is obtained.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Replace OECH1 prefix encoding with any supported secure prefix encoding based on symmetric encryption.
  • Re‑encode all existing values that currently use OECH1 to the new secure format.
  • Verify the OpenEdge application no longer references OECH1 anywhere in configuration or code.
  • If any credentials or secrets were exposed, rotate them immediately and update all affected systems.
  • Review database access controls to limit read access to sensitive data during remediation.

Generated by OpenCVE AI on April 14, 2026 at 14:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Progress Software Corporation
Progress Software Corporation openedge
Vendors & Products Progress Software Corporation
Progress Software Corporation openedge
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Recoverable obfuscation using the OECH1 prefix encoding in OpenEdge
Weaknesses CWE-257
References
Metrics cvssV4_0

{'score': 9.1, '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'}

Weaknesses
  • CWE-257

    Storing Passwords in a Recoverable Format

Sources

Status
PUBLISHED
Assigner
ProgressSoftware
Published
Updated
Apr 15, 2026, 3:58 AM
Reserved
Jul 23, 2025, 4:36 PM
Status
Awaiting Analysis
Published
Apr 14, 2026, 2:16 PM
Modified
Oct 7, 2026, 9:10 AM