Live › vulnerability › CVE-2026-101577
Go to dashboardHelidon's helidon-cors component in versions 4.0.0 through 4.5.5 has a flaw that an unauthenticated network attacker can trigger, but it needs a victim user to take an action. A successful attack can let the attacker change, insert or delete some data that Helidon can access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications built on Helidon 4.0.0 through 4.5.5 that use the helidon-cors component and expose it over HTTP. Sources do not describe further configuration conditions; teams on other Helidon versions or not using CORS handling are not indicated as affected.
No product ranges from the sources yet.
io.helidon version in pom.xml) and look for versions 4.0.0 through 4.5.5.io.helidon.cors).4.5.5, as listed in the Oracle advisory (unknown exact fixed version in sources).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Vulnerability in the Helidon product of Oracle Fusion Middleware (component: helidon-cors). Supported versions that are affected are 4.0.0-4.5.5. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Helidon. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Helidon accessible data. CVSS 3.1 Base Score 3.1 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N).
This page as .md · .json · in your agent: get_signal("CVE-2026-101577")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.