Cadmos LTI: Insertion of Sensitive Information Into Debugging Code
CVE-2026-102628 is a critical-severity insertion of sensitive information into debugging code vulnerability in Cadmos LTI from Eummena, with a CVSS 3.1 base score of 9.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2026-09-02 as the first without the flaw, so updating Cadmos LTI to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.34% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Cadmos LTI to 2026-09-02 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Eummena | Cadmos LTI | before 2026-09-02 | 2026-09-02 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.2 | Critical | CNA |
| CVSS 3.1 | 9.3 | Critical | CNA |
Official description
The Cadmos LTI application hosted at cadmos.eummena.io had Laravel debug mode enabled (APP_DEBUG=true, APP_ENV=local) in a publicly accessible environment. An unauthenticated attacker could send a GET request and trigger an unhandled exception, causing Laravel to expose the entire server environment, including all .env configuration variables, in plaintext. Fixed on or before 2026-09-02.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information Into Debugging Code
The product inserts sensitive information into debugging code.
How developers prevent this class of flaw
- Do not leave debug statements that could be executed in the source code. Ensure that all debug information is eradicated before releasing the software.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
More Insertion of Sensitive Information Into Debugging Code vulnerabilities (CWE-215)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Recent Insertion of Sensitive Information Into Debugging Code vulnerabilities
- 9.3 Critical severity
- 7.0 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.