ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-8095

The OECH1 prefix encoding is intended to obfuscate values across the OpenEdge platform.

Published Apr 14, 2026 · catalog updated Oct 7, 2026 · The OECH1 prefix encoding

Check if you run it

No confirmed exploitation is on record for CVE-2025-8095. EPSS is 0.22%. Act only if a listed version of The OECH1 prefix encoding is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The OECH1 prefix encoding).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.22%
Remediation
Not established
Affected products
See sources for product scope

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.

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix CVE-2025-8095

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-8095. EPSS is 0.22%. Act only if a listed version of The OECH1 prefix encoding is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-257. EPSS 0.22%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 14, 2026 · NIST NVD

    Detected

    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.

  2. Oct 7, 2026 · NIST NVD

    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.

Sources

  • CVE.orgVulnerability recordCVE-2025-8095

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-8095

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2025-8095

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.