Okta credential exposure via hardcoded API key
Published Mar 5, 2025 · Updated Nov 3, 2025
Use of a hardcoded cryptographic key in Vasion Print before Application 20.0.1923 allows attackers to obtain an Okta API key from environment files. The appliance stores the same Okta API credential in application .env files instead of provisioning a per-installation secret. Exploitation requires access to those appliance files; the public disclosure does not establish the credential’s Okta privileges or a demonstrated follow-on action.
Summary
What happened
Use of a hardcoded cryptographic key in Vasion Print before Application 20.0.1923 allows attackers to obtain an Okta API key from environment files. The appliance stores the same Okta API credential in application .env files instead of provisioning a per-installation secret. Exploitation requires access to those appliance files; the public disclosure does not establish the credential’s Okta privileges or a demonstrated follow-on action.
The record
- CVE
- CVE-2025-27674
- Published
- Mar 5, 2025
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-321, T1552.001
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 5, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
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