# CVE-2026-102628: Cadmos LTI exposure of sensitive information via debug mode

> An attacker can view sensitive server environment variables by triggering an exception in a Laravel application with debug mode enabled.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 11 Oct 2026
- **Also known as:** GHSA-2h69-w2xf-8972

## What is CVE-2026-102628?

CVE-2026-102628 is a critical vulnerability in Eummena Cadmos LTI, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-489 (Active Debug Code), CWE-215 (Insertion of Sensitive Information Into Debugging Code)

## Which versions are affected by CVE-2026-102628?


## How do I fix CVE-2026-102628?

No fix has been published for CVE-2026-102628 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102628 being exploited?

There is no known exploitation of CVE-2026-102628 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102628 and fix it if it is affected.

What it is: CVE-2026-102628 is a critical vulnerability in Eummena Cadmos LTI, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102628 in the wild and no public exploit code.

Affected product: Eummena Cadmos LTI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102628/ (Markdown: https://insights.sbomify.com/CVE-2026-102628/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102628
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102628
- OSV: https://osv.dev/vulnerability/CVE-2026-102628

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102628/
Summaries are generated and may contain mistakes; the official description above is the record.