# CVE-2026-53933: Maravel-Framework Vulnerable to Side-Channel Information Disclosure (Error Oracle) via Dynamic Route Fuzzing

> Attackers can map internal route parameters and controller schemas by triggering distinct 500 errors via dynamic route fuzzing in the Maravel PHP framework.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/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:** 8 Sep 2026
- **Updated:** 9 Sep 2026

## What is CVE-2026-53933?

CVE-2026-53933 is a medium-severity vulnerability in macropay-solutions maravel-framework, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2026-53933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53933 is a medium-severity vulnerability in macropay-solutions maravel-framework, published on 8 Sep 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-53933 in the wild and no public exploit code.

Affected product: macropay-solutions maravel-framework. 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-53933/ (Markdown: https://insights.sbomify.com/CVE-2026-53933/index.md)
```

## Sources

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

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