MediumGHSA-h5fg-jpgr-rv9cCVE-2025-11965

Vert.x-Web Access Control Flaw in StaticHandler’s Hidden File Protection for Files Under Hidden Directories

Published 22 Oct 2025 · Updated 10 Sept 2026

Is your project on an affected io.vertx:vertx-web?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<4.5.22
Fixed in
4.5.22
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.vertx:vertx-web -DdepVersion=4.5.22 -DforceVersion=true
Affected
>=5.0.0 <5.0.5
Fixed in
5.0.5
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.vertx:vertx-web -DdepVersion=5.0.5 -DforceVersion=true

Details

Description

There is a flaw in the hidden file protection feature of Vert.x Web’s StaticHandler when setIncludeHidden(false) is configured.

In the current implementation, only files whose final path segment (i.e., the file name) begins with a dot (.) are treated as “hidden” and are blocked from being served. However, this logic fails in the following cases:

  • Files under hidden directories: For example, /.secret/config.txt — although .secret is a hidden directory, the file config.txt itself does not start with a dot, so it gets served.
  • Real-world impact: Sensitive files placed in hidden directories like .git, .env, .aws may become publicly accessible.

As a result, the behavior does not meet the expectations set by the includeHidden=false configuration, which should ideally protect all hidden files and directories. This gap may lead to unintended exposure of sensitive information.

Steps to Reproduce

1. Prepare test environment

# Create directory structure
mkdir -p src/test/resources/webroot/.secret
mkdir -p src/test/resources/webroot/.git

# Place test files
echo "This is a visible file" > src/test/resources/webroot/visible.txt
echo "This is a hidden file" > src/test/resources/webroot/.hidden.txt
echo "SECRET DATA: API_KEY=abc123" > src/test/resources/webroot/.secret/config.txt
echo "Git config data" > src/test/resources/webroot/.git/config
2. Implement test server

import io.vertx.core.AbstractVerticle;
import io.vertx.core.Vertx;
import io.vertx.ext.web.Router;
import io.vertx.ext.web.handler.StaticHandler;

public class StaticHandlerTestServer extends AbstractVerticle {
  @Override
  public void start() {
    Router router = Router.router(vertx);

    // Configure to not serve hidden files
    StaticHandler staticHandler = StaticHandler.create("src/test/resources/webroot")
      .setIncludeHidden(false)
      .setDirectoryListing(false);

    router.route("/*").handler(staticHandler);

    vertx.createHttpServer()
      .requestHandler(router)
      .listen(8082);
  }

  public static void main(String[] args) {
    Vertx vertx = Vertx.vertx();
    vertx.deployVerticle(new StaticHandlerTestServer());
  }
}
3. Confirm the vulnerability

# Normal file (accessible)
curl http://localhost:8082/visible.txt
# Result: 200 OK

# Hidden file (correctly blocked)
curl http://localhost:8082/.git
# Result: 404 Not Found

# File under hidden directory (vulnerable)
curl http://localhost:8082/.git/config
# Result: 200 OK - Returns contents of Git config

Potential Impact

1. Information Disclosure

Examples of sensitive files that could be exposed:

  • .git/config: Git repository settings (e.g., remote URL, credentials)
  • .env/*: Environment variables (API keys, DB credentials)
  • .aws/credentials: AWS access keys
  • .ssh/known_hosts: SSH host trust info
  • .docker/config.json: Docker registry credentials

2. Attack Scenarios

  • Attackers can guess common hidden directory names and enumerate filenames under them to access confidential data.
  • Especially dangerous for .git/HEAD, .git/config, .git/objects/* — which may allow full reconstruction of source code.

3. Affected Scope

  • Affected version: Vert.x Web 5.1.0-SNAPSHOT (likely earlier versions as well)
  • Environments: All OSes (Windows, Linux, macOS)
  • Configurations: All applications using StaticHandler.setIncludeHidden(false)

Is GHSA-h5fg-jpgr-rv9c in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected io.vertx:vertx-web, and gives you the command that fixes it.

More advisories for io.vertx:vertx-web

  • LowCVE-2025-11966Vert.x-Web vulnerable to Stored Cross-site Scripting in directory listings via file names · 22 Oct 2025
  • MediumCVE-2023-24815StaticHandler disclosure of classpath resources on Windows when mounted on a wildcard route · 10 Feb 2023
  • CriticalCVE-2019-17640Path Traversal in Eclipse Vert · 10 Feb 2022
  • HighCVE-2020-35217Cross-Site Request Forgery in Vert.x-Web framework · 22 Apr 2021
  • CriticalCVE-2018-12542Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location · 17 Oct 2018
  • HighCVE-2018-12540High severity vulnerability that affects io.vertx:vertx-web · 17 Oct 2018
io.vertx:vertx-web security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.