{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-102477 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102477 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102477 is a high-severity denial of service vulnerability in Eclipse Vert.x, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102477 and fix it if it is affected.\n\nWhat it is: CVE-2026-102477 is a high-severity denial of service vulnerability in Eclipse Vert.x, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102477 in the wild and no public exploit code.\n\nAffected product: Eclipse Vert.x. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102477/ (Markdown: https://insights.sbomify.com/CVE-2026-102477/index.md)","id":"CVE-2026-102477","markdown":"https://insights.sbomify.com/CVE-2026-102477/index.md","name":"CVE-2026-102477","record":{"aliases":["GHSA-3f8m-f8fw-9m74","GHSA-4wvq-75mw-q6cg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Java gRPC library","requires_auth":"none","summary":"Attackers can cause denial of service in Eclipse Vert.x gRPC endpoints by sending compressed messages that expand beyond configured size limits.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"vert.x","vendor":"eclipse"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-409","name":"Improper Handling of Highly Compressed Data (Data Amplification)"}],"description":"In Eclipse Vert.x versions [4.0.0, 4.5.34] or [5.0.0,5.0.12] or [5.1.0,5.1.9] or [5.2.0, 5.2.0], a gRPC endpoint does have a configurable per message maximum size in bytes, however the maximum size applies to the received bytes. When applied to a compressed message, this only applies to the compressed size and not the actual size of the uncompressed content. This can be used to force a gRPC endpoint to allocate more bytes than the value defined by the configuration, making the endpoint vulnerable to compression bomb attacks.\n\nThe impacted component is io.vertx:vertx-gprc-server.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in Eclipse Vert.x","id":"CVE-2026-102477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in Octopus Server","id":"CVE-2026-102478"},"packages":[],"prev":{"headline":"Security feature bypass in Eclipse Vert.x","id":"CVE-2026-102476"},"products":["Eclipse Vert.x"],"published":"2026-10-15","related":[{"cvss_score":9.8,"headline":"Path Traversal in Eclipse Vert","id":"CVE-2019-17640","kev_date_added":null,"published":"2020-10-15"},{"cvss_score":9.8,"headline":"Eclipse Vert.x does not properly neutralize '' (forward slashes) sequences that can resolve to an external location","id":"CVE-2018-12542","kev_date_added":null,"published":"2018-10-10"},{"cvss_score":9.8,"headline":"Moderate severity vulnerability that affects io.vertx:vertx-core","id":"CVE-2018-12544","kev_date_added":null,"published":"2018-10-10"},{"cvss_score":9.2,"headline":"Deserialization in Eclipse Vert.x","id":"CVE-2026-102469","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":8.8,"headline":"High severity vulnerability that affects io.vertx:vertx-web","id":"CVE-2018-12540","kev_date_added":null,"published":"2018-07-12"},{"cvss_score":8.7,"headline":"Denial of service in Eclipse Vert.x","id":"CVE-2026-102461","kev_date_added":null,"published":"2026-10-15"},{"cvss_score":8.7,"headline":"Denial of service in Eclipse Vert.x","id":"CVE-2026-102467","kev_date_added":null,"published":"2026-10-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Eclipse Foundation"]},"summary":"Attackers can cause denial of service in Eclipse Vert.x gRPC endpoints by sending compressed messages that expand beyond configured size limits.","url":"https://insights.sbomify.com/CVE-2026-102477/"}