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.
0.3%(unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 27th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-215Insertion of Sensitive Information Into Debugging Code CWE-489Active Debug Code
Show the promptExplain CVE-2026-102628 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102628?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102628?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102628 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
eummena:cadmos lti
Versions
From the CNA's record in the CVE List.
Product
Affected
Eummena Cadmos LTI
before 2026-09-02
Attack patterns (CAPEC)
CAPEC-121 Exploit Non-Production Interfaces Likelihood: Low · Severity: High
CAPEC-661 Root/Jailbreak Detection Evasion via Debugging Likelihood: Medium · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.