CVE-2026-2103
Use of Hard-Coded Cryptographic Key for Password Storage
Description
Infor SyteLine ERP uses hard-coded static cryptographic keys to encrypt stored credentials, including user passwords, database connection strings, and API keys. The encryption keys are identical across all installations. An attacker with access to the application binary and database can decrypt all stored credentials.
INFO
Published Date :
Feb. 6, 2026, 5:16 p.m.
Last Modified :
Feb. 17, 2026, 3:46 p.m.
Remotely Exploit :
No
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 27b6da8a-f51d-48d9-9eef-9b7f3405d20d | ||||
| CVSS 3.1 | HIGH | [email protected] | ||||
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Generate unique encryption keys for each installation.
- Do not hard-code sensitive cryptographic keys.
- Rotate keys regularly.
- Securely store and manage keys.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-2103.
| URL | Resource |
|---|---|
| https://blog.blacklanternsecurity.com/p/cve-2026-2103-infor-syteline-erp | ExploitThird Party Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-2103 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-2103
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-2103 vulnerability anywhere in the article.
-
reddit.com
CVE-2026-2103 - Infor Syteline ERP - Keys Included: No Assembly Required
Let us know your cookie preferences Reddit uses cookies and similar technologies to: Keep the website operational and running properly Prevent fraud and abuse Monitor site usage and performance metric ... Read more
The following table lists the changes that have been made to the
CVE-2026-2103 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Feb. 17, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Added CWE CWE-798 Added CPE Configuration OR *cpe:2.3:a:infor:syteline_erp:10.0.8803.16889:*:*:*:*:*:*:* Added Reference Type Black Lantern Security: https://blog.blacklanternsecurity.com/p/cve-2026-2103-infor-syteline-erp Types: Exploit, Third Party Advisory -
New CVE Received by [email protected]
Feb. 06, 2026
Action Type Old Value New Value Added Description Infor SyteLine ERP uses hard-coded static cryptographic keys to encrypt stored credentials, including user passwords, database connection strings, and API keys. The encryption keys are identical across all installations. An attacker with access to the application binary and database can decrypt all stored credentials. Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Added CWE CWE-321 Added Reference https://blog.blacklanternsecurity.com/p/cve-2026-2103-infor-syteline-erp