# CVE-2025-11965: Vert.x-Web Access Control Flaw in StaticHandler’s Hidden File Protection for Files Under Hidden Directories

> Attackers can access files in hidden directories like .git/config if StaticHandler is configured to block hidden files but not directories.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/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:** Yes
- **Published:** 22 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** CLEANSTART-2026-HQ10523, CLEANSTART-2026-NB67850, CLEANSTART-2026-WF23391, ECHO-7ccb-ff37-0c34, GHSA-h5fg-jpgr-rv9c, MINI-5x3w-gv5r-ggw3, MINI-fwfv-365v-89gm, MINI-gp3g-92jx-7w3j, MINI-gwwc-hx57-h6p3, MINI-jf59-v72v-x246, MINI-wfcf-mhc3-vxrx

## What is CVE-2025-11965?

CVE-2025-11965 is a medium-severity path traversal vulnerability in Eclipse Foundation Vert.x, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Eclipse Vert.x versions [4.0.0, 4.5.21] and [5.0.0, 5.0.4], a StaticHandler configuration for restricting access to hidden files fails to restrict access to hidden directories, allowing unauthorized users to retrieve files within them (e.g. '.git/config').

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2025-11965?

4 open source packages ship an affected version, including io.vertx:vertx-web. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.vertx:vertx-web` | Maven | All versions | 4.5.22 |
| `io.vertx:vertx-web` | Maven | All versions | 4.5.22 |
| `io.vertx:vertx-web` | Maven | From 5.0.0 | 5.0.5 |
| `io.vertx:vertx-web` | Maven | From 5.0.0 | 5.0.5 |

Products: Eclipse Vert.x.

## How do I fix CVE-2025-11965?

Upgrade io.vertx:vertx-web to a fixed version for your release line: 4.5.22 or 5.0.5.

## Is CVE-2025-11965 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11965 exists.

## Other vulnerabilities in Eclipse Foundation Vert.x

- [CVE-2019-17640](https://insights.sbomify.com/CVE-2019-17640/): Path Traversal in Eclipse Vert (critical 9.8)
- [CVE-2018-12542](https://insights.sbomify.com/CVE-2018-12542/): Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location (critical 9.8)
- [CVE-2018-12544](https://insights.sbomify.com/CVE-2018-12544/): Moderate severity vulnerability that affects io.vertx:vertx-core (critical 9.8)
- [CVE-2026-102469](https://insights.sbomify.com/CVE-2026-102469/): Deserialization in Eclipse Vert.x (critical 9.2)
- [CVE-2018-12540](https://insights.sbomify.com/CVE-2018-12540/): High severity vulnerability that affects io.vertx:vertx-web (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11965 and fix it if it is affected.

What it is: CVE-2025-11965 is a medium-severity path traversal vulnerability in Eclipse Foundation Vert.x, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11965 exists.

Affected packages and fixed versions:
- io.vertx:vertx-web (Maven): affected all versions; fixed in 4.5.22
- io.vertx:vertx-web (Maven): affected all versions; fixed in 4.5.22
- io.vertx:vertx-web (Maven): affected from 5.0.0; fixed in 5.0.5
- io.vertx:vertx-web (Maven): affected from 5.0.0; fixed in 5.0.5

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-2025-11965/ (Markdown: https://insights.sbomify.com/CVE-2025-11965/index.md)
```

## Sources

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

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