Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess exposed configuration files
-
DeliveryExtract OECH1-encoded secrets
-
ExploitDecode using weak algorithm
-
ExecutionAuthenticate with recovered credentials
-
PersistAccess database or admin interface
-
ImpactExfiltrate sensitive data or escalate privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Irreversible password storage
|
| Impact | CVSS 4.0 score of 9.1 reflects critical severity with network attack vector (AV:N), low complexity (AC:L), no privileges required (PR:N), and high impact across confidentiality, integrity, and availability for both vulnerable and subsequent systems (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H). SSVC framework confirms automatable exploitation with total technical impact, but exploitation status is 'none' at analysis time. EPSS data not provided, but the automatable nature and credential-focused impact suggest high weaponization potential once tooling emerges. The network attack vector combined with PR:N means any attacker accessing OECH1-encoded configuration files (via web server misconfiguration, backup exposure, supply chain compromise, or insider access) can reverse credentials without authentication barriers. However, absence of confirmed active exploitation (not KEV-listed) and unclear EPSS probability moderates immediate urgency compared to exploited RCE flaws. Risk escalates sharply in environments where OECH1-encoded database credentials or admin passwords are network-accessible in config repositories, CI/CD pipelines, or cloud storage. Organizations must treat this as a credential hygiene emergency requiring immediate inventory and re-encoding, not just a patch cycle item. |
| Exploit ScenarioDerived | An attacker discovers an OpenEdge application's configuration backup exposed via misconfigured cloud storage bucket or compromised CI/CD pipeline. The backup contains database.properties with OECH1-encoded admin password. Using publicly documented OECH1 decoding algorithms (or reverse-engineered tools likely to emerge), the attacker recovers plaintext credentials in seconds without cryptographic expertise. With database admin access, the attacker exfiltrates customer PII, injects backdoor stored procedures, or pivots to connected enterprise systems using the compromised credentials. The automatable nature enables mass scanning of exposed config files across internet-facing OpenEdge deployments. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 14, 2026
Progress OpenEdge 12.2.0-12.2.18 and 12.8.0-12.8.9 expose stored passwords and secrets to decryption through cryptographically weak OECH1 prefix encoding. Remote unauthenticated attackers can exploit this weakness to recover obfuscated credentials and sensitive data (CVSS 9.1, VC:H/VI:H). No public exploit identified at time of analysis, but the vulnerability is automatable with total technical impact per SSVC framework, making credential harvesting straightforward once encoding is accessed.
RemediationAI
Progress Software mandates immediate replacement of all OECH1-encoded values with alternative symmetric encryption-based prefix encodings supported in current OpenEdge versions, including OESHA256, OEAES, or other vendor-approved schemes documented in the security advisory. Organizations should inventory all configuration files, environment variables, startup scripts, and database connection pools for OECH1-prefixed strings using vendor-provided scanning tools or custom regex patterns (search for OECH1: prefix in .properties, .xml, .ini files). Re-encode identified secrets using OpenEdge's proenv utility or Secrets Manager integration, then rotate underlying credentials to invalidate compromised values. Vendor advisory at https://community.progress.com/s/article/Unintended-Use-of-OECH1-for-Password-Secrets-Protection includes migration scripts and encoding conversion procedures. No drop-in patch exists as the flaw is architectural; remediation requires manual re-encoding and credential rotation across all OpenEdge deployments. Implement configuration file access controls, encrypt backups containing secrets, and audit code repositories for checked-in OECH1 values during remediation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
OECH1 is a proprietary obfuscation scheme used across Progress OpenEdge platform components (application server, database, middleware) to encode sensitive configuration values like passwords, API keys, and database connection strings. Unlike modern symmetric encryption-based encodings (AES, 3DES), OECH1 relies on reversible obfuscation algorithms susceptible to cryptanalysis and brute-force recovery. The vulnerability falls under CWE-257 (Storing Passwords in a Recoverable Format), where the encoding provides only superficial protection against credential extraction. OpenEdge products affected include both the 12.2.x LTS branch (versions 12.2.0 through 12.2.18) and 12.8.x current branch (12.8.0 through 12.8.9) per CPE cpe:2.3:a:progress_software_corporation:openedge. Configuration files, environment variables, and runtime parameters using OECH1-prefixed values are vulnerable wherever stored or transmitted. The cryptographic weakness is intrinsic to the algorithm design, not an implementation flaw, requiring migration to alternative encodings rather than patching.
Know when Openedge gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Primary rating from Vendor (ProgressSoftware) · only source for this CVE.
CVSS VectorVendor: ProgressSoftware
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
Progress OpenEdge versions 12.2.0-12.2.18 and 12.8.0-12.8.9 contain a critical cryptographic weakness that allows unauthenticated attackers to decrypt stored passwords and secrets, potentially exposing all credential material within affected deployments. This vulnerability requires immediate assessment and isolation of affected systems, as credential compromise directly enables lateral movement and data breach scenarios across dependent applications and infrastructure.
No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to OpenEdge instances to trusted internal networks only; implement credential rotation for all accounts managed through affected OpenEdge deployments; monitor OpenEdge configuration files and authentication logs for unauthorized access attempts; deploy network segmentation to limit lateral movement post-compromise; prepare alternative authentication mechanisms or manual credential management until patched versions are available.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Insecure default configuration in Progress Software OpenEdge 10.2x and 11.x allows unauthenticated remote attackers to s
In OpenEdge Authentication Gateway and AdminServer prior to 11.7.19, 12.2.14, 12.8.1 on all platforms supported by the O
Directory traversal vulnerability in report/reportViewAction.jsp in Progress Software OpenEdge 11.2 allows remote attack
Local ABL Client bypass of the required PASOE security checks may allow an attacker to commit unauthorized code injectio
In Progress OpenEdge OEM (OpenEdge Management) and OEE (OpenEdge Explorer) before 12.7, a remote user (who has any OEM o
Progress OpenEdge AdminServer exposes authenticated RMI methods allowing arbitrary file reads with escalated OS privileg
In Progress OpenEdge before 11.7.14 and 12.x before 12.2.9, certain SUID binaries within the OpenEdge application were s
An ActiveMQ Discovery service was reachable by default from an OpenEdge Management installation when an OEE/OEM auto-dis
Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perfo
EUVD-2025-209440
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB