CVE-2026-2103CWE-321

Use of Hard-Coded Cryptographic Key for Password Storage

High · published February 6, 2026

CVSS v3.1
7.1
EPSS
0%
Percentile
1.1
In the wild
Unconfirmed
What it is

⚡ Those hard-coded cryptographic keys are a huge security risk! With identical keys across all installations, anyone with access to the application binary can decrypt sensitive data. 🔥 Think of it as a master key that every hotel room shares—anyone with that key can unlock every door without a trace. This allows attackers to access a treasure trove of sensitive information if they gain access to the application binary. An attacker could potentially reveal all user passwords, database connection strings, and API keys stored in the system. This could lead to unauthorized access to your entire network, resulting in catastrophic data breaches and loss of trust from your clients, all because those keys are like an all-access backstage pass!

Put simply

Think of it as a master key that every hotel room shares—anyone with that key can unlock every door without a trace. This allows attackers to access a treasure trove of sensitive information if they gain access to the application binary. CVE-2026-2103 reveals that Infor SyteLine ERP uses hard-coded static cryptographic keys for encrypting credentials, making it easy for attackers who can access the application binary and database to decrypt this sensitive information.

What to do

An attacker could potentially reveal all user passwords, database connection strings, and API keys stored in the system. This could lead to unauthorized access to your entire network, resulting in catastrophic data breaches and loss of trust from your clients, all because those keys are like an all-access backstage pass! Immediately switch to dynamic keys for encrypting credentials to bolster your security. Review your database for any hard-coded keys, and ensure that sensitive information is properly encrypted with unique keys per installation. Additionally, consider conducting a security audit to identify any other vulnerabilities. 🛡️ You've got this! By following these steps, you'll make your system a fortress against potential attackers. 🦸‍♂️

The record
Technical detail
CVSS v3.1
7.1 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CVSS v4.0
Not supplied
EPSS
0.00106 · 1.1th percentile
Weakness
CWE-321 · Use of Hard-coded Cryptographic Key
Published
2026-02-06T16:22Z
EPSS history
Timeline
  • 06 FEB 16:22Z
    Use of Hard-Coded Cryptographic Key for Password Storage
    cvelistv5