OAuth2 client-secret exposure via reversible encoding
Published Apr 17, 2026 · Updated Apr 17, 2026
Credential exposure in Sparx Systems Enterprise Architect 16.1.1627 allows local users to recover the plaintext OAuth2 client secret. The desktop client decodes the encoded secret into plaintext and supplies it during the OpenID token exchange. Local access to the installed client is required, and disclosure compromises OAuth2 client authentication during OpenID token requests.
Summary
What happened
Credential exposure in Sparx Systems Enterprise Architect 16.1.1627 allows local users to recover the plaintext OAuth2 client secret. The desktop client decodes the encoded secret into plaintext and supplies it during the OpenID token exchange. Local access to the installed client is required, and disclosure compromises OAuth2 client authentication during OpenID token requests.
The record
- CVE
- CVE-2025-15622
- Published
- Apr 17, 2026
- Updated
- Apr 17, 2026
- Vendor
- Sparx Systems
- Product
- Enterprise Architect
- Classifications
- CWE-522, T1552
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2026CVE publishedPublication date reported by the CVE source.
- Apr 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.1.1627
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo