Skip to main content
VulnerabilityPublished

CVE-2025-11965: Eclipse Foundation Vert.x · Exposed Files or Directories

Affects Eclipse Foundation Vert.xSource CVE Database V5

0

Not known to be exploited · CVSS 6.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Eclipse Foundation Vert.xAffected
  • 4.0.0 – 5.0.4
4 affected builds
Fixed in–

AI-suggested

  1. Upgrade Vert.x to a patched version once it becomes available from the Eclipse Foundation to address the StaticHandler access control flaw.
  2. In the interim, configure web servers or reverse proxies (e.g., Nginx, Apache) to explicitly deny access to hidden directories such as those starting with a dot (e.g., '.git', '.svn').
  3. Implement strict file system permissions to restrict access to sensitive directories and files on servers hosting Vert.x applications.
  4. Use application-level access controls to enforce authentication and authorization for sensitive resources.
  5. Conduct thorough code and configuration reviews to identify any inadvertent exposure of hidden directories or files.
  6. Monitor web server logs and application logs for unusual access patterns targeting hidden directories or files.
  7. Employ web application firewalls (WAFs) with rules to block requests attempting to access hidden directories.
  8. Educate development and operations teams about secure StaticHandler configuration and the risks of exposing hidden files or directories.
  9. Regularly scan deployed applications for exposed sensitive files using automated tools.
  10. Maintain an incident response plan to quickly address any detected unauthorized access related to this vulnerability.

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').

References

Community reviews

Loading reviews…