Live › vulnerability › CVE-2026-101574
Go to dashboardHelidon's OIDC component, in versions 4.0.0 through 4.5.5 and 27.0.0, has a flaw that a remote unauthenticated attacker can trigger over HTTP with difficulty and a user's action. A successful attack can expose critical data and allow some unauthorized changes to data Helidon can reach.
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 that run Helidon 4.0.0 through 4.5.5 or 27.0.0 with the OIDC component for login or token handling are exposed. Exploitation requires a victim to take an action, and the attacker needs network access to the HTTP endpoint. Teams not using Helidon OIDC can skip it.
No product ranges from the sources yet.
4.0.0 through 4.5.5 and 27.0.04.5.5 in the 4.x line or the fixed 27.x release (unknown exact fixed version in the 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: OIDC). Supported versions that are affected are 4.0.0-4.5.5 and 27.0.0. 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 and while the vulnerability is in Helidon, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Helidon accessible data as well as unauthorized update, insert or delete access to some of Helidon accessible data. CVSS 3.1 Base Score 6.9 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N).
This page as .md · .json · in your agent: get_signal("CVE-2026-101574")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.