CVE-2026-53933

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Maravel, a PHP framework oriented towards dependency injection, prior to version 10.73.1 has a side-channel information disclosure issue. When a route was compiled with dynamic placeholders (e.g., /api/v1/users/{id}), the raw string placeholder key was mistakenly registered into the flat static route checklist. An attacker scanning endpoints could intentionally pass the literal template syntax (e.g., GET /api/v1/users/{id}) to force an unexpected match against the static map. Because the dynamic tree engine was bypassed, no arguments were captured. This forced modern PHP 8+ versions to throw a native ArgumentCountError, resulting in a 500 Internal Server Error instead of a uniform 404 Not Found. By tracking which fuzz patterns exploded into a 500 error, a malicious actor could programmatically profile and map out internal route parameter names and controller schemas. Version 10.73.1 contains a patch. As a workaround, mitigate this side-channel leak by implementing a defensive check in a global middleware. This will reject any literal brace patterns before they reach the router engine.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 10, 2026

Advisory Details (3)

Auto-updated Sep 8, 2026
No patch confirmed yet.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 06:14 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 07:46 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-17 09:18 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 10:50 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 12:23 UTCEG score recompute
  10. 2026-09-14 13:54 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-12 16:59 UTCEG score recompute
  13. 2026-09-11 18:32 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 12:57 UTCEG score recompute
  16. 2026-09-10 09:35 UTCEPSS rescore
  17. 2026-09-09 14:29 UTCEG score recompute
  18. 2026-09-09 13:37 UTCEG score recompute
  19. 2026-09-08 22:28 UTCEG score recompute
  20. 2026-09-08 22:04 UTCEG score recompute
  21. 2026-09-08 22:04 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53933?
CVE-2026-53933 is a medium vulnerability published on September 8, 2026. Maravel, a PHP framework oriented towards dependency injection, prior to version 10.73.1 has a side-channel information disclosure issue. When a route was compiled with dynamic placeholders (e.g., /api/v1/users/{id}), the raw string placeholder key was mistakenly registered into the flat static…
When was CVE-2026-53933 disclosed?
CVE-2026-53933 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53933 actively exploited?
CVE-2026-53933 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53933?
CVE-2026-53933 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-53933?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53933, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53933

Explore →

Is Your Infrastructure Affected by CVE-2026-53933?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.