Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-102628 – Sensitive Information Disclosure via Laravel Debug Mode – Eummena Cadmos LTI

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-102628 is a critical information-disclosure vulnerability (CVSS 9.3) in Eummena’s Cadmos LTI application, a Laravel-based learning tool. The production deployment at cadmos.eummena.io was left running with Laravel debug mode enabled (APP_DEBUG=true, APP_ENV=local), allowing an unauthenticated attacker to trigger an unhandled exception and have Laravel return the full server environment — including all .env configuration values — in plaintext. The issue was fixed on or before September 2, 2026.

Technical details

  • Root cause: Laravel’s debug mode (APP_DEBUG=true) was enabled on a publicly reachable production instance, which causes the framework to render detailed error pages (via Laravel/Symfony’s exception handler) on unhandled exceptions.
  • Trigger conditions: No authentication or special request is required; a simple GET request that causes the application to throw an unhandled exception is sufficient to render the debug error page.
  • Attack vector: Network-based, no privileges or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: The rendered debug page discloses the complete server environment, including .env file contents — database credentials, API keys, and other secrets — in plaintext, which can be leveraged for further compromise of the application and connected systems.

Affected software

  • Eummena Cadmos LTI — all versions/deployments running with debug mode enabled prior to the fix applied on or before September 2, 2026 (publicly confirmed on the instance hosted at cadmos.eummena.io).

Severity

  • CVSS v3.1 Base Score: 9.3 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Mitigation and recommended actions

  • Immediate: Ensure the deployed Cadmos LTI instance reflects the vendor’s fix applied on or before September 2, 2026, and confirm APP_DEBUG=false and APP_ENV=production are set in the live environment.
  • If debug mode was ever enabled in production: Treat all secrets in the .env file (database credentials, API keys, application key, third-party service tokens) as compromised and rotate them immediately.
  • General hardening: Verify debug/error-detail pages are not reachable from the internet on any Laravel-based application, and add monitoring/alerting for unhandled exceptions that could indicate reconnaissance or exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge