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

Published Apr 14, 2026
·
Updated

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.

Affected Software

1 affected component
Progress Software OpenEdge

Event History

Apr 14, 2026
CVE Published
via MITRE·01:13 PM
Data Sourced
via MITRE·01:13 PM
DescriptionWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-8095?

CVE-2025-8095 is considered a high severity vulnerability due to its cryptographic weakness in the OECH1 prefix encoding.

2

How do I fix CVE-2025-8095?

To fix CVE-2025-8095, replace the OECH1 prefix encoding with a stronger encryption method and review your data obfuscation strategies.

3

Which software is affected by CVE-2025-8095?

CVE-2025-8095 affects Progress Software OpenEdge due to its use of the OECH1 encoding method.

4

What are the risks associated with CVE-2025-8095?

The risks of CVE-2025-8095 include potential data exposure and compromised integrity of sensitive information stored using weak obfuscation.

5

When was CVE-2025-8095 published?

CVE-2025-8095 was published as part of ongoing security assessments of cryptographic implementations within OpenEdge.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203