CVE-2026-1002

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% 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, nvd
Elevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The Vert.x Web static handler component cache can be manipulated to deny the access to static files served by the handler using specifically crafted request URI.

The issue comes from an improper implementation of the C. rule of section 5.2.4 of RFC3986 and is fixed in Vert.x Core component (used by Vert.x Web): https://github.com/eclipse-vertx/vert.x/pull/5895

Steps to reproduce Given a file served by the static handler, craft an URI that introduces a string like bar%2F..%2F after the last / char to deny the access to the URI with an HTTP 404 response. For example https://example.com/foo/index.html can be denied with https://example.com/foo/bar%2F..%2Findex.html

Mitgation Disabling Static Handler cache fixes the issue.

StaticHandler staticHandler = StaticHandler.create().setCachingEnabled(false);

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

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
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

January 15, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 8, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

StaticHandlerImpl cache corruption · Issue #2836 · vert-x3/vertx-web · GitHub

https://github.com/vert-x3/vertx-web/issues/2836
github_pr

Fix a bug in the removeDots implementation.

Fix merged in eclipse-vertx/vert.x PR #5895 on 2026-01-14 — awaiting tagged release

https://github.com/eclipse-vertx/vert.x/pull/5895

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatvertx-core2026-07-02redhat
redhateap7-wildfly-0:7.3.18-3.GA_redhat_00001.1.el7eap2026-06-30redhat
redhatcryostat/jfr-datasource-rhel9:4.2.0-92026-05-26redhat
redhatvertx-core-logging2026-05-04redhat
redhatrhoai/odh-trustyai-service-rhel9:17767488592026-04-23redhat
redhatdevspaces/server-rhel9:17742287402026-03-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.vertx:vertx-core5.0.0 ... 5.0.6 (15 versions)5.0.7

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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.

Showing the most recent 100 of 130 total refreshes for this CVE.

  1. 2026-08-31 07:25 UTCOSV refresh
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:48 UTCEPSS rescore
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 14:04 UTCEG score recompute
  18. 2026-08-14 14:04 UTCVendor advisory
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 13:50 UTCEPSS rescore
  21. 2026-08-11 13:42 UTCEPSS rescore
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-09 19:35 UTCEG score recompute
  24. 2026-08-09 19:35 UTCVendor advisory
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-08 00:27 UTCEG score recompute
  3. 2026-08-08 00:27 UTCVendor advisory
  4. 2026-08-06 13:46 UTCEPSS rescore
  5. 2026-08-06 05:40 UTCEG score recompute
  6. 2026-08-06 05:40 UTCVendor advisory
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 15:10 UTCEPSS rescore
  9. 2026-08-04 10:38 UTCEPSS rescore
  10. 2026-08-03 10:35 UTCEPSS rescore
  11. 2026-08-02 23:16 UTCEG score recompute
  12. 2026-08-02 23:16 UTCVendor advisory
  13. 2026-08-02 02:26 UTCEPSS rescore
  14. 2026-08-01 04:15 UTCEPSS rescore
  15. 2026-07-30 01:30 UTCEPSS rescore
  16. 2026-07-27 14:13 UTCEPSS rescore
  17. 2026-07-26 14:54 UTCEPSS rescore
  18. 2026-07-26 14:54 UTCEPSS rescore
  19. 2026-07-25 14:17 UTCEPSS rescore
  20. 2026-07-25 14:17 UTCEPSS rescore
  21. 2026-07-24 14:17 UTCEPSS rescore
  22. 2026-07-23 14:18 UTCEPSS rescore
  23. 2026-07-23 14:18 UTCEPSS rescore
  24. 2026-07-23 10:19 UTCOSV refresh
  25. 2026-07-23 03:04 UTCEG score recompute
  26. 2026-07-22 14:08 UTCEPSS rescore
  27. 2026-07-21 15:24 UTCEPSS rescore
  28. 2026-07-20 17:08 UTCEPSS rescore
  29. 2026-07-19 14:30 UTCEPSS rescore
  30. 2026-07-19 02:28 UTCEPSS rescore
  31. 2026-07-18 10:04 UTCEPSS rescore
  32. 2026-07-16 17:02 UTCEPSS rescore
  33. 2026-07-15 16:57 UTCEPSS rescore
  34. 2026-07-15 02:00 UTCEPSS rescore
  35. 2026-07-13 22:30 UTCEPSS rescore
  36. 2026-07-13 06:12 UTCEPSS rescore
  37. 2026-07-12 05:46 UTCEPSS rescore
  38. 2026-07-11 08:27 UTCEPSS rescore
  39. 2026-07-09 19:10 UTCEPSS rescore
  40. 2026-07-08 15:15 UTCEPSS rescore
  41. 2026-07-08 15:15 UTCEPSS rescore
  42. 2026-07-07 13:46 UTCEPSS rescore
  43. 2026-07-06 16:27 UTCEPSS rescore
  44. 2026-07-06 05:02 UTCOSV refresh
  45. 2026-07-06 02:23 UTCEPSS rescore
  46. 2026-07-05 02:30 UTCEPSS rescore
  47. 2026-07-05 02:30 UTCEPSS rescore
  48. 2026-07-04 06:31 UTCEPSS rescore
  49. 2026-07-01 15:06 UTCEPSS rescore
  50. 2026-07-01 15:06 UTCEPSS rescore
  51. 2026-06-30 23:22 UTCEPSS rescore
  52. 2026-06-29 14:06 UTCEPSS rescore
  53. 2026-06-28 14:07 UTCEPSS rescore
  54. 2026-06-28 04:56 UTCEPSS rescore
  55. 2026-06-28 04:56 UTCEPSS rescore
  56. 2026-06-27 03:08 UTCEPSS rescore
  57. 2026-06-25 13:49 UTCEPSS rescore
  58. 2026-06-24 14:05 UTCEPSS rescore
  59. 2026-06-23 21:32 UTCEPSS rescore
  60. 2026-06-22 14:25 UTCEPSS rescore
  61. 2026-06-22 14:25 UTCEPSS rescore
  62. 2026-06-21 14:56 UTCEPSS rescore
  63. 2026-06-21 14:56 UTCEPSS rescore
  64. 2026-06-21 01:59 UTCEPSS rescore
  65. 2026-06-21 01:59 UTCEPSS rescore
  66. 2026-06-19 19:25 UTCEPSS rescore
  67. 2026-06-18 17:52 UTCEPSS rescore
  68. 2026-06-17 17:53 UTCEPSS rescore
  69. 2026-06-17 16:43 UTCOSV refresh
  70. 2026-06-16 17:52 UTCEPSS rescore
  71. 2026-06-15 17:48 UTCEPSS rescore
  72. 2026-06-14 23:18 UTCEPSS rescore
  73. 2026-06-13 23:00 UTCEPSS rescore
  74. 2026-06-13 23:00 UTCEPSS rescore
  75. 2026-06-12 23:12 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-1002?
CVE-2026-1002 is a medium vulnerability published on January 15, 2026. The Vert.x Web static handler component cache can be manipulated to deny the access to static files served by the handler using specifically crafted request URI. The issue comes from an improper implementation of the C. rule of section 5.2.4 of RFC3986 and is fixed in Vert.x Core component (used by…
When was CVE-2026-1002 disclosed?
CVE-2026-1002 was first published in the National Vulnerability Database on January 15, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1002 actively exploited?
CVE-2026-1002 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 71.5% of all scored CVEs.
What is the CVSS score of CVE-2026-1002?
CVE-2026-1002 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-1002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1002, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-1002

Explore →

Is Your Infrastructure Affected by CVE-2026-1002?

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